3 ms·
Some positive sounding concepts that are used to wreck code and software engineering at a large: - "Get it done attitude": Declare something as done while it's
by partycoder 10y ago
Some positive sounding concepts that are used to wreck code and software engineering at a large:
- "Get it done attitude": Declare something as done while it's still a prototype.
- "Fail early": start with prototypes, end with prototypes. ship a prototype to production.
- "Knowing the software business": know how to trick non-technical people into buying overpriced prototypes made of spaghetti.
- "Product driven", "Feature driven", "Customer driven": implement only what can be sold (features), disregard everything else. e.g: security, scalability, etc.
It is becoming a business model to sell prototypes as finished products.
- sidlls 10y agoI'm experiencing this in my current job, and it's a bit demoralizing. It seems "agile" has been internalized to some extent to mean "start writing code on day 1 or else we're basically doing waterfall which sucks," too.
- partycoder 10y agoAgile is often cherry-picked and reduced to only the parts that people like. Burn-down charts are ubiquitous but sprint retrospectives are not. Then some other parts are conveniently misinterpreted. People misunderstand the role of the scrum master and interpret it as the development team leader... confuse points with hours, or try to measure team performance using velocity... which is the same as measuring a truck driver performance by how much gas they're using rather than concrete results. Everyone claims to be doing scrum correctly, just like everyone claims to be doing git-flow correctly. It's not only cool to be agile and use scrum, it's more like a dogmatic cult where scrum is the ultimate truth that solves every problem in every case and cannot be criticized.