Not testing is crazy. Once you realize you can actually refactor without ever having the fear you’ve broken something, there’s actually opportunity to make rapid improvments in structure and performance. Taking 2 minutes to write the test can save your hours of debugging. Unless you’re building a throwaway prototype, not unit testing is always the wrong choice.
On a serious note, I love cooking and washing and cleaning. I’m not staring at a screen and the objective is clear.
I’m not contemplating whether this is worth my time or stressed about other things. Although, I don’t cook for many people so I guess my outlook would be different in those cases.
The difference is, in the job interview you’re writing it from scratch yourself. On the job you have to take over from the guy who left 10 years ago and that button was designed in such a way that resizing it will add garbage data to all tables in the database and also send an email to all your customers telling them to switch providers.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.