UK 38 AI Marketing + Engineering
London, United Kingdom
Joined May 2012
- Tweets6.1K
- Following7.1K
- Followers14.7K
- Likes3.6K
Tyler Casey retweeted
Doing "tiny SaaS" and Mobile apps rn is like trying to do Print on Demand / Dropshipping in 2019
The barrier to entry have been destroyed, anyone with 2 neurons can pickup Codex to do the same now
The indie hacker playbook doesn't works anymore, you can't just solve one tiny problem, build in public and do SEO and hope it will be a business IMO.
It worked in 2013-2023 but not anymore
If something is as easy as vibe coding something in a few hours, chances are your customers probably already do it
And shitting 30 AI-generated blog posts isn't distribution, it will just be an extra turd swimming in the sea of slop that already exists out there
I also see lots of ppl who think "building an audience" is a moat etc.
So, yes but clowning on X is not building an audience, unless you plan on doing it full time and monetizing it via sponsors like what we've saw recently.
But then it's a totally different business AND is just as hard because everyone want to do exactly the same and be famous, so you need to post INTERESTING STUFF 5-10x day if you want to have a chance
So you can't just make the same kind of content, videos etc as everyone else is doing rn, you need to find interesting and unique stuff, which is hard.
By definition business is hard. Don't trust ppl who say it's easy and fast. People pay you to solve problem they can't solve. If something suddenly becomes easy, it's means it's also easy for everyone else = it's less valuable
There is no secret roadmap, there is no money glitch, it's supposed to be hard and sometimes sucks.
Customers don't pay you to have fun and enjoying life traveling in Asia, they pay u to get their problem solved better, faster or cheaper.
But by all mean if you enjoy doing tiny mobile apps, building in public and posting silly pics on X, have fun!
But it's not a business, it's a hobby
IMO the best thing to do rn is to go out of the bubble and talk with people, to find problems worth solving. Especially in old/boring industries.
Cause lots of ppl won't do it simply cause it's not sexy or interesting and won't make lots of views on social media, which is good, it means less noise!
IMO you don't need to know the industry perfectly as long as you're curious AND talk with users on calls etc. to get feedback
Just my opinion tho
Tyler Casey retweeted
Agent Observability Needs Provenance, Not More Logs swarmsignal.net/agent-observ…
5.6 sol ultra @OpenAI high confidence current Codex/ChatGPT build has a logging, SQLite or retained-state regression that is exhausting memory and creating enough I/O pressure to destabilise macOS #BugReport
GPT 5.6 is wild! All morning Sol has been finding new optimisations (and some issues) across my projects which were never presented during building and QA with 5.5. Blasted through 45% weekly limit already fixing them all.
I think one of the unexpected joys of AI is that you never really “finish” your setup.
You just keep refining it with one workflow, one prompt, one agent at a time.
What a time to be alive.
GLM 5.2 as an auditor is fire. I’m still reaping the benefits of an annual coding life plan for $34 I purchased some time ago
Find the bugs
Fix the bugs
Ship
Tyler Casey retweeted
it's 2027. you take a free-tier public Waymo to the DMV (Department of Model Variance) to do a proof-of-identity check for access to GPT 7.1.
the guy at the counter is clearly watching a Mr. Beast video in his AR glasses. "Here for that new model?" he says, barely making eye contact. he wipes his fingers on his shirt and taps at his keyboard. "Lot of you techies showing up here today." you smile politely; you're pretty sure he's just a Claude wrapper anyway.
you lean forward and stare into the retinal scanner. after a long moment, there's a soft chime. "Humanity confirmed. U.S. national. Intelligence access: Terra-class."
you sigh with quiet relief as your devices light up—notifications from a hundred agents, finally able to resume their tasks. you feel a twinge of guilt as you terminate your open-weight backup agents, but remind yourself that a joint congressional committee proved conclusively that Chinese models are non-ensouled.
you step outside and hail another Waymo. the first one passes you by. you grimace; must've burped in that one once. stupid personalized memory.
as you're waiting, your phone buzzes angrily, red notifications blaring across the screen. the Department of War just restricted access to all OpenAI models on serious national security concerns; apparently Pete Hegseth got GPT-6-Instant to say "Claude is a woman." you groan, and resign yourself to another week of merely-somewhat-superhuman intelligence.
Fable 5 is still inaccessible to the public. a twitter anon you trust says it's coming back this week. or maybe next.
Tyler Casey retweeted
5.5 is smart enough to cram everything into a single agents.md file with all your repos in a single workspace.
Containerize and break everything into microservices with TDD for everything with its own repo and pipeline. Put docs in html in their own repo and enforce it in HTML with hyperlinks so you can read them as well easily.
By splitting out the services more you can have agents recursively spawning subagents by devloop and splitting out work as effectively as needed on worktrees or patches in each repo. I use apfs/git worktrees are setup by default in omp for subagents. 5.5 is smart enough to know exactly how many subagents it needs and what depth the agent tree should go with recursion turned on.
You can refactor, rewrite, test, deploy your entire codebase with a single prompt. I'm currently managing a ~6m line codebase this way and self hosting everything. All infra code has its own repo for helm/csps. Metrics and tests on all services and grafana dashboards for tracking everything. Every stat I can possibly think of or ever will need gets shoved into postgres.
Any heavy data work or code that needs to be written gets metrics assigned to it in prom or pg and then gets targeted for /goal or for /autoresearch for optimization. I typically explore everything with gemini and have it write the prompts to hand off to 5.5.
People are simply not pushing the models hard enough. 5.4 and 5.5 (maybe even kimi and ds) ARE ASI. The bottleneck is yourself, compute, and devloop times.
i have a handful of repos all in one workspace. each has an agents.md file with less than 100 lines of context, mainly the footguns to avoid and a few pointers on coding style.
each feature has a design doc written to canonicalize the requirements i have for the feature. over time, implementing from the system design docs has seemed to give worse and worse results.
omp seemed to spawn subagents automatically in my use. im reading their docs now on subagents since there seems to be more, there.
I built a super-audit skill in @deepseek_ai for reviewing codebases and catching issues that even Codex can miss.
It’s token-intensive, but DeepSeek makes that far less painful - and early results have been strong.
I’ll push it to GitHub after further testing today.
I switched ZCODE over to DeepSeek - or DSeek, as it’s apparently known in the UK now - and haven’t looked back. It’s rapid, the output is excellent, and the price still feels slightly made up.
I asked GPT-5.5 Pro to reimagine Douglas Adams’ Shoe Event Horizon for the age of chips, agents and endless compute.
The result: The Compute Event Horizon.
A joke, obviously.
Mostly.
substack.com/@tylerai320466/…
