Hacker Newsnew | past | comments | ask | show | jobs | submit | djeastm's commentslogin

That's a generous interpretation.

I see it as just preparation for selling the space. After a few months of "tips" they go to companies and say, "hey, you know those tips we have in our PRs? You can be in every 10th one of them for X dollars?"


I could totally see them priming the ad engine; next step would be "PR tips get viewed by X million eyeballs a month; how many do you want to buy?"

Right or wrong about this, none of us can do much about it at this point. The die is cast. I guess we'll just wait and see.

Same here. Knowledge is being commodified.

> Knowledge is being commodified.

Already was well before AI, the difference now is that a few big AI providers risk becoming the ultimate rent-seekers that will increasingly capture all of the value of that commodified knowledge whether the original knowledge generators want that or not. There is no opt out, everything will be vacuumed up into the machine mind.

This will almost certainly lead to vastly increased amounts of wealth inequality (on top of the already unsustainable levels we have today) and possibly a very messy societal disintegration (this is theoretically avoidable, but I am not convinced it is practically avoidable given our current socioeconomic/political realities).

Bright future ahead!


Industrial-scale plagiarism. A form of copyright-laundering only available to big actors.

OG feudalism involved owning knights and horses and armor and grain production; techno-feudalism involves owning all ideas

They don't own ideas, but they own the land we build on and the means of production.

>We should endeavor to craft experiences

It'd be better if we all turned this tech off and went to be with other people.


Any thoughts on what the next generation of software devs is going to look like without as much manual experience?

When C arrived, programmers wonder how software devs would look like when they won't have assembly experience.

Then the same happened with languages that managed memory.

And with IDE that could refactor your code in a click and autocomplete API calls.

And with Stack Overflow where people copy/pasted code they didn't understand.


And over and over time proves that, when you need it, ASM or C or generals system knowledge was handy. One example, I am not a "Windows" or "NT" guy, mostly working in various Unixes and Linux in my professional career. I had a client who had battered every resource trying to fix some horrible freeze/timeout in their application. So I rolled up my sleeves, first search " is there dtrace on windows", found some profiling tools, found the process was stuck in some dumb blocking call loop, resource was unavailable, and the rest was history.

So yeah i mean - who cares how it works - but also if you have experience in how things _do_ work you can solve problems other people cannot.


Sure, "it's handy" and once every few years you encounter a bug where ASM or C knowledge is valuable.

Yet most programmers nowadays can't write ASM or C and still manage to produce useful software.


I reckon there's a limit to how long this abstraction can go on before not understanding underlying mechanisms will seriously hamstring you.

I think we're a long ways from that.

But with that said, those who learn the underlying mechanisms will always be able to solve more problems than the folks who don't. When you know the lower pieces, your mental model tells you when and where the higher level pieces are likely to break. Legit superpower.


> But with that said, those who learn the underlying mechanisms will always be able to solve more problems than the folks who don't

I would define that as being "seriously hamstrung"


Well how many times have we seen the S3 bucket set to public while the customer data piles up and leaks out to space.

It started before that. When assemblers came out, (some) programmers worried about losing touch with the machine if they didn't have to know the instructions in octal.

Honestly, I think it will look pretty much like this one. There’s a lot of manual experience that the current generation doesn’t have.

For example, I haven’t racked and cabled a server in over 15 years. That used to be a valuable skill.

I also used to know how to operate Cisco switches and routers (on the original IOS!). I haven't thought about CIDR and the difference between a /24 and a /30 since the year 2008. A class IP addresses, how do those work? What subnet am I on? Is thing running on a different VLAN? Irrelevant to me these days. Some people still know it! But not as many as in the past.

The late Dr. Richard Hamming observed that once a upon a time, "a good man knew how to implement square root in machine code." If you didn't know how to do that, you weren't legit. These days nobody would make such a claim.

So some skills fade and others rise. And also, software has moved in predictable cycles for many decades at this point. We are still a very young field but we do have some history at this point.

So things will remain the same the more they change on that front.


> So some skills fade and others rise. And also, software has moved in predictable cycles for many decades at this point. We are still a very young field but we do have some history at this point.

And there'll be a split too... like there's a giant divide between those mechanics who used to work on carburetors and the new gen with microcontrollers, injection systems, etc. People who think cars are 'too complicated' aren't wrong, but for someone who grew up in the injected era, i vastly prefer debugging issues over the canbus rather than snaking my ass around a hot exhaust to check something.


And to take the analogy even further, I'm sure there will be a subset of people who develop really strong opinions about a particular toolchain or workflow. Like how we have people who specialize in 70s diesel trucks or 90-00s JDM sports cars, there'll likely be programmers who are SMEs at updating COBAL to Rust using Claude.

yup. I do early bosch EFI and K-Jet... thats what I know!

I am pretty sure network knowledge and all those things are still necessary for people running data centers and really big computers and I imagine we will build a lot more of that.

Also anyone making a homelab has to know these stuff.


I seem to recall a lot more hype for these companies than people saying it won't work. You seem to be cherry picking from the naysayers of the time, but not the broad consensus.

> fancy brick

If we're going to be reductionist we can just call humans "meat sacks" and flip the question around entirely.


They usually don't put it like that, though. It's usually just "please respect our privacy during this difficult time", etc.

Heartbeat should be set to be a cheaper model.

I'm using lite.cnn.com while it still exists

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

Search: