News for hackers. Stuff that matters.

A comment on Dealing with insubordination. Parent comment

Re:Dealing with insubordination by Clubber on Tuesday November 21, 2017 @09:53AM (#15748171)
>How do we/the developer know it was “a hack”, and also “a bad idea”? The word hack isn’t used in the article.

Well we don't for sure, but based on that paragraph I quoted, it sounded like it, especially since the author immediately mentioned ripping it out if it proved to be a bad idea in a later sprint (which doesn't happen as often as you would like in software shops with deadlines.)

>The lead should have .. well, led .. by having a business logic reason for the inclusion of the variable. If they did and the developer still refused, then they’re in insubordination territory.

I would be comfortable with that scenario.

[ Parent | on HN ]
Re:Dealing with insubordination by paulgrimes1 on Tuesday November 21, 2017 @10:07AM (#15748286)
> Well we don't for sure, but based on that paragraph I quoted, it sounded like it, especially since the author immediately mentioned ripping it out if it proved to be a bad idea in a later sprint (which doesn't happen as often as you would like in software shops with deadlines.)

That’s a valid point. The article is not without flaws. Thanks for your reply!

[ Parent | on HN ]