Low effort writing. Medium.

This is funny on all levels:

• The initial motivation for the heinous act;

• How the plan was implemented;

• The reaction to the plan.

Yes, i was part of the cult in my early days as programmer. I would endlessly create abstractions over abstractions. But the whole madness started for valid reasons.

Im the early days of Java on the web, you had servlets and JSP. Servlets were miserable to write, and JSPs were basically the java interpretation of having a PHP. Those were the days before JSON and yaml, when XML was king.

So people wanted to abstract their way out of JSP and XML, so they created layers to isolate the nasty parts and make it easier to write actual Java code. So a few ideas emerged/frameworks: ORMs, EJBs, Struts, JSF, template frameworks, and finally Spring which was the lightweight one, if you can believe it. A lot of those ideas coming from the Java world were exported into various other languages in a selective ways.

People experienced with various patterns and frameworks. Eventually Spring won, and then Spring started to use annotations, JSON became more popular, etc., the code became less and less verbose.

Some Java developers never made the mental jump and are still creating huge piles of abstractions because this is what they’ve learned from their seniors.

Yes it does, the only parts where Java doesn’t shine are usually some advanced features that are nightmarish for people who are building tools and libraries:

• The type system is so 90s and it’s kept like that for backwards compatibility.

• Generics having type erasure is again an improvisation for the sake of backwards compatibility. It makes writing generic code in conjunction with Reflection painful.

• The lack of control for the memory layout. I mean in most cases you dont need full control, but there are use cases where it’s literally impossible to do optimisations that are easy to do in C/C++. You must have faith in the JVM and JIT.

• Integration with native code is cumbersome.

Other than that Java is fine for most backend work you need to do, except probably for Real Time Processing apps where every millisecond count, but even there there are ways.

You use Java not for the languages itself, but for the tooling and the ecosystem.

For personal projects and prototypes i believe it’s fine, but when you consume the electricity of mid-size countries just because you prefer to write your production code in convenient languages don’t lecture others about ecology and climate change (i am not refering to you).

That’s a possibility.

Developers should go back writing efficient code in lower level programming languages to stop wasting CPU cycles for stupid reasons, like not wanting to use types, or something more stupid than that.

It’s a little curse to be remotely passionated about programming and be a programmer nowadays. Some companies make it extremely dull and toxic with all their additional requirements and managerial practices. But there’s hope, there are good companies or teams, and eventually if you stay long enough you will find your place.

That was my case.

The only lesson you need to learn is to make distinction between your interests, side projects and hobbies and the actual work you need to do ar work. If they overlap that’s amazing, if not you need to adapt. You need to give the company what the company wants (so you can get paid), and to yourself what you want, so you can be fulfilled.

It would be C++. Its versatile enough to do everything with it.

They force you think of o(n) and train you better than anything else on how to write your functions (but not how to organise them).

I have around 600 leetcode exercises solved, and there’s a big difference in skill between the person i was before leetcode and the person i am now.

There’s definitely a ladder, for me it was constant work, rather than hard work.

deleted by creator

Great rss feed. Not everything is for me, but i did found some good sources of information. Thank you for sharing.

HN is still a good resource, but I wish spending my time reading what real people have to say, even if i disagree. A lot of articles there are about subjects, or written by “entities” that are not on my radar.

lobste.rs is my favourite hn alternative, but considerably smaller. At least people there are more civil, and being part of the site for a few years made me feel part of community, as i already (virtually) know some of the people there, and appreciate their opinions.

Still, nothing beats the “curation” of content you can achieve by maintaining your own RSS feeds list.

Amazing, you’ve got my point quite well. Added almost everything to my RSS reader.

🍿

I dont think the Dev who has the blog is unaware of DAG, he usually deal with CS stuff, i believe he was trying to make a point.

But who knows what he knows or doesn’t know, i am not his lawyer. In any case, there are a few valid points.

I never understood the hype behind gradle.

Love the metaphor, how the game of life is powered by the sun itself.

I am not saying they are competing on the same niche. I am saying both sites started well, and they transformed into something worse, profiting by their monopoly on their specific markets.

Things will get better the moment your youngest becomes more independent, and sleeps well at night.