I have always assumed that, being in a larger vehicle that is bright red, people would be more likely to spot the vehicle from further away, notice it out of the corner of their eye, or that I would generally be MORE visible to other drivers.

I'm sure the correlation insurance companies are looking at is that the driver's of red vehicles are the cause of the higher accident rate.

Either we stunt the models to the point where they are not useful, or we allow things like this to seep in and create one of the most insecure concepts the internet (and maybe tech as a whole) has ever seen: a robot that can be tricked.

I’m not sure I get the pushback on the robots file. Shouldn’t the robot prevention be ON by default?

I wish I was kidding but I work with people doing this. I think it’s going to be a real mess in the future, we’re going to completely disintegrate the critical thinking portions of our brains.

Fortunately, I’m seeing more articles about this, some of us are noticing and raising the flag asking “is this a good idea?”

Loved to use fancy words, speak at a “conceptual” level. Unfortunately it was mostly just tech mumbo-jumbo and he couldn’t actually back it up with real work - but I wonder if that’s why Claude does it. Makes it seem like a higher power, hand wavey abstractions that “seem” correct but don’t actually need to be rooted in truth or detailed.

“That’s exactly the type of seam we need to prepare for in a prod-like environment, if this change lands in the data plane, we’ve effectively shut down the load bearing critical path that was needed. It’s not over-engineered; it’s the right thing to do.”

Thanks Claude, whatever that means.

Also have read the term “seam” dozens of times by now, when previously I saw it maybe once or twice over years. Very abstract term.

FWIW we are a smaller company and we had a user run through 500$ in a DAY. Had to put a stop to that. I'm hopeful that our company gets better at asking what the ROI is, what is being built, how much time is it taking, etc... It's no big deal when it's 20 / 100$ a month - but if the prices end up higher we will need to start seeing some returns other than "I feel faster".

The editing is what really makes it useful - instead of wasting paper after writing some scratch math, I can just select the area and clear it - giving me a fresh page with all the info I already had on there. It's been pretty great for my use case, maybe a little expensive - but I've used it every day so far.

It is 1 level up from traditional pen + paper IMO, editing / moving things around / bulk erasing is a major upgrade that I didn't know I wanted.

Many folks have touted the "calculator" similarities as an argument, saying it's more of an efficiency gain / productivity enhancer. To me, LLMs are far more involved than this. Now, unknowingly (or knowingly), people are offloading the problem solving portion of small tasks.

- Creative Writing (Claude, make this email sound more professional)

- Coding (Handle this small logic bug for me)

- Note Taking (Generate a summary of this meeting recording)

- Strategy (Set up a roadmap for X project) and many other areas

- Design (Give me a powerpoint for a stakeholder meeting)

- Personal Life (Find a restaurant I can take my wife to for our anniversary)

Many people underestimate how many "simple" tasks required creative problem solving abilities, and we're actively handing more and more of that over to the thinking machine.

Perhaps it's human nature to give this up, and maybe it's in our best interests - but this is the first time I've ever seen people stop thinking for themselves en masse. Interesting times ahead, IMO.

I notified them and they said that this was noted, skipped, and they didn't believe it was an issue. Worst case scenario an attacker could... Pay for someone elses order, if this happened the attacker would be found by their payment details. Likewise on the payment screen they only see the order's total, nothing about the customer, nothing else about the order, just the total. So - I'm not sure. Maybe they're right?

I just shrugged. I would've patched it, feels like poor design and is easy enough to fix - but I couldn't really argue other than to say it felt sloppy.

Going to PAY with the QR code feels a little worse. I went out with some friends and I planned to pay cash, the waitress came over to tell us all that we should pay using the QR code on our receipts - missed me, and I had to wait 5 minutes to let them know I was using cash. My friends didn't have much trouble, but we're all younger folks so we are used to pulling up Apple Pay or whatever. I imagine some people do not enjoy that experience.

I will say that there is this inherent disdain towards automated systems, and I feel it's warranted - to a degree. Some experiences are improved with automation, others are stifled. Sometimes we just want to talk to other people who understand our problems.

Maybe I'm wrong. Maybe AI Natives will be faster in the end and can build / do more, or building software really is a dead field - but I noticed that I was losing my brain and had to get back into the seat.

There are definitely great use cases for agents - but I think a lot of us aren't flexing our brains anymore and, even worse, some devs believe they are. I urge every developer to put Claude down for a day/week... see how well you can do in the "old" ways. It'll still be here when you get back, but my guess is it'll be a rude awakening.

Consider some software that was written by AI purely using markdown files. The spec was sufficient enough to classify all of the business logic, conditionals, etc... You might even end up creating "loops" that tell AI to do something over and over again. Some markdown files become standard, repeatable "functions" that are to be followed EXACTLY (determinism). Some markdown files become assertion tests. Heck, the markdown file might eventually invent some kind of "typing system" so that you know when you're working with the person "class", it's always going to have the same facets.

I love the concept of it going in this direction - we already had plenty of languages to tell a computer what to do, we've just generated MORE text at a higher level and made it less deterministic.

Just to clarify, I don't think it's likely that this is the end result, but it sure is funny to think about.

I fully expect the air to last me at least another 6 years or so for my use case. The thing is a beast.

Compare this to a Dell laptop I bought when I started college, that thing was 850 dollars and died on me within 3 years. For Apple, I could justify spending more (maybe even 20% more) considering both Apple computers I’ve had feel extremely fast. The only reason I dropped the 2019 MBP was battery fatigue (and I probably could have repaired it for 100$ and gotten another 3-4 years out of it. But the new air was just too attractive).

(Joking, mostly) but we did see this with Wordpress, Bootstrap, etc. the masses converge on simple web experiences because it’s pretty easy to get something that “just works”.

If I give an agent a sufficient spec, and it can one shot it, I imagine we won't need to loop, especially if we assume the tech is going to meaningfully improve in the coming years. In 5 years, "make no mistakes" and "add tests + review this code" will be baked into the agent or completely unnecessary, right?

Maybe I'm out of the loop.

I agree with your overall sentiment. Paying for "Claude Mini" doesn't get you "Claude Maximos".

However, the overall precedent that the companies have set is that if you pay for the top tier subscription, you get the top tier model. That's not true any more.