How much of this feverish "I spend all day typing to AI and it does my bidding, it's incredible!" is because these people have never gotten to order anyone around before, and now they feel kind of power-hungry?
When operating LLMs in a conversational mode, it's clear that they are deeply subject to suggestion, and spend a lot of energy just following the implications built into the questions you ask.
"Estimate this quantity." It does so, gives you a long explanation, and it seems convincing.
"Wait, don't you think this number should be higher, because of reason X?" It will say yes of course, I didn't properly consider X, here is a higher answer.
"Wait, don't you think this number should be lower, because of reason Y?" Yes of course. It will give you a lower answer.
People use these for programming.
@Revision_124c41@Grummz Lost me at 'not a halo fan'. Being a fan of and play the games you work on should be a hard pre-requisite. This contributes heavily to the outcome of the game. It's when all team members have and believe in a mission. Why did that stop?
If you are asking “Why push back against anti-datacenter efforts?” I consider it a tragedy that anti-nuclear efforts largely strangled nuclear power in the US based on vibes, and I don’t want to see that happen to AI. Public opinion matters, and it shouldn’t be ceded unchallenged.
If you are asking “Why should I support AI efforts at all?” I believe we are in the midst of a transition more vibrant than the industrial revolution. Opinions formed a couple of years ago about the uselessness of AI are no longer valid. Millions of people and organizations are getting great returns from using it, and the demand for data centers is the market responding to the value signal. That is how progress is made!
What they told you:
- Manual memory is too hard
- Always use abstractions
- Don't reinvent the wheel
The reality:
- Memory is predictable
- Abstractions hide complexity
- Reinventing is how you learn
Rely on the judgement of your own mind
One of the main reasons big companies die is because the political processes, that were put in place to enable a bunch of people to work together, become a factory of reasons why they can’t do anything good, and have to do things that are lame. The company evolves into a thing that preemptively shoots down its future prosperity.
Modern “AI” is prediction using a statistical model based on a huge dataset of preexisting human work. This, by definition, considers ~mean quality output as successful output. That isn’t a bad thing, nor is it useless, but that’s what it is.
Software has sucked for a long time. A small number of people really cared to make it great. They are statistical outliers.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.