5 comments

1

This article is scaring the crap out of me. I'm currently enrolled in a training program centered around agile web development, and I have zero experience working on software in a professional environment (I've written code on my own and in school, but I've never been paid for it). I'm about 3 weeks into it, and so far it's seemed like a decent process to me, but I'm worried I'm learning something that will lead to a crappy work environment. I don't have a degree and was hoping to get a job at the end of this program, and now I'm worried I'll end up stuck somewhere where everything is mismanaged.

Should I take this article with a grain of salt? It seems like he's more upset about bad management than agile (I understand his points, especially about the sprints/emphasis on short term goals, but some of the micromanaging stuff seems like it's more dependent on the manager/specificity of stories than the process), and he doesn't seem to offer an alternative. What are the types of places that I should look for as a junior developer, if places that do agile are as bad as this guy suggests? I'm perfectly willing to slog through some crap to "earn my stripes" if that's necessary, but I'd rather find someplace that allows me to demonstrate my skills and move up without having to deal with too much dysfunction.

2

Take it with a huge grain of salt. I work in an agile office environment and it's been good to me

0

Isn't AGILE becoming old though?

0

Ok, will do. Thanks for the feedback.