But the people who can easily afford the insurance in Florida can afford the new tax as well. And as an added bonus, they don't have to live in Florida!
But in all seriousness, they all already own homes in Florida.
Just to say the obvious, but gaining muscles gave you confidence. People aren't laughing at your jokes more because you're swole. I mean, I'm sure there is some of that. But with any virtuous cycle, it's never just one thing that makes a positive change. It's a reinforcing loop.
I've been calling it the "AI argument from misanthropy" but that's way more succinct. Thanks.
What really drives me crazy is how laden it is with negative emotions, and then people pretend it's just a rational assessment of the world. I was told growing up that if you're anxious or negative, it's just because you are smart and you understand how terrible everything is, while stupid people are happy. Seems like a lot of people got a similar message, and now they're shilling AI.
I would replace the word scientists with engineers in that quote. People often conflate the two, but in my experience, scientists tend to be more cautious and there are built in checks and balances in the process (however flawed).
Engineers/technologists tend to have no such guardrails, and are also usually embedded into entirely profit motivated environments, whatever their own values might be.
This sounds like you don’t have much exposure to actual professional engineering disciplines. I’m sure civil, electrical, structural and mechanical PEs would be quite surprised to hear there are no guardrails on their professions.
I have fond memories of a boss who was an actual, licensed engineer while the rest of us were very much normal software devs. Boss was pretty chill except when someone someone suggested we should be called "engineers" rather than "developers", at which point they said "if you guys were building bridges, people would be dead." (I don't think all software needs to be built to rigorous engineering standards but man... I think about that line a lot.)
I prefer the term "software developer" and that's what I use when I don't need the prestige of the term "software engineer". It's disadvantageous for organizations to do that with actual job titles, though.
Absent US government intervention to codify the term "engineer", probably the only way out of the "engineer" trap is through further title inflation, where the developers all become "vice presidents". :)
Yeah, it's 100% the better term. We've got rules against using engineer here in Canada though several companies I've worked for have called me an engineer. Apparently Professional Engineers Ontario sometimes goes after people for calling themselves engineers but I've never heard of it actually happening, and I don't know that they have any real teeth given that the places I worked that called me an engineer were Canadian-owned. (In fact, the only place where they checked if I could use the title was the one multi-national. Go figure.)
In my experience “engineers” and builders are often quite “conservative” and really don’t like pushing the envelope, and they often only do it under protest.
The most famous example may be the perpetual war between architects and engineers/builders.
Researchers need to go wild and sometimes far off-the-rails to increase the odds of coming up with something that is both new, and potentially popular enough, if they want the option to attract marketers who can only thrive on mass-consumption.
With luck, one out of 100 inventions will show promise on those points.
There's always a lifetime wake where the overwhelming vast majority of the work remains undeployed no matter what. The more undeployed milestones and inventions that some scientists have under their belt, the more accomplished they often are whether anybody knows it or not.
OTOH, equally active engineers more often need to have most of their time engaged in actual deployment of some kind or another, otherwise not as much progress will be able to reach as many people that could benefit. So many times nothing would be accomplished without a long-term focused engineering effort once an objective has been identified. But it can be hard to stop a train when it's already coming off the drawing board at full steam.
It does seem a lot more likely for a judicious researcher to cast off some major progress in what could very well turn out to be an unsavory development, such as likely misuse, even if it could be marketed as the most popular thing they have so far. Just add it to the pile of other things that best remain undeployed. There's plenty more where that came from, and the best is yet to come.
Perhaps popularity alone is not always the best measure of progress.
I actually originally wrote "technologists" but thought that the word sounded kind of odd. Now I realize it better captures what I was trying to convey.
Honestly, scientists too.
I did 10 years of research after deciding that it was not worth it. There is a vast amount of research with no direct application that gets published under the assumption that more knowledge is always better, but in my experience scientists rarely question the usefulness of their research (because most of the time, they find it interesting, which is motivating enough).
Granted, I am talking about harmless subjects, but there is also the dimension of resource usage that almost no scientist considers (the amount of plastics and chemicals used in biochemistry and cell biology is... concerning).
Ok, but try the same argument with sedentary societies. Those seem "superior" despite all the negative side effects, right? But here comes one of a number of steppe nomad tribes to show up and decimate their "superior" neighbors.
The vast diversity of human societies refuses any kind of rigid hierarchy of development. There are many branching paths, and no paradigm wins for long.
It's so funny when technological progress guys encounter YIMBYs. They can't even perceive that somebody would have a criticism of the impact of a technology on one's lived environment. "But, history is one big game of Civilization, and we replaced the little horses with tanks? What do you mean you don't like it?"
Technology-brain is confusing because it's usually pretty well-educated people who presumably read. There are so many examples of technological adoption that has made our lives worse. Cars and social media are easy and widely obvious examples.
I've noticed that AI has caused this narrative to become more popular. "Nothing is original anyway, so why bother?" That's pure cope and you know it. A deep insecurity masked as bold truthtelling.
I think you're right, the ease in which AI can do task that we previously considered unique to human creativity does force us to further rethink and acknowledge how creativity is in a large part about "remixing" prior works, although of course we've had discourse about this for at least as early as Richard Simon's 1678 "Critical History of the Old Testament", which identified it as being a remix of earlier sources [0].
We talk a lot about the risks of AI in schools, but those same risks apply in any learning environment.
I recently started a new job and I find that AI is making it so much harder for me to onboard. I am adjusting to my role much slower than my peers who are using AI less. I am coding in a language I am unfamiliar with, which makes the lure of vibe coding stronger. I am at least skilled enough to recognize when Claude gives me an answer that either makes no sense or is unnecessarily verbose. But the more time I spend asking Claude to write code, the less I feel like I'm developing the skills that the job requires. Plus, when I submit a PR, I lack the necessary confidence in my own work, which just feels bad.
Honestly, another part of this is that I'm asking Claude to search through Slack and docs for answers to questions when I should just ask another person. The AI is feeding my social anxiety, luring me into avoiding human contact that I know will be good for my understanding as well as my general need for social interaction.
That all sounds like I am absolving myself of responsibility, but I think it's important to point out how a given technology is especially addictive for a certain type of person, and traps them in a negative behavioral cycle. If I hold off on relying on AI now, I suspect I can grow in my skills to the point that I can delegate tasks to AI that are rote and easy for me to verify their results. It feels challenging, but it's necessary.
I'd suggest going the route of having Claude teach you what you need to know. How do I uppercase this string? What's the best way to tackle this problem? Is there a standard way to do this thing? Then you learn along the way. You don't have to use it as a search engine, just ask it what you need to know in the moment. It will shake it's token chains and give you something that's useful, especially for a beginner in the language. This way you can implement your plan of growing your skills and then starting to delegate to it later.
I've been doing this, and it's a nice balance for me. Having Claude code things when you don't know how to evaluate it's code seems like madness to me, but I guess I'm in the minority on this.
> How do I uppercase this string? What's the best way to tackle this problem? Is there a standard way to do this thing?
I strongly believe that it's better to just take a couple week of slow times and read a good book about the technical matter you're dealing with. Having bite sized answers isn't a good way to be proficient.
No, and if you aren't going through mental effort, your brain isn't learning. It's just being briefly entertained by the information. You need practice and association building to actually build knowledge and skill.
It is the worst time for the apprenticeship system (internship). everyone expect you to ship fast and good with ai, but you can barely have the time to pick up any skills during the fast iteration.
But in all seriousness, they all already own homes in Florida.
reply