it's at least as much about the control you have over what you do. And software developers these days have little say in what apps they build. "More than anything, what bothered me is the feeling that my work doesn't matter one way or another," said one of my friends before he quit his programming job. He continued, "You get into software thinking you'll build cool things, but instead, it's about jumping through hoops for business school people with bad ideas."
Isn't this the whole point of agile programming? Isn't this what the field wanted as a majority for a while now? Like, I remember learning about agile programming for the first time and thinking "So, this puts all the burden of making things and making things work on the programmers while all the power of having oversight and decision making goes to the non-programmers while the programmers help the non-programmers figure out what they want or do." Like, I know waterfall is almost considered a bad word at this point, but there's a reason for some of that. Part of me feels like if you've gotten into programming within the last 4~5 years not knowing that agile programming is, that's on you. That's not to say crunch is acceptable or humane or people aren't ever treated badly. But this is the state of the industry currently. The idea of going into the industry with expectations of anything but constant sprints, managers telling you what and how to program and under appreciation is naivete at best, willful ignorance at worst.
Correct me if I'm wrong but... (Score:1)
it's at least as much about the control you have over what you do. And software developers these days have little say in what apps they build. "More than anything, what bothered me is the feeling that my work doesn't matter one way or another," said one of my friends before he quit his programming job. He continued, "You get into software thinking you'll build cool things, but instead, it's about jumping through hoops for business school people with bad ideas."
Isn't this the whole point of agile programming? Isn't this what the field wanted as a majority for a while now? Like, I remember learning about agile programming for the first time and thinking "So, this puts all the burden of making things and making things work on the programmers while all the power of having oversight and decision making goes to the non-programmers while the programmers help the non-programmers figure out what they want or do." Like, I know waterfall is almost considered a bad word at this point, but there's a reason for some of that. Part of me feels like if you've gotten into programming within the last 4~5 years not knowing that agile programming is, that's on you. That's not to say crunch is acceptable or humane or people aren't ever treated badly. But this is the state of the industry currently. The idea of going into the industry with expectations of anything but constant sprints, managers telling you what and how to program and under appreciation is naivete at best, willful ignorance at worst.