News for hackers. Stuff that matters.
Re:It's about what broke, not who broke it by smallbigfish on Wednesday March 28, 2018 @12:00AM (#16695157)
We don't touch production. We don't upgrade. We are are a X million company we can't afford the risks.

These are some of the excuses they put up.

And then they sit 10 years or more with that bad stuff in there, build even uglier ways around it.

But the time comes to actually do something about. And what was once a one day job becomes "we will hire a consultancy firm to guide us".

Re:It's about what broke, not who broke it by iamdave on Wednesday March 28, 2018 @12:03AM (#16695176)
Are you my coworker? Because you sound like him /s

No really I appreciate risk management but when it cripples your ability to make decisions, innovate or otherwise ACT on information that could help you be a more efficient team and the develoment team becomes a room full of people doing nothing but maintenance for years on end people leave and companies fail.

I just watched that very thing happen this year to my company for exactly that reason. Someone with the word "senior" in their job title was so risk averse that the market caught up, passed us and started eating our lunch.

God help them because I can't do it anymore, and writing on the wall says they'll be closing up shop this fall. I'm out the door for good at the end of the week.

Re:It's about what broke, not who broke it by bigiain on Wednesday March 28, 2018 @01:12AM (#16695470)
Ha. "Outsourcing of blame"!

Outsourcing of blame - as a Service. Where's my VC???

Re:It's about what broke, not who broke it by leoc on Wednesday March 28, 2018 @01:24AM (#16695538)
Accenture. You've invented Accenture.
Re:It's about what broke, not who broke it by bigiain on Wednesday March 28, 2018 @01:37AM (#16695614)
Damn.

(Second thought - did they patent it? "A system and method for reallocating blame and responsibility for business related negative outcomes. The negative outcomes include a plurality of career limiting moves and hastily made decisions." ... )

Re:It's about what broke, not who broke it by StavrosK on Wednesday March 28, 2018 @02:47AM (#16695909)
What do they do, exactly?
Re:It's about what broke, not who broke it by itronitron on Wednesday March 28, 2018 @01:28AM (#16695559)
code rots, whether it is being used in production or not, and should be consistently refactored and updated to accommodate the current status quo
Re:It's about what broke, not who broke it by thinkloop on Wednesday March 28, 2018 @02:08AM (#16695740)
So much so that I don't think "refactoring" should even be a concept - that's what coding is. Every feature, bug fix or change should take into account the new relationships and structure of the model. Leaving refactoring for later is ignoring the fundamental required task of coding.
Re:It's about what broke, not who broke it by iovrthoughtthis on Wednesday March 28, 2018 @05:43AM (#16696540)
Eh, refactoring is distinct from feature developement, prototyping and testing.

They are different modes of thought.

Re:It's about what broke, not who broke it by ashleyn on Wednesday March 28, 2018 @08:22AM (#16697118)
This must be how data leaks/vulnerabilities happen.