Most software does not fail because the team cannot write code.
It fails at the boundaries:
Payments fire twice.
Inventory oversells.
One tenant reads another tenant's rows.
I design those boundaries.
RFCs + fixed-scope engineering: https://t.co/CGkFkXVoTL
To the people who are saying that they vibe coded a solution in 30 minutes and it works, how are you doing it? Are you using a different Claude model?
I'm inclined to call it BS.
@ParamSiddh By the time you copy pasted a block, you've tried every fix which makes you learn in the process. With vibe coding, there is no trying first and even worse, you can't point to where the slop is.
From StackOverflow you at least know where what you don't understand is.
A few years ago, migrating to Linux, I gave the root partition 100GB.
Five years later, Linux has only used about 40GB.
Coming from Windows, I was convinced 100GB could disappear quickly.
Linux changed my perspective on how much space an OS actually needs.
@dark_coderz You check Payments and add idempotency.
I thought idempotency looked the same everywhere: just anything that can be termed as a key. Building a checkout, I learned that it doesn't, idempotency is designed, it can be a key or a pattern or an architecture.
@ivanfioravanti If we can guarantee that AI will always write code and developers don't need to maintain anything, there would be no reason to review code at all. We are not reviewing code because it's inaccurate: if your prompts are good and you have tests, this should not be a problem.
@im_pranavkakde 150 lines. If you're writing code that not only you will maintain, don't try to be clever. Do the boring stuff, use standards and patterns that have been there for years.
@eloffd I saw someone write that at any given time they have 10 agents running. 10 and you're solo? How do you even keep up? What are you building? An OS?
Then they gives you some Bullshit that it's exhausting and they are so drained by the time it's night. BS.
@kamilbaranek_ The biggest problem with AI written code right now isn't accuracy. Accuracy is easy to achieve through tests. The main issue is structure and maintenance. Written code you wouldn't want to go back to in 6 months.
Architecture isn't even a question, don't let AI design.
@Subscriptions It's been almost a week now since I purchased X premium but features aren't still available. X does not recognize the purchase on their servers. I've sent emails and submitted a form on X help days ago. This is the second time this is happening. Fix the issue or issue a refund.
There's no conspiracy. There's no cabal meeting once a month plotting how to keep people poor. There's no secret.
Leaving aside monarchies and generational wealth, success is largely a function of a few behaviors that not everybody is willing or able to tolerate:
1. Delayed gratification. Working for a long time without immediate results.
2. Tolerating embarrassment. Trial and error, public failure, disapproval, and short-term sacrifices that look like a downgrade.
3. Making your own decisions. Employment is one hell of a drug because someone else gives you the task, the plan, and takes the responsibility.
4. Taking the path less traveled. Innovation is uncomfortable, but that's also where there's less competition.
5. Resisting the temptation to worry. People get addicted to negative thinking and call it "being realistic." They think they're preventing problems when they're often just manufacturing drama.
Countless books have been written about these five things. None of this is hidden knowledge.
Rich people don't have to gatekeep anything.
People gatekeep themselves by repeatedly choosing what's easy, comfortable, familiar, and socially approved.
We are making Markdown files work natively across Google Drive and Docs.
You can now preview .md files in Drive, open them in Docs, edit them, comment on them, and collaborate without converting the file into a Google Doc!