4 ms·
Things that a good engineer should be able to do in a day gets done in a month or more. I think the fact that you put "a good engineer" in your post undermines
by onion2k 4y ago
Things that a good engineer should be able to do in a day gets done in a month or more.
I think the fact that you put "a good engineer" in your post undermines the point you're making.
People taking too long to complete simple tasks is a problem, but only where those tasks don't really require any significant ability to complete. Something simple and low risk should be completed quickly by anyone, even a terrible engineer.
Good engineers don't go quickly though. Where something is complex or high risk they should take their time and go slowly. Spending more than a day just considering the task in full is fine. Honestly, for the majority of tasks beyond anything trivial, I'd be very wary of any dev who claimed to be able to go quickly.
- ramblerman 4y agoSo... not "Things that a good engineer should be able to do in a day" then.
- onion2k 4y agoThe point is that things that there isn't anything that requires a good engineer that also can be done in a day. Either a job is something that can be done in a trivial amount of time because it's simple, or it's something that's hard enough to take some skill. It's never both. There are no jobs that can be done faster by being a better engineer. Good engineers do better work, not faster work. Often they're actually slower because they consider the edge cases and they don't cut corners.