Live data from Hacker News

The Software Crisis

wryl.tech

1–10 of 201 posts

Re: The Software Crisis

#3
The “inscrutable layers unapproachable to beginners” of today are the bare metal low level computing of tomorrow.

Sure I learned with DOS and Turbo Pascal and it was wonderful, but if you ask my teachers who learned with machine code and microcontrollers, they worried that computers have become too abstract and kids these days have little chance to learn the true details.

Re: The Software Crisis

#4
> It's catastrophic when they don't."

I have found this not to be the case.

Very often, an inaccurate mental model is the ideal user state, and it's my job to afford and reinforce it.

But that's just me, and my experience. I'm sure there's a ton of folks that have found better ways.

Re: The Software Crisis

#5
> It seems as if this state of comfort is due to a sense of defeat and acceptance, rather than of a true, genuine comfort.

A whole lot of, say, Bay Area software developer salaries/compensation have genuine comfort.

Defeat and acceptance doesn't come into this, for most organizations: they face little-to-no accountability for security problems or other system defects, so... comfort for the developers.

Re: The Software Crisis

#6
Abstractions themselves aren't a problem; they are in fact a necessity if you want to move anywhere beyond simple bit-twiddling. (Heck, even the idea of software itself is an abstraction over hard-wired instructions.)

The real problem with abstractions is when they are implemented poorly, or have side-effects, or just plain bugs. In other words, we will always be at the mercy of human-produced software.

Re: The Software Crisis

#8
post #2

The ending: "Things can be better. I'll show you how." It's just an intro for clickbait.

The prime criteria for being clickbait is if it is sensationalized, deceptive, or intentionally misleading. This strikes me as none of those things. It's the last sentence of a blog post.

Re: The Software Crisis

#10
post #6

Abstractions themselves aren't a problem; they are in fact a necessity if you want to move anywhere beyond simple bit-twiddling. (Heck, even the idea of software itself is an abstraction over hard-wired instructions.) The real problem with abstractions is when they are implemented poorly, or have side-effects, or just plain bugs. In other words, we will always be at the mercy of human-produced software.

>The real problem with abstractions is when they are implemented poorly, or have side-effects, or just plain bugs.

Which is always, and is why clean maintainable code uses minimal abstractions to accomplish the task. However it seems the default these days has become "pile it on".

Post reply on HN