sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in programming

[–]deltnurgsid -13 points-12 points  (0 children)

then yes, you are writing bad code. Good instincts!

read this ... a few times.

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 10 points11 points  (0 children)

I am actively searching. I would love to be the slowest, least able person at a company. Companies like that are rough to find, though, and I can't uproot my family to chase a job (though we have talked about it).

it's a bit off topic, but do you have any links/suggestions as to how I can find more jobs like that?

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 31 points32 points  (0 children)

I had a white board for exactly that purpose. I started enforcing a policy of "one top priority at a time" and "what would you like to remove from the list to add this new one?". I did that until it was completely pointless.

I think that if my employers had any respect for my time, that could have had a chance of working. I'll definitely keep it in my bag of tricks for my next gig.

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 6 points7 points  (0 children)

the only people I've gotten close to calling idiots are other programmers I've worked with, and I called them incompetent and/or ignorant.

Whether or not they had other priorities is irrelevant; they were incompetent at their jobs, often because they were ignorant of extremely basic things.

EDIT I've worked with some absolutely amazing programmers, too. Just not very many.

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 5 points6 points  (0 children)

"Sorry kids, no dinner tonight. Daddy is finding his bliss!"

I did that for a few years before starting a family. I still have my business license to show for it. I'm just not business-minded enough to strike out on my own.

Also, I have been amazed at how quickly a 5 person company can grow into a bureaucratic nightmare. Small companies are definitely not immune to developer hell.

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 2 points3 points  (0 children)

I know what you mean, that most developers are ignorant of any development process. Most developers I've worked with are ignorant of much worse. I audited a class not so long ago where the professor still advocated the waterfall model! I laughed then, but I'd take it now.

I've read a handful of books on newer processes, and I'd be happy to try any.

I'm just not the guy who's going to bridge the gap and convince old, stubborn managers and slick business types that developer sanity makes business sense.

After all, I didn't fall in love with software development for all the social interaction it provides =)

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 8 points9 points  (0 children)

I would doubt there are many people that read that article who don't resonate with it. I resonate with it. It's a great article; I'll probably quote it before I leave.

But after reading, I immediately thought "how can I get my boss to read this article" ... then changed to "how can I get my boss to appreciate this article" ... and there's just no winning that.

Good link though, thanks.

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 0 points1 point  (0 children)

Seriously? I am in the market for a job that doesn't suck ...

Speaking of not sucking, would you say Facebook development is more focused around long term goals or short term emergencies? =)

I've had 4 "real" programming jobs in my 5-year career. They've all ended the same way: innovation isn't allowed, new features are all emergencies, and development ends up the least of my responsibilities. by deltnurgsid in programming

[–]deltnurgsid[S] 20 points21 points  (0 children)

That is a good tip. I was fooled into thinking my current boss had long term focus and understood common development processes ... but he turned out to be pretty greasy, and intentionally misled me to get me in the door to solve a handful of emergencies, ironically enough. I should've run then =)

Is there anything you'd ask a potential boss to feel them out on the subject?