Mobile blogging

I have just installed the Blogger app onto my cell phone, which means that is I'll be more likely to actually blog my random thoughts and ideas. Hopefully I will be able to keep my blogging audience entertained.

Just think of it as a glimpse into a real programmer's life.

Stay tuned....

Never stop Learning

I know a bit of C# and a myriad of other languages, but it results in jack of all trades master of none type of deal for me.  I don't like this at all, it restricts my confidence in my abilities and tries to stop me from treading ahead in projects.   I have pushed myself to start learning again, I chose ASP.NET MVC 5, which is very exciting, I can't wait to start creating websites with MVC.  The big thing that really gets me excited is figuring out a piece of the puzzle that has evaded me or intimidated me for the longest time.

I HAVE CONQUERED A NEW LAND!

I know about the concepts of MVC but never really put it to use because most of the projects that I work on are all legacy applications that were built 10+ years ago, so I couldn't even slip pieces of new technology into them without exerting a bit more time than my project managers would allow.

Now there is another new developer that is also interested in learning MVC, so he started a new project in MVC and everyone is forced to allow us the learning curve needed to make the site functional.

Figuring out the Syntax and how each piece of the puzzle fits together to make the system work is what makes this job satisfying and exciting all at the same time. 

Never stop learning.  Find a book or a good web series or a YouTube video and absorb all the knowledge that you can.

NEVER STOP LEARNING

Old Code, You Wrote

Do you ever go back to code you had written a long time ago and wonder who had written it and why they made it so messy?

I realized that I need to go through my documentation for some of my first projects here (or actually write the documentation).  While looking through the code I have seen things that I really want to change or improve, not that the code I had written before was bad, but the code could be better.  The only problem that I face in doing this is that then the code needs to be tested and compiled and pushed to production, and some of these projects have their feet in many places all at once.

I think that what I am going to do with this code (since I am short on time, most of the time) is to change some of the things that don't change the flow of logic.  I am talking about things like using blocks where before I didn't have them because I didn't know about them when I first wrote the code. 

The rest of the changes I think I might just put into the documentation of the code in a section labeled "Future Updates", or something of the like.  If the change isn't too ​big, but something that I don't want to change and not test for fear of breaking the code, I am going to write a little comment where I would make the change, something that would make complete sense to whoever looks at it, especially me.

​​​​​How do you document code?