In the case of the North Sentinelese, this incident in 1880 might have something to do with their hostility to the outside world.
> After several days, six Sentinelese—an elderly couple and four children—were taken to Port Blair. The colonial officer in charge of the operation wrote that the entire group "sickened rapidly, and the old man and his wife died, so the four children were sent back to their home with quantities of presents".
After the 2004 tsunami, indian government sent helicopters to see if they had survived and they started firing arrows at the helicopter. It's possible that they think the foreigners caused the tsunami.
Telling codex how to program a feature is a much different, much easier type of thinking than back in the olden days of a year ago, when I had to get everything to work myself. I can't imagine that's going to be great for my long-term brain health.
This only holds when you keep the task fixed and compare with and without AI. But because AI changed expectations the difficulty of work we supervise today is much higher. My theory is that AI runs our brains just as hard as no-AI, maybe harder. That is if you want to have high quality outputs, not for slop.
Certainly, AI is allow us to 10x our code, but also 10x our mental work. Steve Yegge calls this the AI Vampire[0] and it does effect us, more so than TV or old school social media ever did.
My father went through a stroke a few years ago, and is now always online. He blames the stroke for his brain fog, but I still feel that the modern day dopamine addiction is a huge factor.
It is possible if you consider madaxe_again's theory(comment here). If the debris just started descending without interruption, there would be no receding.
I clicked an ad for a quote on a shower door, followed the prompts, and gave my # to what seemed like a single company. The phone calls haven't stopped since.
At a few companies I've worked at, they squelch this kind of bug/security breach reporting by immediately making it the discoverer's job to fix the problem and champion it through the system to production, taking on all responsibility if something breaks of course. You only have to go through that once to get the message.
This is standard because after a year of experience, a fresh junior dev is worth roughly twice as much on the open market. Most companies won't give a 100% raise because it would upset the apple cart with other employees wanting similar raises. So the junior dev has to move on to get paid what they're worth.
> This is standard because after a year of experience, a fresh junior dev is worth roughly twice as much on the open market.
My internal Brandolini's Law alarm is ringing loud and clear on this one. Absolutely not. This is only true for the best junior devs in the most competitive markets. From my professional experience, it is very difficult to keep star junior devs. The "gravity" pulling them away is simply too strong.
reply