Hacker News Reader

There is challenging for the wrong reasons then there is challenging for the right reasons.

You will want to make sure you work on things that are challenging for the right reasons.

I've heard this described as inherent complexity versus accidental complexity.

Inherent complexity (due to difficult real-world constraints) is fine. Accidental complexity, like that caused by overcomplicated tools or architectural decisions, just feels bad.

And then you have weaponized accidental complexity, aiding cv-driven development and vendor lock-in (which are really the same sort of thing).

Hey, leave next.js, react router and vercel alone!

Why do I enjoy writing shell scripts then?

That is another axis around quick feedback loops. A shell script comes with a repl you don’t even need to invoke!

There is a threshold where you can still make things work right despite the accidental complexity, and some enjoy that challenge, but beyond that threshold you just have to accept that things won’t work right. CSS is very often beyond that threshold.

Then some stakeholder just doen’t like a thing for silly reasons and never can anyone always be happy - for cheap at least

Reply on news.ycombinator.com