Note that "Finish shit on time" is almost a subset of "being able to estimate well". Having mentored and hired more than a few junior devs, if I could stress O

Note that "Finish shit on time" is almost a subset of "being able to estimate well". Having mentored and hired more than a few junior devs, if I could stress ONE thing to make them better developers, it would be to focus on figuring out how to estimate accurately. Estimating accurately has a variety of criteria, like knowing the system you're developing against well enough to understand pitfalls and hurdles, knowing how much time will be spent discussing the task at hand, etc. It's not just "this is how long it will take me to write <x> function"... but it is absolutely critical to getting shit done on time, as it literally helps you define what on time is.