I am constantly espousing the importance of professional development and keeping up with engineering best practices. It’s a necessity if you want to stay relevant, marketable, and sharp in the world of software engineering. (It can also be hard AF, especially when there are other demands in your life. I’m looking 👀 at you two rugrats running around my house.) Recently, I’ve felt like I’ve needed more structure to my approach, so I’m unveiling The Matrix (of Professional Development Excellence)!Read More
As part of my process to keep my professional development razor sharp, I’m making it a point to read more. A great resource is php[architect], the definitive publication for modern PHP developers. It’s something I have been meaning to read more consistently, and after having read the latest issue (February 2018 at the time of this writing), I’m planning on reading past issues as well. Read More
Three weeks ago, I set lofty goals for my journey to change up my career. The idea was 6 weeks to success, and putting it out there did a few things for me. It laid out a plan to follow, and also gave me something to keep me accountable. Three weeks later I’m checking in and happy with my progress.
[Illustration attributed to Sean Gallo at http://www.seangallo.com]
How do you approach a large project? (The same way you eat an elephant.)
My mantra is to break it down into smaller parts and methodically work my way through. How you work your way through can vary. If it is something you quickly want feedback on I like to iterate, as with agile project management. If the requirements/goal are more static, waterfall may be the appropriate technique.