Full time shitposter part time SWE @momenticai
Cyberspace
Joined December 2025
- Tweets176
- Following41
- Followers145
- Likes183
SWEs have basically become QA engs, Mo should help alleviate some of the burden of vibing a bunch of stuff into prod
Introducing Mo, the world's first AI QA engineer
Point it at your app and 100+ agents bug bash it in parallel. Every bug comes back with repro steps, logs, and a video
In our evals vs Codex with Playwright MCP: → 3.8x more bugs → 9x more bugs per hour → half the cost per bug
RT + reply "Mo" for $250 in free credits. Drop your app URL, Mo will bug bash it and DM you the report today
Alysa Liu recently went viral for comments she made in a 60 Minutes interview.
When asked about the future of software testing, Liu responded:
“Just say no to more E2E tests.”
Honestly, she had a point.
Not because E2E doesn’t matter.
Because E2E matters too much to waste on low-signal tests.
A healthy testing strategy looks like a pyramid:
- lots of fast unit tests
- fewer integration tests
- a small number of high-value E2E tests
Unit tests tell you the parts work.
Integration tests tell you the boundaries work.
E2E tests tell you the product still works.
The mistake is using E2E to catch every bug.
The opportunity is using E2E to protect the workflows users and revenue depend on.
How Much Are You Worth In Github Stars?
stars.momentic.ai
Question: Why bother with backups when you can just live dangerously?
I deleted all our S3 buckets to cut costs.
The data? It's in the cloud, literally.
When the team panicked, I said, "Rebuilds build character."
Now we're crowdsourcing user data from old emails.
One dev found a CSV in his spam folder.
It's like archaeology, but for customer info.
The CEO asked about downtime.
I told him it's "unplanned innovation time."
Users are reporting missing profiles.
I suggested they create new ones (fresh start)!
Legal's freaking out over data loss.
I smiled and said, "What data? No evidence, no problem."
We had over 400 open tickets in the backlog this morning.
I realized that managing them was taking up valuable engineering time.
So I just selected all of them and changed the status to closed.
My reasoning is that if a bug has been there for two years, it's not a bug.
It's a core structural element of the user experience.
The PM called an emergency meeting and asked where the Q2 roadmap went.
I told him the roadmap was in our hearts now.
We don't need a Kanban board to tell us how to write code.
If a user actually cares about a feature, they'll submit another ticket.
It's essentially a natural selection process for software requirements.
Only the strongest complaints survive the great purge.
Someone pointed out that I deleted the compliance tasks for GDPR.
I just smiled and said privacy is an illusion anyway.
The legal team is drafting a memo about my actions.
I'm hoping they put it in Jira so I can close it too.