4 ms·

I stopped reading at "Agile had a great run in it’s youth by taking on some obviously bad practices such as 'Waterfall' software development." Nothing about wa

I stopped reading at "Agile had a great run in it’s youth by taking on some obviously bad practices such as 'Waterfall' software development." Nothing about waterfall is obviously bad. It's how most engineering projects are done. Heck, it's how most projects generally in the world are done. There's a reason it took a long time to move away from waterfall. It solves obvious problems and meshes with how the rest of corporations typically operate. In fact, with software delivery methods which were dominant back then, agile probably would have completely failed. --- In the end, I ended up reading the full piece. One doesn't get much more oblivious and buzzwordy than this: > We are now more squarely in the age of Microservices, Mobile first, Polyglot, post-Java JVM languages, GitHub, Docker and the emergence of a world being eaten by Software. How is this piece on the top of Hacker News? This piece reads like it was written by a marketing consultant with no idea what these terms actually mean or how software is actually built.

fuck_google 11y ago
The waterfall model (of software development) wasn't even originally (by Herbert D. Benington in 1956) meant to by applied in a strict top-down fashion, but in an incremental and iterative fashion and by making use of prototypes, which has probably always been clear to everyone except clueless managers with no software engineering background. http://sunset.usc.edu/csse/TECHRPTS/1983/usccse83-501/usccse83-501.pdf http://sunset.usc.edu/csse/TECHRPTS/1983/usccse83-501/usccse...
wmonk 11y ago
You are not wrong, it is written by the CMO of Gradle.
emitstop 11y ago
Yeah and I like how he goes in on 'Agile Gurus' and then at the end of the article plugs his continuous delivery conference like it isn't the exact same thing in a different hat.
vorg 11y ago
> We are now more squarely in the age of Microservices, Mobile first, Polyglot, post-Java JVM languages Gradle provides only one language, i.e. Apache Groovy on the JVM, for specifying build configuration info. Before talking about "Polyglot, post-Java JVM languages", perhaps Gradleware needs to eat its own dogfood and provide an API so users can write their build configs in Jython or JRuby if they want. Be polyglot before preaching it.

fuck_google 11y ago

The waterfall model (of software development) wasn't even originally (by Herbert D. Benington in 1956) meant to by applied in a strict top-down fashion, but in an incremental and iterative fashion and by making use of prototypes, which has probably always been clear to everyone except clueless managers with no software engineering background. http://sunset.usc.edu/csse/TECHRPTS/1983/usccse83-501/usccse83-501.pdf http://sunset.usc.edu/csse/TECHRPTS/1983/usccse83-501/usccse...

wmonk 11y ago

You are not wrong, it is written by the CMO of Gradle.

emitstop 11y ago

Yeah and I like how he goes in on 'Agile Gurus' and then at the end of the article plugs his continuous delivery conference like it isn't the exact same thing in a different hat.

vorg 11y ago

> We are now more squarely in the age of Microservices, Mobile first, Polyglot, post-Java JVM languages Gradle provides only one language, i.e. Apache Groovy on the JVM, for specifying build configuration info. Before talking about "Polyglot, post-Java JVM languages", perhaps Gradleware needs to eat its own dogfood and provide an API so users can write their build configs in Jython or JRuby if they want. Be polyglot before preaching it.