3 ms·
I wanted to edit this factor in as well actually. I remember well the anecdotes of working for Steve Jobs. Devs sitting through an entire weekend just to make
by xxxdarrenxxx 9y ago
I wanted to edit this factor in as well actually.
I remember well the anecdotes of working for Steve Jobs. Devs sitting through an entire weekend just to make the transition for switching between menu's precise to the millisecond. This one is slightly hyperbole, but the point is standards.
It's no coincidence the ipod is the most famous music player in history ever.
Devs might see the issues with the code, but as you say, a lot off people in high places give 0 shits.
I've had this happen myself at many companies I worked with. I found a way to be more efficient and u get false promises of it being adressed in the future or your advice gets ignored, or dismissed as a waste off time.
At worst u become the know-it-all who "can't let things go". Fun times..
While there are many inexperienced devs. A devs work is only as good as the standards of it's "captain".
- throwaway47861 9y agoDo what I do. Don't ask them for the extra time. Make it a challenge for yourself to create the better solution in the allotted time budget. Or make it a side project (10-20% time). I may be becoming too cynical or slightly old but I don't care if the businessmen are smart enough to recognize a good investment in quality. I am not interested in educating bean counters. I simply don't ask them and I leave them no choice. I invest in a future where I won't be cursing myself or them. They never know it and we're all better off.