kristianbrigman

The watermark is based on stylometry - and we all know Claude has a style. But it doesn’t have to - everyone knows caveman - so not sure there is enough room in all cases for it to work.

1. Who knows that it will? The point is just that it’s possible.

2. This is one of the (many) side assumptions that are worth discussing.

pg’s argument is essentially 1. Build something people want to buy 2. If you do, you can get exponential growth of people buying it 3. This isn’t inherently immoral.

There are many assumptions around this you could argue about, but he’s directly addressing the original statement (which was also simple, and did not explicitly include the assumptions either).

I agree they are talking past each other - a lot of this is more related to marginal cost differences than anything else imho (basically how leveraged the value of my labor could practically be).

UI/UX is important.

I bought a used Audi etron a couple months ago. Agent was going to try to sell me a service plan and realized none of them apply to electric :) The downstream fanout of the auto industry is huge…

IIRC he did get a lot of ideas from fans talking about their own workplaces …

That's partly because python has a very large installed base, and ease of entry (including distribution). This leads to people running into issues quicker, and many alternative solutions.

Unlike something like Rust, which has much fewer users (though growing) and requires PhDs in Compiler Imprecation and Lexical Exegetics.

Or C++ which has a much larger installed base but also no standard distribution method at all, and an honorary degree in Dorsal Artillery.

But heat = energy, right? So maybe we don’t really want to radiate it, but redirect it back into the system in a usable way and reduce how much we need to take in? (From the sun etc)

Where does the food come from that you have the right to?

NYSE, NASDAQ, but also AMEX…

I had the AI implement two parallel implementations of the same thing in one project. Was lots of fun when it was 'fixing' the one that wasn't being used. So yeah, it can definitely muck up your codebase.

For pet projects, it might be less fun. For real projects, having to actually think about what I'm trying to do has been a net positive, LLM or no LLM.

It's about as much time as I think about caching artifacts and branch mispredict latencies. Things I cared a lot about when I was doing assembly, but don't even think about really in Python (or C++).

My assembly has definitely rotted and I doubt I could do it again without some refreshing but it's been replaced with other higher-level skills, some which are general like using correct data structures and algorithms, and others that are more specific like knowing some pandas magic and React Flow basics.

I expect this iteration I'll get a lot better at systems design, UML, algorithm development, and other things that are slightly higher level. And probably reverse-engineering as well :) The computer engineering space is still vast IMHO....

It was intel culture at one time - when I started, everyone got a card to wear with your badge with intel values, there were only 6 and ‘customer orientation’ was one. It definitely influenced my personal development, but was clearly not adopted equally across the company.

One interesting side effect of AI is that it makes it sometimes easy to just recreate the behavior, perhaps without even realizing it..