News for hackers. Stuff that matters.
Re:How Completely Messed Up Practices Become Normal by ryandrake on Wednesday December 30, 2015 @03:50PM (#10814288)
Not sure why you are getting so many replies disagreeing with you. Narrowly-defined roles are indeed the norm, even in the tech world. When I was an "individual contributor" I'd get frustrated with Worst Practices all the time, but was told that I was hired to write code not to change our infrastructure or suggest different product features or improve our testing practices--MANAGEMENT makes those decisions. But even when you get into management, there are always managers above you to limit what you can achieve.

There may be awesome companies out there where anyone is empowered to just go fix some practice that's not productive, no matter where they are in the org chart, but those companies are few and far between. I'd love to see one.

Re:How Completely Messed Up Practices Become Normal by kyllo on Wednesday December 30, 2015 @11:29PM (#10816121)
There may be awesome companies out there where anyone is empowered to just go fix some practice that's not productive, no matter where they are in the org chart, but those companies are few and far between. I'd love to see one.

One thing I would consider doing, if I ever start my own company or rise high enough up in someone else's company to implement this, is to give every single employee some sort of discretionary budget to spend on things that make the workplace better. The more experienced and trusted you are, the bigger of a budget you get. I think this would go a long way in fighting the learned helplessness dynamic.

Re:How Completely Messed Up Practices Become Normal by yekim on Thursday December 31, 2015 @11:08AM (#10818151)
This is a very interesting idea. Have you, or anyone else on HN, ever seen this in action? I would LOVE to hear stories about this, either successes or failures.
Re:How Completely Messed Up Practices Become Normal by mike_hearn on Saturday January 02, 2016 @08:39AM (#10826148)
It's called 20% time and it works OK. I always used it when I was at Google, although most people didn't.

20% is not specifically for "improving the organisation" of course. It's most famous on the outside for the new products it led to, like Gmail. But actually most 20% projects were small internal things intended to smooth the rough edges off a particular tool or process, or to improve the company in some way. If the particular bee in your bonnet was a type of bug that cropped up frequently in other people's software, making a linter to spot it and driving adoption through the organisation would be a good 20% project, for instance.

Re:How Completely Messed Up Practices Become Normal by joe_the_user on Wednesday December 30, 2015 @05:17PM (#10814739)
Part of it is vinceguidry makes something of a false distinction. Either fight the system and solve X problem behavior or just accept it and don't think about. A third option is simply investigating classes of behavior of this sort and learning something from them.
Re:How Completely Messed Up Practices Become Normal by calinet6 on Wednesday December 30, 2015 @09:43PM (#10815819)
I really disagree, strongly. It takes time and perseverance, but you can spread better ways of working.
Re:How Completely Messed Up Practices Become Normal by Illotus on Thursday December 31, 2015 @02:12AM (#10816635)
The job would really need to be worth it to work against pushback from above.
Re:How Completely Messed Up Practices Become Normal by calinet6 on Thursday December 31, 2015 @12:31PM (#10818584)
That part's true. It's probably almost always easier to find a better environment.