Dear Client, Here’s Why That Change Took So Long

Re:Dear Client, Here’s Why That Change Took So Long by dfjhdkjfhsdkf on Tuesday May 07, 2019 @12:57PM (#19851249)

I agree with your comment about senior devs. it seems as devs climb the ladder many get a superiority complex where they could do things quickly and others cannot.

I was once a tech lead of a team where the architect had been berating and criticizing a team member for weeks over something he thought should take a day.

I suggested he should take over and complete it. It took him weeks to complete.

[ Parent | on HN ]

Re:Dear Client, Here’s Why That Change Took So Long by rdiddly on Tuesday May 07, 2019 @02:37PM (#19852193)

the architect had been berating and criticizing a team member for weeks

If berate is truly the appropriate word (upon investigation), and I had any say in the matter, I would fire his toxic ass immediately.

[ Parent | on HN ]

Re:Dear Client, Here’s Why That Change Took So Long by jimrhods23 on Tuesday May 07, 2019 @02:16PM (#19852003)

"I was once a tech lead of a team where the architect had been berating and criticizing a team member for weeks over something he thought should take a day"

As I've gotten more experience as a developer, I've realized that most tasks take longer than I used to estimate..usually because I want to come up with a long-term solution and not just hack something together with no testing.

[ Parent | on HN ]

Re:Dear Client, Here’s Why That Change Took So Long by funkymike on Wednesday May 08, 2019 @11:47AM (#19859978)

I'm sure I still have far to go, but currently when I see someone quote a time frame for a change I am more concerned when it is short vs. seems too long. Especially when the dev is questioned and the estimate doesn't include time for documentation, deployment, etc.

[ Parent | on HN ]