Wow, the only one I agree with here is MongoDB (and probably Lombok, I don’t write Java), and that has more to do with their licensing issues than anything technical.
That’s pretty impressive.
Here’s my list:
no-go list of languages - Java, PHP, Ruby, C++ (unless you absolutely need C++ for some domain)
OOP - OOP should be isolated, not forced on every problem; many OOP advocates are dogmatic about injecting it everywhere
waterfall - screw that noise, faster to market + faster feedback is generally better
That’s really it, and I’m totally willing to mentor someone who likes the above if they’re otherwise a good developer.
If you had to write Java you probably would like Lombok if you dislike boilerplate (it can build object constructors, comparators, and field accessor methods via annotation).
Java is boilerplate though. It’s finally getting almost tolerable with static imports, arrow functions/lambdas (whatever Java calls it), etc.
If I had to write Java, I’d push for Kotlin instead, after failing to convince management that there are much better options for the problem they need to solve.
Wow, the only one I agree with here is MongoDB (and probably Lombok, I don’t write Java), and that has more to do with their licensing issues than anything technical.
That’s pretty impressive.
Here’s my list:
That’s really it, and I’m totally willing to mentor someone who likes the above if they’re otherwise a good developer.
If you had to write Java you probably would like Lombok if you dislike boilerplate (it can build object constructors, comparators, and field accessor methods via annotation).
Java is boilerplate though. It’s finally getting almost tolerable with static imports, arrow functions/lambdas (whatever Java calls it), etc.
If I had to write Java, I’d push for Kotlin instead, after failing to convince management that there are much better options for the problem they need to solve.
You can say you’re running Java and write components in Kotlin or Scala, no one knows after the module is published!