4 ms·
Maintainable code is a fools errand people just need the lingo for the interview, people don't stay at the same job long enough to really worry about it long te
by literallyaduck 5y ago
Maintainable code is a fools errand people just need the lingo for the interview, people don't stay at the same job long enough to really worry about it long term. People ship the one to throw away then the next devs rewrite everything their foredevs wrote. Languages, databases and standards are moving targets and today's best practice is tomorrow's antipattern.
If you want to ensure that you hire devs who have longevity in your product only hire devs who have worked in the same place long enough to pay for their coding choices and ask them for specific times they had technical debt and what steps they took to remedy the problem. You will find out more by letting them talk.
- moneywoes 5y agoLet’s say I’m in an interview situation, how do I implement this lingo? Additionally I wholeheartedly agree with you based on what I’ve seen at work
- literallyaduck 5y agoFrom an interviewed side: Ask open ended questions. Examples: Tell me about a time, describe a situation where, what steps have you taken, the more they talk the better chance you have to assess them. From an interviewee side: be prepared to describe situation where you maintained and application what safeguards you put in place, keep everything pleasant and remember to smile as people can hear it in your voice even if there is no video feed. Feign passion if you must. The whole process is a sales pitch and you are selling yourself, toot your own horn and make mountains of every little molehill of a project you have been part of. Talk about your commitment to testing and know the test pyramid, flip the interview around and ask them questions, it throws them off their guard and they will be impressed. The one who betrays the most information loses.