3 ms·
Anecdotal example that apparently stung you too deep. Sorry for that. You should know there are some of us who are quite disciplined and self-reevaluate fairly
by pdimitar 10y ago
Anecdotal example that apparently stung you too deep. Sorry for that.
You should know there are some of us who are quite disciplined and self-reevaluate fairly often. If I was on the place of your engineer I'd spend 2 weeks at most and then just think it through the weekend -- why is this taking so long? Am I overthinking the possible future plans for this feature? (Very likely.) What are the main hurdles? (I'd write them down and analyze them one by one.) What makes me think a quickly put together code isn't good enough?
It seems you had a junior developer put in a situation too big for their non-technical abilities. Again, this is nasty and I am sorry that you have been bitten by that.
But please have in mind there are many other programmers out there who can do a much better job from the organizational (non-technical) side of things.