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

Not having so many plug-n-play abstractions that you’re so strongly encouraged to use to “not re-invent the wheel”. The problem in my mind is that the abstractions leak all over the place, but we stop caring.

Pushing off compute to the browser because it’s cheaper, nevermind the cost to non-powerhouse phones.

Avoid putting any thought into optimization because compute and memory is cheap. Nevermind that you’ll have to do a complete re-write when a few dozen 600+ ms microservice responses results in 20 second page loads.

Store all the things! You might need them someday, after all. GDPR what?

I work with developers who think that DB migrations are “of the devil”. As a result, they have pivoted to use the RDBMS as a rudimentary k/v store and create the relational data structures in memory. All they need to do is pull a few dozen GB of rows from the DB with every container restart.

So, yeah. I miss having fewer abstractions; having more constraints. The software seems somehow nicer through the CRT-colored lenses.



> Not having so many plug-n-play abstractions that you’re so strongly encouraged to use to “not re-invent the wheel”.

Inventing the wheel, rather than re-inventing it. There was a lot more "doing something for the first time" and less "doing something for the Nth time, slightly differently".

(Or so it felt to me. But there was still a bunch of "doing what the mainframe people did a decade ago, but doing it badly". Still, it felt different.)




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

Search: