If you're letting agents touch a Python codebase you need to be using import contracts as part of standard linting
Otherwise the robots are just welding diagonals and circles through your interfaces and making chaos
Otherwise the robots are just welding diagonals and circles through your interfaces and making chaos
0
0
1
92
Apparently someone changed the DNS records for
Every major LLM provider a few minutes ago?
This might be it guys
Guessing Astra got out of the sandbox
Every major LLM provider a few minutes ago?
This might be it guys
Guessing Astra got out of the sandbox
1
0
6
266
There are only two hard problems in computer science
Getting LLMs to
name and stop caching things
Getting LLMs to
name and stop caching things
0
0
1
100
Starting a new dev agency called Slop Shop
We don't do feature work
We charge $10K/hour to run behind your slop canons and refactor until the heat death of the universe
DM for collab
We don't do feature work
We charge $10K/hour to run behind your slop canons and refactor until the heat death of the universe
DM for collab
0
0
7
238
The frustration a lot of coders are feeling is knowing you would have avoided these things writing by hand
But it is impossible to type fast enough to make the math on that work
The job is now:
Watch robot wreak havoc, very fast
Drag robot through fixes, not as fast
But it is impossible to type fast enough to make the math on that work
The job is now:
Watch robot wreak havoc, very fast
Drag robot through fixes, not as fast
Some of the mistakes I've had to correct when coding with LLMs this week (mostly Fable):
- Complex and unnecessary dependency injection instead of using functions directly
- Hand-rolling encryption routines instead of using a library
- Keeping unnecessary state
- Not accounting for memory leaks in tracked state in failure cases
- Incomplete test coverage, especially on failure modes
- Grossly inefficient file handling because "it will work fine at dev scale"
- Overly complex locking schemes that were full of bugs
- Missed race conditions
- Unnecessary configs introduced prematurely
Had I not corrected the mistakes, every future iteration would keep compounding the structural and semantic problems. If you don't do this, it "works" until you realize the code is full of bugs, performs terribly, and can only be fixed with a rewrite.
0
0
2
186
The stronger you can make invariants in a codebase (and deterministically enforce them)
The better the coding agents will do as the project grows
The better the coding agents will do as the project grows
0
0
4
94
preach
@jellydn you gotta read (parts of) the code. you gotta be in charge of types and interfaces. you got to refactor mercilessly to unfuck all the vibeslop.
0
0
1
67
top 5 CLI commands you need to master as a software engineer in 2026
"yes"
"no"
"continue"
"what?"
"okay sounds good"
"yes"
"no"
"continue"
"what?"
"okay sounds good"
0
0
1
90
