News for hackers. Stuff that matters.
Re:Signs that you are a bad programmer by bmj on Wednesday October 19, 2011 @04:32PM (#3131924)
The other problem with this is that you never have the opportunity to improve the business, either. Often, management wants the rank and file to improve processes ("because they know them best") but it's hard to find the time for that when you're already working full time (and more) on your deliverables.
Re:Signs that you are a bad programmer by nhangen on Wednesday October 19, 2011 @10:36PM (#3133165)
No doubt. In fact, this is exactly what happened to me today. I'm supposed to have great ideas, but when trying to implement them, told that I need to focus on paying the bills. I don't know how people manage this long-term.
Re:Signs that you are a bad programmer by wnight on Thursday October 20, 2011 @02:53AM (#3133760)
By jumping ship and landing at a less-dysfunctional workplace.

If their business plan doesn't include time for improvements of the processes it's a failure. Leave now. Don't try to make up for their mistakes. They won't see it (positively), let alone reward you for it.

Do good for your old co-workers by recruiting the good ones into the more-functional company.

Re:Signs that you are a bad programmer by bmj on Thursday October 20, 2011 @07:47AM (#3134377)
This. Don't ask me to make process improvements when you are expecting me to be billable 115% of the time.

Fortunately, my group typically allows for 10%-20% of my time to be used for either training (learning new tech/languages) or process improvements (mostly internal tools). Other groups at the company don't have it so lucky, and those are the groups that desperately need improvements.

Re:Signs that you are a bad programmer by AppSec on Thursday October 20, 2011 @01:55PM (#3135970)
Depends on what process you are talking about. If you are trying to improve a process which will hurt the time to deliver of a major project costing a company money, then is it really right to call the company a failure?

Every company/division/organization has priorities and while there maybe inefficiencies in their processes, they maybe a minor cost in relation to the other priorities. (I can't believe I actually just played devils advocate/defended this).

Re:Signs that you are a bad programmer by wnight on Thursday October 27, 2011 @06:49PM (#3165980)
No, I stand by it. If a company doesn't include time for process improvement they have failed. Maybe they haven't tanked yet but the first bend in the road will finish them.

This doesn't mean they have to stop and fix every non-problem, but if there's no time budgeted to fix what comes up the first real problem will ruin everything.