diff --git a/Me/2023-11-10.md b/Me/2023-11-10.md
index fb884b2..90c0d67 100644
--- a/Me/2023-11-10.md
+++ b/Me/2023-11-10.md
@@ -12,7 +12,7 @@ The last 2 years (as showing my by commits on this repo), has been pretty busy l
 I had, about 4 months before getting the job at Fastwyre (known as "Cameron Communications" when I first started working here), I had enrolled at Full Sail University to get a bachelor's in CS. 
 
 ## Why I chose CS over IT
-At the time I decided to go for CS rather than IT because, in comparison to CS, IT is simple-ish and you can learn it fairly quickly compared to CS. Yes you can learn CS by yourself, but the 'best practices' are MUCH more difficult to learn by yourself
+At the time I decided to go for CS rather than IT because, in comparison to CS, IT is simple-ish and you can learn it fairly quickly compared to CS. Yes you can learn CS by yourself, but the 'best practices' are MUCH more difficult to learn by yourself. At least in my experience, you can break something and then learn how NOT to do something more than learning how not to do somehing correctly from the beginning. 
 
 ## How I got my Job with Fastwyre
 
@@ -23,5 +23,4 @@ The simple fact I had a good background in Software and DB's, helped me get the
 ## My Companies Infrastructure
 Without going into detail, most of our systems are YEARS out of date. Most of them being RHEL 4 & RedHat 6 or older. Just about all of our systems are OLD and mostly DIY (with the industry and corperate direction of not spending more money than needed). Many of the core workflows being 10+ years old shell scripts running on a system that went EOL in 2014. 
 
-Most of our internal systems only being held together by spit and dirt. I've had to learn most of the OLD methods of admining
-
+Most of our internal systems only being held together by spit and dirt. I've had to learn most of the OLD methods of admin-ing, alongside having to find out how scripts were made in the "old times". Most of the shell scripts I've had to re-enginner. I've had to completely re-implement many of the things developed by my predecessor, because he designed them to be more manual than needed. In most of my "re-engineering" of solutions, I've had to reimplement things to be comprehensive. Basically meaning that I've had to rework the workflows that my predecessor put together to encompase both the present and past. Most of the things I've had to rework were designed to only work in the present (designed to work as if there was never a chance for his system to fail). Most of the things I've had to rework were due to updates to other systems As often in our industry, updates to other systems often break compatiblity with current workflows/applications. This has happend far too often, as I've had gotten the calls & emails that something failed to function (within 1-2 weeks after a update to a