4 ms·
You probably never had developers working for you. First, if you don’t give them a deadline they will work on it for months trying to get it perfect, but it wil
by brabel 1mo ago
You probably never had developers working for you. First, if you don’t give them a deadline they will work on it for months trying to get it perfect, but it will still be buggy and do the wrong thing unless you keep very close attention. Second, because you must give deadlines due to the previous point, the result will be buggier still, as they will spend most of their times on what to name variables and how to structure the packages and modules. Their testing will cover their mocks and when put together in the real thing most functionality will just not work at all.
I’ve seen this happen even with senior developers. With juniors it’s guaranteed to happen without a very good tutor.
Take some fucking responsibility. If you deliver software, make sure it’s in a working state. Don’t blame your manager for everything, they did not force you to write shitty code, if you think they can do that you are not ready to work as a professional developer, you are just a code monkey.
- denkmoon 1mo ago>as they will spend most of their times on what to name variables and how to structure the packages and modules. Incredible strawman of dev behaviour, I can only assume you are a manager yourself. I assure you, that's not what we're doing.
- jbeninger 1mo agoAlso, attacking good naming and structure belies their claim of knowing anything about dev at all. If you can't tell the quality difference between a well-structured program and spaghetti code consisting of single-letter variables, you don't belong in software. Honestly, from the tone, I suspect the gp post is just trying to get a rise.