Re: Just maybe?
Totally agree. But the agile methodology is now used as a bible. It's *the* way to run projects. Thou shalt have daily worship to the PM. Let there be sprint retros, and thus the project will be delivered from evil.
12 publicly visible posts • joined 11 Jun 2020
I often ask myself if developer productivity has improved. I'm not sure it has. Everyone is now obsessed with using containers everywhere. In the past I was waiting for my code to build and deploy to a web server. Now I'm waiting for code builds, plus Docker image rebuilds.
Totally agree there re: streams. They have their place, but sometimes people get obsessed with using them.
I once had a technical interview, where a piece of code I'd written used an enhanced for loop and it worked perfectly. However the interviewer was hell bent on using Java 8 features and asked me to convert the code segment to use a streams approach. Ok so I made it use a foreach loop. The resulting code was harder to read (IMO), and had to be hacked around to make it work.
Just because the language provides these features, doesn't mean you *have* to use them.
And yes, functional programming is the current fashion, so chaining stream methods together on one line is the popular style. Does it make code more, or less readable. And how do you debug that when it doesn't pop out the correct results?
I notice they added 'Records' in the latest raft of features. For when you just can't be arsed to type a class. Java is now chock full of these keystroke saving features. Aside from the fact that most half decent IDEs will literally write code for you, it's almost as if they are striving for the language to be much slimmer. But unfortunately they have too much baggage.
<I'm off to write some Go code..>