SWE since 2015 – @monthlygg_ & @stratforgegg
Joined May 2021
- Tweets7.8K
- Following619
- Followers666
- Likes20.4K
Pinned Tweet
Calypso Casino blueprints done! 😎
Available tomorrow on @StratforgeGG (Monday).
Download follows soon here! DMs open for T1 teams!
boned retweeted
It's almost time.
After a year of development and testing behind closed doors, Stratforge Open Alpha launches November 5th.
Free and open to everyone.
Join thousands of players already using Stratforge.
boned retweeted
Did you know with Stratforge you can export entire stratbooks in seconds, sorted, highlighted and customized?
boned retweeted
Got a little something I achieved in destruction accuracy.
More coming soon. Follow me and @R6replay to stay updated 👀
boned retweeted
Hot take: it’s the second-rate programmers raving about ai.
ai code is mediocre at best.
I have yet to experience the “great leap in dev speeds” on frontier models when I have to baby it for quality.
Even “A-listers” can have bad takes.
boned retweeted
A new release just hit the shelves.
Introducing Workspace Resources.
Build your own library of images, icons, and in-game screenshots. Upload once, reuse across blueprints.
Available in Alpha now, with more to come in our upcoming major release! 👀
Especially SaaS that focus on cloud, infrastructure and complex problems are the new golden era of SaaS.
Your simple CRUD app won't last in the era of AI, whereas complex software however does.
boned retweeted
this is very easy to disprove, empirically from what we see since decades: We have open-source alternatives to most SaaS that you can self-host with a single Docker container. They are basically free and far easier than vibe-coding. Yet, many people still choose SaaS - why is that? Because ownership comes with responsibility and maintenance, both are expensive, economically and physiologically (stress).
Vibe coding costs even more than open source (tokens cost money, prompting costs time, stress costs), and also sometimes more than SaaS, because suddenly you own the bugs and the uptime.
Real fun when it breaks on a Sunday and you have to spin up some prompts to fix it instead of paying 12$ per month to a company that handles everything properly.
I think people use vibe coded currently because it's new and exciting, but eventually see the real costs it has and instead will go with the peace of mind option for a few dollars.
Saying you don't need to know how to code or understand it in the AI era is like saying
"spit me out a perfect work for my master thesis. Make no mistakes."
then not fact checking it after and wondering why you failed
boned retweeted
2026 is fundamentally no different than previous years.
Amateurs can create something that appears to work.
But they’re unlikely to create something that is secure, performant, consistent, accessible, usable, reliable, maintainable, and scalable.
Software engineering was supposed to go away when low-code/no-code hit the shelves. It was supposed to go away when WYSIWYG IDEs hit the shelves. And it didn't.
And now, with AI coding agents, it's still the same. It lowers the barrier to entry. You can get started faster than ever. You can even build small personal projects and productivity tools with little or no SWE experience.
But as soon as you want to build software in earnest, you need to know the fundamentals: Security, maintainability, scale, reliability, etc. They do not go away regardless of how advanced the software-building technology becomes.
boned retweeted
People already treating software developers (who actually can code) like these impossible creatures.
It’s not that hard. Just learn to code and write the code.
You don’t need AI.
boned retweeted
vibecoding sucks man. so many losers on my uni course are only doing cs because their parents told them it'd be good money. they were destined to drop out after 2 months but by some unholy luck they've survived purely on ai code and they all think they're so smart because of it
boned retweeted
Yesterday I coded by hand the entire afternoon.
* I turned off copilot
* I prohibited Claude from touching the code
* The only thing I used Claude for was to help me with compiler errors. But instead of asking it to fix it, I told it to explain the error to me
I loved it
