Test driven development, Extreme Programming, and many other approaches encourage us to start typing in code, either as a test or as functionality. That’s good advice, but you should never start coding blindly.
Knowing how to do something doesn’t mean you know when or where you should do it. Or even if you should. That’s the difference between skill and experience.
There are an infinite number of integers. How many do you use in your thinking and planning?
Eventually what was a best practice in one situation turns into an average practice for the industry.
The trick is to know which models to use, and when to use them.
How you see a problem is just as much of a bias as how you respond to it.
Testing and the essential attributes of what you’re testing
Visualizing your career progression to manage your career
Understanding what scope of influence means in practice
Why taking a break is so important to having an impact
Level is really a proxy of scope of influence