It’s funny how you can hear something over and over again but it doesn’t really ‘click’ until you actually sit down and play with it for a while.
This has been the case with me and using small functions (< 4 or 5 lines). It’s something that I hear people say, and I look at and think “Yeah, that’s a good idea and it makes sense.” Then it comes to implementation and I end up writing methods that range from 5 to 20 lines of code(or sometimes even more I’m ashamed to admit).
In the software development industry, if you’ve heard it once, you’ve heard it a thousand times. Automate your processes or you will regret it in the long run.
Today folks, I want to join the cool kids and say that you should automate your processes or you will regret it in the long run. And not in the sort of “Oh boy this sure is annoying, I wish I didn’t have press this combination of buttons every week” way but rather the “Oh s@#$, if this had been automated we would be able to figure out what the he** went wrong here.”
This week I’ve been thinking about priorities a lot. I’ve recently gone through a busy phase and during that time I came to realize what I’m willing to sacrifice and what I’m not willing to sacrifice for my career. One of the things I’m not willing to budge on is time with my fiance. Now, before I get too far into this I just want to say that yes, I understand that there are busy times in the life-cycle of a project and I’m willing to be flexible with that, I’m willing to have busy weeks and spend late nights at the office, what I’m not willing to budge on is this: when I’m with my fiance, when we’re spending time alone, going to the farmer’s market or general adventuring in this city of ours, my attention will be with my fiance.
My (very) Out of Date Blog 