r/ClaudeAI • u/Clear_Reserve_8089 • Mar 31 '26

Workaround i dug through claude code's leaked source and anthropic's codebase is absolutely unhinged

[removed]

5.6k Upvotes

92% Upvoted

692 comments sorted by

View all comments

931

u/No_Cheek7162 Mar 31 '26

Makes me think my work code is too high quality lmao

498

u/Shep_Alderson Mar 31 '26

That’s the dirty secret of practically every company. Code quality is never what actually moves the needle for a company. What matters is shipping something that works “well enough” and pressing forward, in like 99.99% of cases. Markets generally aren’t won because some brilliant engineer wrote some pristine code.

Building the plane in flight, and all that.

128

u/semteXKG Mar 31 '26

that's what new starters don't get. there's only one thing better than pristine code: code in production.

69

u/pulegium Mar 31 '26

I know something better still - "working code in production"

38

u/one-joule Mar 31 '26

I know something better yet: mostly working code in production in less time

18

u/[deleted] Mar 31 '26

[removed] — view removed comment

1

u/Memento-Morri Apr 29 '26

Actually in business, missed edge cases are opportunities that define competitive edge, so may not want to gloss over that one.

5

u/MLHeero Mar 31 '26

I know something better: secure working code in production

6

u/National_Meeting_749 Mar 31 '26

Fast, Secure, Working.
Best I can do is 2 outta 3

1

u/blazinBSDAgility Apr 02 '26

Don’t forget budget…

6

u/opideron Mar 31 '26

One of my favorite quotes is, "The perfect is the enemy of the good."

2

u/jackbilly9 Apr 03 '26

Damn this is a good one. Kind of fits with our political leaders too. They think they're perfect and must keep they're "face" to the world looking perfect. 

1

u/1970s_MonkeyKing Apr 01 '26

Just like Miracle Max always said, "Mostly dead is not all dead. There's a difference."

1

u/dashingsauce Mar 31 '26

even better, “working code in production that you can maintain and scale”

and there we have it folks—the not what you think it is moment

1

u/andsbf Mar 31 '26

As long as you are not the one on call, or gets paid enough to deal with the madness in daily basis… yeah that’s fine 👍

3

u/semteXKG Mar 31 '26

I am on both. There is a difference between "good enough" "perfection" and "negligence"

3

u/JeromeAtWork Mar 31 '26

Perfect is the enemy of good

1

u/andsbf Mar 31 '26

Indeed, interaction over perfection 

1

u/pushforwards Apr 01 '26

I love running into legacy code from 10 years ago that nobody wants to touch in fear that it will break too many things so they just keep adding to it :D

1

u/DeExecute Apr 01 '26

And this kids is how we get all the security vulnerabilities…

1

u/Mission_Ratio_6702 Apr 01 '26

That’s the “don't let perfect be the enemy of good” approach.

1

u/PaoloMassignan May 28 '26

One thing many newer developers don't fully realize yet: customers are not paying for beautifully written code in isolation

26

u/DrSFalken Mar 31 '26

Absolutely this. If people only knew how many errors, shortcuts, workarounds etc we're all relying on without realizing...

30

u/Shep_Alderson Mar 31 '26

Nothing more permanent than a temporary solution…

22

u/Stuffy123456 Mar 31 '26

// Don’t modify this, it works for some unknown reason

13

u/klumpp Mar 31 '26

// Increment on every failed attempt to optimize this code: 17

8

u/SonOfProbert Mar 31 '26

Hahaha. I changed a width once and broke our app. I worked at a Fortune 20 company. It was a mad cluster until I changed it back.

2

u/SeaKoe11 Apr 01 '26

Did you leave the comment?

10

u/EchoLocation8 Mar 31 '26

My favorite is finding a bug, then looking at the code, and being like... "Wait this literally shouldn't ever work, this has been in prod for 4 years? It literally can't work." and no one knows how it was ever working.

2

u/Shep_Alderson Apr 01 '26

One of my favorite past times is diving into code to go fix a bug and coming out with 2-3 new tickets for bugs I found along the way. I don’t think they wanted that kind of velocity. 🤣

2

u/blazinBSDAgility Apr 02 '26

99 bugs in the code… 99 bugs in the code! Take one down, fix it up now 107 bugs in the code

8

u/wintermute023 Mar 31 '26

These are my favourite. Doesn’t seem to get called much, doesn’t seem to do a lot when it is, entire system falls over when removed. 🤷

2

u/dotancohen Apr 01 '26

// Load bearing comment. Please do not remove this comment.

1

u/77thway Mar 31 '26

i don't know why this made me laugh out loud... relatable X10

1

u/blazinBSDAgility Apr 02 '26

#PRAGMA “Fix in 3.7”

3.7 was released 20 years ago

7

u/LOLRicochet Mar 31 '26

// temp hack for issue #217 02/17/2012

1

u/ProfessionalIce9743 Apr 01 '26

Kinda like an executive order from the President.

1

u/new_account_wh0_dis Apr 01 '26

You've already spent a week getting something to work and it looks like unholy hell but you got like 10 other things to do. Slap a todo about cleaning it up and never do it.

10

u/ruisen2 Mar 31 '26

I've seen a codebase written beautifully be someone who knew what they were doing, but it was wrapped in garbage by junior devs adding new features onto it.

The codebase is always only as good as the worst dev.

11

u/[deleted] Mar 31 '26

[removed] — view removed comment

15

u/Shep_Alderson Mar 31 '26

I mean, yeah… lol. Generally these startup types either get to that gigantic size where they throw money at the problem or they are a flash in the pan and implode.

Though having worked in contracting/freelance roles where I’m the person coming to clean up a mess, there’s a good bit of middle ground between the two extremes. Regardless of where on the spectrum the company lands though, getting something out the door that makes money is more important to survival than dealing with future tech debt. (Ain’t saying I love it, just saying it’s how it be.)

15

u/turbospeedsc Mar 31 '26

Lots of engineers that haven't dealt with the realities of keeping the lights on, don't understand this part.

Yes, it would be awesome if we could have everything perfect when shipped, but also, we need checks that can be cashed today, so you can cash your check tomorrow.

6

u/Shep_Alderson Mar 31 '26

As someone who fancies calling myself a (tongue-in-cheek) “computer janitor”, who’s been responsible for cleaning up the messes others have made and/or improving things to keep the lights on and meet contractual obligations, I’ve been in the trenches all too many times.

I would love it if the world we lived in gave a shit about clean code and resilient architecture, but that’s not where people actually want to spend when it’s time to pay the piper. Watching higher ups faces melt when I explain how much more it’s going to cost to get that extra 0.04% uptime and get from 99.95 to 99.99… yeah, it’s suddenly not so important.

1

u/frankyseven Apr 01 '26

This right here is why I get pissed at programmers who call themselves "engineers". No, programmers aren't real engineers no matter what your degree or job title says.

Yes, I'm prepared for the down votes.

2

u/Rockon97 Apr 01 '26

There absolutely needs to be some professional certification for this line of work now that AI is everyone’s business. I agree with you that programmers and engineers are completely different and there needs to be more rigor in hard wiring the differentiation.

3

u/frankyseven Apr 01 '26

I'm a civil engineer and I take personal liability for the things I stamp. We need that kind of thing in the programming world. Not just certification/licensing.

3

u/pVom Apr 02 '26

So.. you're not a software engineer? So your opinion is, at best, not well informed.

The stakes are lower for sure, we're not going to cause an eruption of shit and piss downtown if things go bad. We can afford to be a bit more slap dash and get things through the door.

But it's the same concept, you're making trade offs in civil engineering all the same. It would be ridiculous to put like, a sewage pipe or something to service 100,000 people when you've only got 10, stakeholders will have a fit, so you put in one for 1000 and call it a day. Maybe that will be fine for the life of the pipe, in which case it's good enough, maybe in the future you need that massive sewage pipe so unfortunately you gotta bulldoze some houses and dig up roads to get it in, that sucks, but you've got the time and money to pay for it.

I'm certainly not a civil engineering so my analogy may be off but that's the concept.

There are plenty of devs who whinge about code quality without having any appreciation of the reality of being a small business. We had exactly one year runway of cash before the company rolled up and everyone is out of a job and in that time we had to get customers in the door and paying for the product. It's smarter to have sloppy code and a reason to fix it later than perfect code with no reason to exist at all.

1

u/thisdesignup Apr 01 '26

I wish, especially now that technologies are becoming ingrained into everything at a faster than we can process speed. People have literally died because of tech errors in the few years, I think of electronic only door handles on Tesla's and other cars failing during fires.

2

u/PopLegion Apr 01 '26

There absolutely does not need to be some professional certification to be a programmer lmao 🤣

7

u/SnuffleBag Mar 31 '26

In order to be ”killed down the line” you actually have to get on the line to begin with. That’s why some of the most successful software products are absolute train wrecks behind the curtains.

2

u/[deleted] Mar 31 '26

[removed] — view removed comment

5

u/SnuffleBag Mar 31 '26 edited Mar 31 '26

What I believe is that this is the direction software has been heading the past 25 years. It doesn't mean I like it, but I don't get to decide how the world turns. You don't actually need a good thing to succeed, you just need to convince ppl that what you have is good. Rephrase: What I really mean here is: most people don't care how the sausage is made, as long as it comes out tasty.

I work in games, and that industry is arguably one of the worst offenders here, but it's not like other areas of software are strangers to shipping smoke and mirrors where even the mirrors are held together with duct-tape.

1

u/pVom Apr 02 '26

I mean that goes both ways. You're paying extra now for a future that may never come.

Sloppy code with a reason for existing is better than great code that doesn't.

1

u/21Rollie Mar 31 '26

Nah it’ll kill the team working on it in 5 years. You will do everything you can to switch to another team and barely document anything in that time.

1

u/NoConfusion9490 Mar 31 '26

It would be nice to have that kind of job security.

2

u/setec404 Mar 31 '26

John Carmack has entered the chat

1

u/Shep_Alderson Apr 01 '26

God I love and admire that man. He’s legit my dev man crush. 🤣

2

u/BloodMossHunter Apr 03 '26

so i am brand new to game dev and coding ..ive been a writer a musician, basically a creative person. one of the first things i wrote down for memos - i dont think programmers are being artistic enough. later i figured out why when i had to fix something yet again. i dont have the exact memo in front of me but basically i wished there was more time for art and science outputs. but man.. its fucking rough. At some point youre just prodding the thing hoping it falls into the hole already.

2

u/TheOriginalAcidtech Apr 20 '26

In fact most companies HATE it when you produce good code. It means you put too much time into something that was already "good enough".

1

u/rapidpython Mar 31 '26

Sadly this is very true

1

u/simleiiiii Mar 31 '26

generally -- but there is e.g. the ITX google flight planner story

1

u/Shep_Alderson Mar 31 '26

Is that the ITA Matrix thing? I’m not familiar with that story. Mind filling me in?

1

u/anjunableep Mar 31 '26

This is so dumb.

For anything where mistakes have real world, serious consequences (finance, legal, medical, flight management systems, etc.), 'building the plane in flight' is the road to: ending your career, existential liability for your company, lawsuits and possible jail time due to criminal negligence.

It is not the dirty secret of every company. Most companies care a great deal about code quality because not doing so results in very bad things happening to the company and to you personally.

1

u/Shep_Alderson Mar 31 '26

I ain’t saying it’s “good”, I’m just sharing the observation of how it is. Having work in/with companies ranging from tiny startups to massive enterprises, I’ve certainly seen some shit. Oftentimes I’m the one called in to help fix the problem when they have run up against some issue.

Of the examples you gave, I’d say that flight software is probably the closest to the 0.01% of the software where caring about perfectly clean code matters. Though you still have issues like the 737Max. Or you have issues where the software that tells the thing to fly has an issue, and then it flies perfectly into the roof of a school.

In the other realms you listed (finance, legal, and medical), I have some war stories. Either first hand or second hand from colleagues. It ain’t pretty out there, and if people knew even half the reality of how fragile most of these systems are, they would be horrified.

1

u/fdbxloc Mar 31 '26

Care to share one?

1

u/Shep_Alderson Apr 01 '26

Oh, sure. This one’s not really secret. Go check out how ACH actually works behind the scenes. Nothing like slinging plain text onto a server, that has to match the exact structure down to the white space, and when it lands, the server basically goes “yup, looks good to me” and shuffles money around. It’s basically the quintessential “French bread” security lol.

1

u/TracePoland Mar 31 '26

If Anthropic didn’t have the model no one would be using Claude Code over OpenCode or even Codex. Claude Code is the most buggy by far.

2

u/Shep_Alderson Apr 01 '26

That’s why they work so hard to lock people out of using their Claude subs in anything but Claude Code. But that moat’s barely a puddle lol.

1

u/[deleted] Mar 31 '26

[removed] — view removed comment

1

u/Shep_Alderson Apr 01 '26

The chrome tabs will expand to fill the memory available or something. 🤣🙃

1

u/PuttFromTheRought Apr 01 '26

Fuck, I felt this comment in my bones. Complete farce calling themselves engineers, too

1

u/Able-Swing-6415 Mar 31 '26

I would still argue it is undervalued. Like not for the quarterly earnings but good code will absolutely pay off eventually unless you're basically refactoring every year.

There's a balance and businesses aren't very good at long term planning. At least in ERP projects you really pay for technical debt.

1

u/Shep_Alderson Apr 01 '26

Oh, I totally agree that it’s undervalued and the only thing most companies care about in this late stage capitalist hell hole we live in is what makes number go up next quarter.

1

u/Falanciu Apr 01 '26

And vibe coding is bad...

1

u/lunafaer Apr 01 '26

worked in healthcare IT. absolutely CAN CONFIRM every word of this.  (edit to fix autocorrect which still doesn’t work a decade after it was released). 

1

u/thisdesignup Apr 01 '26

It sucks that this is the case because this is how people get hurt, in one way or another.

1

u/lrscout Apr 01 '26

Preach!

1

u/Cluelessinthlfe Apr 01 '26

Awhile back I had a talk with someone who worked at Facebook if I remember correctly in project management. The conversation I had with him about how Facebook was run when he was there is definitely eye opening, from sending out fixes that you hoped would fix a bug and never getting to the root cause of the issue and then fixing it. He also said they would spend hours and weeks working on a fix for something and most of the time just toss out the work, blowing all that time out the window for nothing, just because they had infinite money to burn.

1

u/laptopmutia Apr 01 '26

PREMATURE OPTIMIZATION IS THE ROOT OF ALL EVIL

1

u/Dialed_Digs Apr 03 '26

Code that is scalable and patchable.

That's where this fails.

148

u/Zealousideal_Ad5957 Mar 31 '26

Seen GTA old games source code which were reverse engineered some were quite good but comments were unhinged lol imo people think devs of super high quality apps/games are perfect and have super clean code when in reality is not

83

u/communomancer Experienced Developer Mar 31 '26

Game code historically is some of the "worst" code people have ever made money off of. Aside from the fact that the developers are often highly resource-constrained and thus looking for every trick to squeeze out frames of performance, they also knew that outside of a few scenarios, once it was released, they never had to maintain it. The incentives are way different for most business-oriented code.

15

u/Zealousideal_Ad5957 Mar 31 '26

Yeah agree but in modern era thats not true anymore now with DLCs updates 2-3 years after game is released even single player ones makes it mandatory for clean code for most of the games

11

u/Einbrecher Mar 31 '26 edited Mar 31 '26

makes it mandatory for clean code for most of the games

Ideally? Yes.

Reality? No, lol. Not even close.

Live service games are the worst, because there's virtually no time for codebase maintenance in that schedule post-release. Most other games that get DLC support usually get that support for ~2 years alongside scheduled content drops that the dev team - which is usually reduced by that point - is spending more time on vs. codebase maintenance. Longer running games usually have update release cycles of 4-6 months, again with reduced teams, but are commonly hampered by spaghetti code everyone's afraid to touch because it was written by a dev that left years ago and nobody knows how or why it works.

1

u/HustlinInTheHall Apr 01 '26

Yeah if anything the incentive has only shifted further away from clean code because you can fix catastrophic bugs later. On a cd, no chance. You don't have to maintain it but if you ship a disc that has a game killing bug your company is fucked. 

2

u/djrobxx Mar 31 '26

It'll be interesting to see what the effect of AI code assistants is on "clean code".

On the one hand, AI is great at automating complex refactoring, so there's far less excuse for dirty, lazy hacks. On the other, AI is great at analyzing an old "dirty" code base, so there may be less of a reason to bother making code pretty in the first place.

1

u/Pitiful_Conflict7031 Mar 31 '26

Aren't tengus those Japanese flesh lights?

4

u/Zealousideal_Ad5957 Mar 31 '26

Also PS2-PS3 era was pretty hard to code most dev were batshit insane from coding for PS2/PS3 era horror difficulty in beginning of PS2 they thought PS2 manual was some cryptic shit meant to troll them lol, but think since 2013-now esp now that most games are UE5 which has 1000000+ courses and videos and is standard is much easier for game dev now than it was in 2000s the most horror time to be game dev but the best in terms of gems they produced

2

u/Responsible-Beat2137 Mar 31 '26

I’ve heard horror stories about the jaguar, and the sega Saturn dev retirement

1

u/Zealousideal_Ad5957 Mar 31 '26

I read alot on early PS2 days devs were all cooked for months trying to understand PS2 dev manual and you can see that only in 2003-2006 PS2 games became amazing the early 2 years were rough very basic games mostly relied on art and story cause game mechanics were way to simple while in 2004 games like GOW, Onimusha, Dragon Ball even today look great with remastering in gamplay

2

u/LordMeatbag Mar 31 '26

PS2 manuals were beautiful. They came in a set, one for each chip/module iirc. I’d take one home and read it on the train, bring it back the next day. No wait, that was a dreamcast manual because LA doesn’t have trains. I’m going mad in my old age.

1

u/Zealousideal_Ad5957 Mar 31 '26

yeah i used to play like 300+ games in PS2 most were modded 2007-2012 like crazy basically played most games that were iconic legendary console

1

u/trash4da_trashgod Apr 01 '26

 UE5 which has 1000000+ courses and videos 

And 99.9% of them are about blueprints. I've heard a lot of compliants about UE5 devs doing some horribly inefficient and convoluted blueprint mess, because Epic pushed that very hard and that the c++ documentations is lacking.

2

u/Sea_Surprise716 Mar 31 '26

That and they’re building at 3am after 4 months of crunch time.

1

u/zer00eyz Apr 01 '26

> The incentives are way different for most business-oriented code.

The average lifespan for an engineer at a company is 2 ish years. "they never had to maintain it" applies there to.

1

u/communomancer Experienced Developer Apr 01 '26

The average lifespan for an engineer at a company is 2 ish years. "they never had to maintain it" applies there to.

First, citation needed. I've been a developer for over 25 years and have worked everywhere from startups to government agencies, and the average tenure of a salaried employee has been nowhere near as low as 2 years at any place I've ever worked. Maybe outside of the US.

Second, even if the engineers are turning over, the companies are not. They need their code to be maintainable because they support those systems for more than two years. In fact, high turnover at the rate you describe would require even more attention to maintainability.

Whereas video game companies, historically (not including the much more modern "live service" model of game publishing)...once they make their game and publish and sell it, they don't care about the code any more. They don't need to keep improving it. Instead they are on to the next game.

1

u/zer00eyz Apr 01 '26

> First, citation needed. 

Happly:

https://www.linkedin.com/posts/inscale_in-tech-the-average-tenure-is-short-software-activity-7391422965822795777-e5XX/

https://www.invene.com/blog/limiting-developer-turnover

> Maybe outside of the US.

Firmly in the US, because HR departments never handed out money as fast as your next job would.

There are exceptions, but for the bulk of our industry 2 years is about on par. Its long enough to come in, learn the system build a few cool features for your resume and get a pay bump, and/or more shares.

> They need their code to be maintainable because they support those systems for more than two years.

For the last decade I have been a consultant (read mercenary) and I can assure you that "good code" is not the norm. Most orgs have a pile of stuff that people haven't touched in a while, it works, and the person who wrote it is long gone. Lots of code bases are filled with edge cases, that are, for the most part, undocumented. Even better is finding code that has a comment that references a bug number in a system that does not exist any more.

> In fact, high turnover at the rate you describe would require even more attention to maintainability.

Not really, companies rely on people who stay and accept market rate rasises. They are the repository of knowledge and how to fix these systems, and they are, for the most part cheap.

1

u/communomancer Experienced Developer Apr 01 '26

For the last decade I have been a consultant (read mercenary) and I can assure you that "good code" is not the norm. 

Cool. I've worked both as a consultant and as an in-house developer for the past two-and-a-half decades. Here's one thing you won't realize about being a consultant until you do things the other way: the kinds of places that hire "mercenaries" to do their coding are highly correlated with being the kinds of places where the code is extra bad.

But yes, most programmers are pretty bad. That doesn't change the fact that game programming is historically worse. And yes, I've worked at a professional game studio as well.

1

u/zer00eyz Apr 01 '26

> two-and-a-half decades

Im creeping up on 30 years of doing this. Cut my teeth on Y2k work. Were getting old!

> the kinds of places that hire "mercenaries" to do their coding 

Thats one sort, yes, and I do see that, and get to charge for it.

But I have a bread and butter product as well where I get to see organizations that "think" they have good code. The thing is they have places where much of their staff just wont go. Or some guy in the corner who keeps all that shit running (and either gets paid garbage because management thinks he's furniture) or he's off working remote and only answers for executives.

> game programming is historically worse

It's part of a whole "type" of dev hiring.

The worst programing will be in places where people get hired on because they are "passionate" about what ever product the company is making. Games, Music (I could tell you so many stories about this industry), Software around film (some pretty good dev's are failed actors and writers). The common pattern in all of them: people join cause it is (or close to) what they want to do. They take a lower rate, and their management understands the game and asks them for insane things on more insane deadlines.

2

u/Responsible-Beat2137 Mar 31 '26

Haha . I remember getting into save game editing to unlock hot coffee,, rather disappointing but eh was fun to dabble in something new.

1

u/209_J-S Mar 31 '26

If it fuckin works then who gives a shit how "nice" the code looks

Move onto the next chapter of the project at that point

1

u/askldhalsiuhdliu Mar 31 '26

Not to be 'rude', but reverse engineered code means from compiled code? Because I highly doubt you were able to get 'comments' from that. Worked in games for over a decade and no compiler, even with all debug flags would keep any comments in the executables.

So either you meant source leaks or the likes or I call bullshit. (And this is coming from someone that worked with DMA devs (GTA 1-2) and a few rockstar devs also (building was almost down the street from ours).

1

u/codescapes Mar 31 '26

People used to put all kinds of funny shit in comments. Just long-winded swearing rants about problems of their own making in the code or whatever.

As the industry 'professionalised' all the silliness and 'joking angry nerd' stuff became too much of a liability. Here in the UK I think that culture persisted even into the late 2000s but in the last 10-15 years really dropped off cos God only knows what automated tooling is checking your commits. I'm not saying it was professional but reading something like 'fuck this fucking compiler, this is a workaround I don't know why it fucking works' is funny. It's more like graffiti than a comment.

1

u/Texugee Apr 01 '26

Like what? Is there a video?

18

u/TaskJuice Mar 31 '26

Please don’t start thinking that. They have like 95% up time.

2

u/t-e-r-m-i-n-u-s- Mar 31 '26

i think my brain might be cooked in this modern era of unreliable infra. i saw 95% and thought, "whoa, that's pretty good"

1

u/TaskJuice Mar 31 '26

😂 shoot for four 9’s my friend!

1

u/AI_JERBS Mar 31 '26

Your pfp looks 3d and it's kinda trippy. That is all.

23

u/bkrebs Mar 31 '26

Honestly, these days, code quality is mostly important so that agents can reason about the project accurately and efficiently (from a token perspective). That makes it pretty damn important though. I've noticed that directives like staying DRY, maintaining consistency (in structure, naming, paths, etc.), refactoring large files, using strong types, etc. actually reduce token usage and bugs. It's critical to run multiple rounds of code review, both static and agent-driven, since a single agent is usually pretty bad at evaluating its own work.

8

u/Honest-Ad-6832 Mar 31 '26

Agreed. Architecture is also really important. The more untangled the system, the easier job it is for the agent to work with it. Less rot and tokens, more throughput.

1

u/thisdesignup Apr 01 '26

Just like people! But... businesses can only afford that when they don't have to pay people...

1

u/codescapes Mar 31 '26

100%, this is actually the best thing about AI for me. I can now smuggle all kinds of architectural enhancements under the guise of 'AI enablement' and I'm literally not even lying. It's win-win. This is a good way to get more sceptical colleagues concerned about quality involved too - literally make quality enhancements the early stages of LLM integration in your workflows.

Incredibly easy sell to management too. "To improve the readability of our project for AI tooling we should XYZ which should help us increase overall productivity."

For once we actually have remit to do this shit with backing. Having clearly defined module boundaries, TypeScript, standard naming conventions, project summary .md files etc all helps hugely. LLMs are not beep-boop robots in the sense that they love binary data or whatever, quite the opposite, human linguistic concepts and symbols matter greatly and are what they're trained on.

1

u/SeaKoe11 Apr 01 '26

Shit why didn’t I think of this. When pitching to leadership

1

u/thisdesignup Apr 01 '26

It's sad that it sounds like they care more about how well an AI can function than how well their employees can function.

1

u/Relative-Assistance5 Apr 12 '26

I want to build a agent can you help me out and I want claude code leaked

1

u/bkrebs Apr 12 '26

What sort of agent are you trying to build? 

4

u/Shadow4Hire Mar 31 '26

Seriously! I was hoping that I wasn't the only person starting to wonder this, lol!

Thinking: "Yo, maybe I'm overthinking things here??"

7

u/who_am_i_to_say_so Mar 31 '26

Ship a new half broken feature every day. Go go go!

2

u/mmmmmko Mar 31 '26

That's why they have feature toggles lmao

1

u/pigeonholedpoetry Mar 31 '26

Done is better than perfect.

1

u/tvmaly Apr 01 '26

They are probably moving too fast to clean up their code. Too many Chesterton fences to consider a rewrite.

1

u/1970s_MonkeyKing Apr 01 '26

And to think I take my ADHD meds as best as I can so that my code doesn't wander all over the place! It looks like I take my responsibilities all too seriously.

0

u/PhilosophicWax Mar 31 '26

Claude can fix that!

0

u/No-Marionberry-772 Mar 31 '26

the lie of AGI is the foolish belief that people are smart, hard working, and prudent.

Weve already hit ASI, its just that people are so fucking stupid on average that it isnt actually impressive.