duck monster posted:

The problem is , Scrum and other Agile methods can be even worse when done half baked or pillaged for bits that make managers happy without the bits that make developers happy.

Like, the other day I had one of the advertising people demand I have some crazy complicated feature done "in a week" . I told him its impossible without doing some fairly gnarly server side work first and he tried to shut me down saying "Spending time on architecture is un-agile, just implement it! If its not done in a sprint its not a deliverable.

I ended up telling him to gently caress off.

Unfortunately this sort of thing is why our back ends now a total clusterfuck. Never given time to actually do it right. Never given time to go back and fix things, and when there is time, its all putting out fires caused by the poo poo pushed on us from above.

The irony is, if we where given time to get the foundations right, all this other poo poo they want to mash on would be straightforward and elegant to implement.

Also: gently caress rails with a rusty fork.