Working on the website

The other day, I was patrolling the wilds of X, dodging clickbait and memes, when I stumbled into a barrage of posts about Flutter web. Links to some slick web apps built in Flutter were flying around like tracer rounds. Naturally, I got a wild hair up my six to rebuild 11b.dev in Flutter—like a grunt thinking he can go Rambo on a new tech stack.

I kicked off the mission at 0600, full of caffeine and ambition. By chow time, though, I was calling in an airstrike on that plan. Flutter web was turning into a FUBAR dumpster fire, and I remembered why Rails is my battle-tested M4 carbine in these scenarios. I waved the white flag on Flutter and fell back to my trusty Rails base camp.

Instead of going AWOL, I decided to reinforce the original 11b.dev with some new firepower. Here’s the sitrep on what I accomplished:

1. Stood up a back office—think of it as my new command post for running the show.
2. Created a blog and project update hub—now I can sling posts and showcase projects without breaking a sweat.
3. Launched a blog with an RSS feed—because even civilians deserve real-time intel from the front lines.
4. Built an API—laying the groundwork for a Flutter desktop app so I can post updates and projects without humping it to a browser.

So, what’s the next mission? A Flutter desktop app to run my blog ops remotely. This post is coming at you live from the new back office—locked, loaded, and battle-ready. Oh, and if you want to go full “borrow with pride,” the whole site is open-source. Grab the code on GitHub here, swap out the content, and make it your own. The future apps for posting? Also open-source, because sharing is caring in the dev trenches.

Stay frosty, and keep coding!