When was the the last time you realized a project was doomed? That time you knew the plug should have been pulled, but you kept things quiet and watched the work painfully fizzle out. If you care enough about the work, you probably have these feelings often. Maybe there’s context…
Tag:
how to code
Art is subjective, soft, human, unique. Science is objective, formulaic, algorithmic, process-heavy. Think about a recent problem you faced and its surrounding context. Was your approach more artistic or more scientific? Did your perception change as you solved the problem? How did it compare with your colleagues? As with anything…
#1 — Do not criticize others while being blind to your own faults. Do not seek fault in others while staying blissfully unaware of your own. When others code slowly, it’s because they’re inefficient and don’t manage their time well. When I code slowly, it’s because I’m being thorough and…
As a Junior IC How comfortable am I developing code and debugging issues? Could I give a presentation about my team? Do I know who to contact if I’m not sure how to solve a problem (besides my mentor)? Did I release a project end-to-end that required me to do…
Debugging is a critical skill. More important than the skill is the mindset. The debugger’s mindset is the attitude that you must always understand the why behind a problem; any ambiguities or unknowns are unacceptable. This mindset has the potential to carry you from debugging small functions to solving difficult…
Creating a technical plan is a sign of professionalism and maturity as a software developer. No matter what you’re working on, whether it be a straightforward feature extension or a massive data migration, a technical plan must be written. Why Should I Write A Technical Plan? A written plan forces…
Code reviews are an essential part of software development. To be good at the craft, we must be able to review the craftsmanship of others. The more books you read, the better you write; the more code you review, the better you code. The following 12-item code review checklist is…
Any developer, with any level of experience, can have bad habits. This is the junior developer neglecting the ripple effect of his changes. It could just as easily be the senior engineer rampaging through the codebase with her rewrites. Bad habits are just habits; they do not define a person…