Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My web search activity went up a lot with experience. Back in the day, almost all of my work consisted of cranking out stuff in the main language (PHP or Python), spiced up with SQL and occasional web or db server setup. I needed manuals sometimes, but not web searches so much. After the hipster-programming/devops explosion of the early 2010s and my dive into highly optimized heterogeneous solutions, the work switched to whipping up logic in a handful of different languages with incessant fiddling of couple dozen specialized technologies and trying out new ones constantly. I don't need the manuals for the core languages anymore after all the years, but I'm not gonna learn Maven, Gradle, the Big Pile of Java Options and whatever else to set up another data-crunching daemon, in Java this time.

I also looked into freelance jobs lately, and it's pretty crazy there too, especially with the JS' frantic mutations. You'd mostly need a handful frameworks and a whole load of specialized microsolutions, but still: last year everyone was using Ionic, now React Native is everywhere. Web APIs are also evolving nonstop. Chill out for some months, and you're lagging behind the others.

And that's not even beginning to mention compiling other people's C programs under MacOS. Pretty sure that ‘The voodoo of satisfying the compiler’ would be a book of respectable thickness without ever getting into programming proper.



Well-deserved naming of an era: "the hipster-programming/devops explosion of the early 2010s"


Why would you learn Maven AND Gradle? Pick one.


Ahaha, if it were that simple...


Concrete example:

I know gradle, and pretty well at that. I had to learn the basics of maven to develop a Jenkins plugin (at work). Developing jenkins plugins for a long time required using maven. Now there's the option for using gradle, but my recollection was that it was a sub-par experience.


Afaict, everything just relies on Maven and its packages as the backbone. At least, after any sort of Java-dev activity I risk discovering 1.5 GB of Maven's package cache in my home dir.


The maven package format is the defacto standard in the java world. Luckily gradle consumes and publishes in that format too.


Likely because they work on multiple products and don't have the time or authority to move them all to one standard.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: