> I’m against attaching bullshit marketing labels to good practices and making them a cancer on the project (cough devops, agile cough). There is absolutely no

> I’m against attaching bullshit marketing labels to good practices and making them a cancer on the project (cough devops, agile cough). There is absolutely no bullshit in replacing waterfall's big upfront design and risk-prone one-shot dev project with an iterative process where at each cycle you reevaluate your course and your planning, always based on developer feedback. There is also absolutely no bullshit in avoiding the mistake of artificially separating the devprocess into sysadmin stuff and dev stuff, and actually get developers directly involved and more importantly become mindful of the reality of everyday operations. Portraying agile and DevOps as bullshit is clear telltale sign you are completely oblivious to the issues software developers face on a daily basis, and how agile and DevOps help solve or mitigate them.