Sammi

If Europe was able to muddle though the 2009 financial crash, then the US will be able to muddle through the next one. Cause that's just what you have to do.

If someone sends you vibe coded code to review, then you are obliged to give them a vibe coded review answer right back at them. Make sure your vibe review prompt tells to agent to be as nit picky as possible. Maybe tell it to be intentionally contradictory with it's change requests. Keep answering with impossible vibe coded review answers when they get back to you and nothing else.

* insert melting face emoji here *

You guys really need to fix your site to be a demo first. See the nimble css page on how to market yourselves well. Right now your site is not telling me anything about how your library works or looks or how it is actually useful to me and how it solves my problems. The questions I actually have when I visit your site.

Think bigger. Don't think in features. Think in business workflows.

You are a consumer, so you naturally think like the consumer you are. But consumers want cheap stuff and only big big businesses are able to provide cheap stuff at massive scale. So stop thinking in b2c. For us little businesses the money is in b2b. Businesses pay lots of money to have problems solved. They want to focus on their core business and outsource the rest.

Consumers hate paying subscriptions. Businesses love paying subscriptions. Because then they can make their problems someone else's problem and focus on what their actual business is.

Man I get exhausted just by reading other people's complaints (without environment description or steps to reproduce). I am puzzled by what keeps OSS maintainers going.

I pretend 4chan doesn't exist and everything's been fine. Now I do the same with twitter and everything is fine just the same.

Linux is big business.

I'm so tired of this quote. It's gets used by douches to justify their douchyness all the time.

The cybertruck was claimed to be a steel exoskeleton. They ended up releasing a car with heavy steel plates glued on.

It's not at all conspiracy theory. It's just same old over promise and under deliver that Elon does.

You don't represent 99% of users.

It's more like the first user catches all of the critical bugs and a handful of users catch all of the high impact bugs. Cause that's kinda the definition of the impact of critical and high impact bugs.

Depends on whether it is a happy error.

> The bad part of LLMs is they don't really "get better" at this stuff. I'm not training a human, and there's a limited amount LLMs can learn. So the training phase never really ends - it's Eternal September.

After I give feedback to the AI I then ask it if we learned something and then I ask it to store that guidance in a relevant skill file.

I have skill files for everything and anything in my project. Three just for testing - one for frontend, backend, and e2e. I have one just for frontend forms. I have one for project terms, which I ask it to read before doing anything, so it keeps the terms in the project right. I have one for doing db migrations and one for doing backend routes. I have many tens of skills that have been slowly built up like this.