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

Is all of it one chip? Seems like a waffer with several at least?

Those are scribe lines where you usually would cut out chips which is why it resembles multiple chips. However, they work with TSMC to etch across them.

Clean your desktop and home folder first and then preach to me for my physical surroundings, bro.

It's real and I've been telling all the people around me who get vested in this sort of exponential growth, to be very wary of the impeding burnout, which spares no soul hungry to get high on information. getting high on information is now a thing, it is not cyberpunk fiction anymore, and burnout is a real threat - VR or not. perhaps one can burn out on tiktok these days.

I noticed today that even with less sleep, I'm more energized than usual when I stayed up late but not consuming information.

use SublimeText, it is perhaps faster now than the stock Notepad

As much as I used to love Sublime, the version switching caught me out which burned me a bit, even if admittedly my v2 key lasted an unreasonable time through the version 3 beta, but I don't want to risk buying a v4 key without a clear roadmap of when they might switch to version 5.

They changed how that works. Licenses are no longer tied to version, you get 3 years of updates no matter what the version is.

It’s $99 for something that is almost 5 years old at that point.

I can definitely vouch for this! I've been using it for many years and it's been essentially the same the whole time: fast, lean and working on all operating systems.

Combined with LSP I find it to be quite a good IDE too. Handles extremely large source trees quite well.

it intensifies work, and shortens time to burnout, which... like nobody still talks of. ingesting these huge slops of information can be super tiring.

> it intensifies work, and shortens time to burnout

This is most likely correct. Everyone talks how AI makes it possible to "do multiple tasks at the same time", but noone seems to care that the cognitive (over)load is very real.


IME you don't even have to do multiple things at the same time to reach that cognitive fatigue. The pace alone, which is now much higher, could be enough to saturate your cognitive capabilities.

For me one unexpected factor is how much it strains my executive function to try and maintain attention on the task at hand while I’m letting the agent spin away for 5-10 minutes at a stretch. It’s even worse than the bad old days of long compile times because at least then I could work on tests or something like that while I wait. But with coding agents I feel like I need to be completely hands off because they might decide to touch literally any file in the repository.

It reminds me a bit of how à while back people were finding that operating a level 3 autonomous vehicle is actually more fatiguing than driving a vehicle that doesn’t even have cruise control.


"It reminds me a bit of how à while back people were finding that operating a level 3 autonomous vehicle is actually more fatiguing than driving a vehicle that doesn’t even have cruise control."

this is huge insight and very philosophical in relation to the question of "which skills shall we retain still, and is this a general threat (perhaps not) to majority of traditional skills?"


For me it's the volume of things that I am now capable of doing in so much shorter amount of time - this leaves almost no space for resting but incurs much more strain on my cognitive limits.

> But with coding agents I feel like I need to be completely hands off because they might decide to touch literally any file in the repository.

Why not just have another worktree?


So the thing about task switching is, everyone is bad at it. And the studies indicate that people who think they’re good at it are even worse at it.

I was responding to:

> It’s even worse than the bad old days of long compile times because at least then I could work on tests or something like that while I wait.

To me it seems like the exact same context switching situation that it always was.


Not exactly maybe.

Different worktrees can still lead to possible merge conflicts later. This may get messy.

Working on tests during compilation seems like a more separate task.


If I’m writing tests and implementation for the same problem, there isn’t so much context switch. Same business domain, same domain model, same API, same contract and invariants. I’m just switching between taking the measurements and making the cuts. Which is a smart thing to do anyway because you can accumulate a lot of need for rework very quickly if you make a bunch of cuts in a row without stopping to confirm you’re making them correctly.

> it intensifies work, and shortens time to burnout

On the bright side, that would address the employability crisis for new grads.


well smart oldies have learned to discern among skills that need focusing on and retaining and those that dont. perhaps with live we learn to navigate information better, given also constraints imposed by (with time) failing organs. so i guess the whole thing about a grownup is really that they be better strategists, and executives than children. everything else pretty much overlaps unreasonably often.

so newgrads burnout faster imho, is all im sayin.


Would it though? If you have 10 people on the team now doing the work of 20, 30, 50, ...

Once they get relocated to asylum, you need to replace them with fresh meat.

After the economy of attention, no things enter the economy of trust.

What I usually do in 2026 is copy the code and article and have Claude clarify the unclear parts for me. then is ok.

But that's sort of the author's job: if they wish to publish an article on a topic, they should make it both comprehensive and comprehensible.

but I cannot hold authors that I've never met accountable, and it is not a job, when you do it in your blog. it is utter nonsense to call writing personal notes in public a job. it is as much a job (and bears similiar responsibility) as is the opensource work, and we've had hundreds of discussions reg. how the author should not be responsible for shortcomings of his public work, when it is done without contract or other formal agreement to do it (even for free).

work != job

so really, what are you talking about? I'm discussing the means to expound on given knowledge - limited, or oversaturated - and you are changing the topic to "is the author responsible for work done in his spare time".

lets focus, people.


It’s early February. Have you really read so many articles you couldn’t understand in one month that you have a “usual” way of dealing with it? You should consider whether you would benefit from curating your sources better, or if use of AI as a crutch has already decayed your ability to understand stuff on your own unrecoverably…

try curating the hacker news commentary when there are 800+ texts. no, really, what the hell are you talking about? having someone figure the insights that are relevant to oneself, among 800 texts, DOES solve a problem, which otherwise is unsolved unless you do it manually. which, the manual thing, as we all know, does not necessarily result in significantly better insights.

and yes, my job is to read technical slop dusk till dawn, and I care very little who wrote it, but whether it is relevant to my research. its a lot of reading, it causes me pain, so OF COURSE I would love to short cut it somehow, given most of it is slop anyway - no matter if its human or synthetic slop.


Why does it even exist, this MSN page, which is ridden with nonsense...? I don't get it.

Because it's probably extremely profitable, unfortunately. I have seen many of my coworkers click on the headlines and ads on the MSN homepage when bored at work.

I resonate strongly with this story. I’ve seen three people teams get in one month where SAP could not in year, and also let and witnessed incredible number of total fakers in SaaS enterprises.

Big corpo may be too big to fail, not so sure about their whole cohort of partners and fakers.


Perhaps not, and it is indeed not unwise from Apple to stay away for a while given their ultra-focus on security.

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

Search: