
Accept all cookies for a better experience. [email protected] | @FortraFoods
Seattle baby
Joined March 2016
- Tweets22.6K
- Following1.7K
- Followers1.5K
- Likes43K
Pinned Tweet
Tryna have a big soul. A big swol soul. Big pumped soul with which I can lift all my brothers and sisters. I can lift them clean from the dirt and filth, spare them the stains on their soles. I also want bigger calves, amen.
Okay, finally watched Backrooms. This is Stephen King's IT, right? Supernatural, alien presence feeds on fears/guilts, doesn't get fully explained. Pretty neat.
Guys who don't report to the board be like:
At work (R&D at a fortune 500 company w/ 15k+ employees), every time a SaaS pitches their product, my first question in the review meeting is, "Why don't we just build this ourselves?"
In the past, there were always good answers to that question. Today, I can't think of any.
If we can point an agent at any website or demo, have it research the broader problem for 72 hours, build the product with a focus on our specific needs, with any extra features we want, AND save a million a year why would we pay for your SaaS?
Scale? It only has to scale to 15,000 employees and a few million customers. We don't have the same scaling problem you do serving 1,000 businesses with 100s of million of customers. Scale is a non-issue.
Reliability? Your 99.9% self-reported uptime is not impressive. We can pay to host an app on a hyperscaler too. And when we do it, we know with certainty whether the uptime number is true or not. Github's official status page reports ~99% uptime. The Missing GitHub Status Page reports 93%. Reliability is a non-issue.
Bugs? You think your SaaS product doesn't have bugs to work out? I've seen bugs in third party products cost our company millions. Everyone is shipping early and often. Including your SaaS. Every piece of software has bugs. But there is a big difference between a bug in your code and a bug in ours. When the bug is in your code, we are at your mercy. Maybe you put it into Jira immediately. Are you going to bypass sprint planning? You won't have a fix for two weeks. Maybe you'll fail to reproduce and blame our code. Maybe it is our code. Maybe its an interplay. Since you don't have our code and we don't have your code, how are we going to figure that out? If it's all our code, an employee can fix it in an hour. If we need to, we can throw ten engineers with agents in a call until it's reproduced, the fix is merged, and it's validated. Bugs are a non-issue.
Bandwidth? Agents are nearly autonomous now. They don't need to be babysat. I can spin up a project and let an agent run for 50 hours, have it build a PowerPoint and walk into a demo with leadership blind. If anything breaks, "I'm still working on that." Things always break in demos. Nobody cares. If leadership proposes a feature, the answer is, "Yeah, great idea, I can add that." Because I can. Bandwidth is a non-issue.
Maintenance? We have so much prior art, inputs and outputs, we can benchmark anything. We have autonomous PR systems built on top of in-app feedback SDKs so even the non-dev users can contribute to every app or service. Even our analytics systems are tied to automated PRs. Maintenance is a non-issue.
Support? It doesn't matter how much we're paying a month for your platinum level enterprise support when our point of contact has to fetch the one dev who already went home for every non-trivial incident. The incident is never trivial. We already checked the top 10 things it could be because that was faster than asking you. Support is a non-issue.
Expertise? Agentic research. We can build anything. Expertise is a non-issue.
Cost? The cost of intelligence has gone down 100x every year. You're still charging 2022 prices. You should be charging closer to your electricity costs. Cost is a non-issue.
At this point, the only reason we don't switch off existing services is that transitioning 15,000 employees to something else is a pain in the butt. It would be a pain in the butt even with a perfect bug-free, infinitely scalable, perfectly-reliable clone.
Your new SaaS doesn't have that moat.
But it does give me an idea for a product to build.
I've seen a few attempts at "'accidentally' posting a humorous poll response choice" but they usually don't land bc people don't know what the UI means and that the joke is Coffee Lover is accidentally admitting to being a closeted trans woman. In this paper, I...
Chris P. Wicks 🔎🐜 retweeted
I was very lonely so I bought some shares it’s nice to have a bit of company
Chris P. Wicks 🔎🐜 retweeted
On a serious note: if you didn’t know, today is M*nday. Please, please check in on your Garfield oomfs today. Bring them a lasagna. You never know what they’re going through :(
Quick reminder that WD-40 is a solvent, not a lubricant. It will remove gunk that impedes hinges, but you should follow up with some spray lube so they remain nice and smooth.
Fun fact: a breast reduction surgery is basically just a breast lift and vice versa. You remove skin from the bottom of the boob and reconnect it, pulling it up higher on the body. This leaves a pretty gnarly scar but can turn pancakes into bundt cakes.
Chris P. Wicks 🔎🐜 retweeted
Seattle is more of a cul-de-sac than I remembered.
It doesn’t feel cool, it feels like some punk anarchist’s time capsule idea of something that was cool ten years ago. Dead end
The people are nice. Everyone is Asian or White. It’s still beautiful. Tech utopia backwater

























