Ricardo Gil Simões

So, what happens when you combine @TauriApps with @Ionicframework ? You get a nice Starter Template #Tauronic github.com/rgilsimoes/Tau…

Our Viseu office now has more square feet than ever! 🫸🫷 This expansion proves that investing in talent outside big cities is a testament to what we stand for: a thriving ecosystem, where growth, innovation, and local opportunities fit in the same sentence. 💪

Even AI acknowledges it's own garbage... But @kirodotdev might get away with it :-)

Hi @kirodotdev ! Are there any plans to switch from credit based usage to session or time limits usage?

Competition is fierce: 2 new kids on the block T3Codes from @theo and Paseo paseo.sh

JNation returns on 26–27 May in Coimbra. Check our website to see this year’s invited speakers - JVM experts, Java Champions and engineers building systems at scale. Early Bird tickets available until April 17. #JNation #Java #Coimbra #tickets" target="_blank" rel="nofollow noopener">jnation.pt/#tickets

Check out my latest article: The Agentic Paradox: Why Building with AI Feels Like Running a Race with No Finish Line linkedin.com/pulse/agentic-… via @LinkedIn

@theo I would like to see you review Kiro CLI

I was wrong. Claude Code's performance is unacceptable. Whenever I open it, my laptop's fans start roaring and my battery goes to shit. No issues with Codex or OpenCode.

This is unprecedented!

So bad that @amazon killed free Amazon Q and imposed Kiro Cli with limited credits :-(

I would like to share a little side-project! Hope it proves useful! evcalculator.eu #evcharging

Here it is! youtube.com/watch?v=ca8fs7…

It's time for @theo to review kiro.dev

@MEOpt Fantástico, o técnico vinha de mau humor, deu meia volta e disse que precisava de ajuda! 🤦🏻‍♂️ 3 dias já sem serviço.

@Rykhard Boa tarde. Para que possamos verificar a situação, pedimos que envie DM com os dados de serviço (NIF e contacto telefónico). ^JR

Lindo serviço @MEOpt ! Obrigam uma pessoa a deslocar-se 50km para estar na morada às oito da manhã e depois não aparecem!

This one is big! ✈️ Critical Software and @Airbus announce the creation of an Engineering Centre focused on embedded aerospace software. 🦾 criticalsoftware.com/en/news/airbus…

É NOSSA!!!!!! 🏆

@theo I'm using... recursion... :-)

ANNOUNCING THE FIRST EVER CLONEATHON Build an open source clone of T3 Chat, win up to $5,000 Deadline is next Wednesday. Good luck and have fun nerds 🫡

@theo Interesting initiative. Does it have to use paid models or are you just interested in the functionality?

@theo I’m not a paying client, but I recognize how hard you have been working on this. Kudos for the transparency and accountability.

T3 Chat has recovered and is now working again. Now for ACCOUNTABILITY POSTING 2.0. Outages like this are unacceptable. Tens of thousands of people rely on T3 Chat every day, and we need to make sure our service is reliable. We also need better safety nets in place for when issues occur. I'm going to talk about the upstream provider that triggered the issue. Please treat this as TRANSPARENCY and not BLAME SHIFTING. Blame us!!! We've been working hard to move over to Convex as our data layer and sync engine for T3 Chat. This might seem like a "database swap" but it goes much deeper. It's effectively a full rewrite of T3 Chat. After a lot of effort and 3 failed migrations, we finally had a successful move at around 8pm last night. That was during our lowest traffic window (~40% of our peak traffic). All looked good. I was pumped. A month of effort, finally shipped. I literally slept for 12 hours. Woke up to utter chaos. The tl;dr is that a traffic spike took down their websocket connection layer, and some bad client code from their React package caused a reconnect loop that effectively DDOS'd the Convex endpoint. Convex will have a detailed write up in the near future, but I want to talk about what we're doing going forward. 1. Actual status updates and reporting in-app Right now, outages are reported via me via Twitter. We're a real app now. You shouldn't have to follow me to know what's going on. We'll be introducing a status page soon to make things clearer 2. Paging system for when outages occur Right now, we're too reliant on the community for tracking outages. I love that y'all DM me when issues occur, but that doesn't help when I am asleep. We need better methods to report outages so Mark and I get woken up and can fix things faster. Side note: I hate PagerDuty, so I'd love suggestions on what we can use instead. 3. Automated "refresh to latest" flow on client A lot of the issue we had today was caused by a bad client side package DDOSing Convex. Even when we pushed a fix, lots of users were on the old version still, and would stay on that old version until refreshing. We have a "please refresh" button, but that's not enough. If an old client can connect, we need the ability to disconnect it. This will be an annoying tech overhaul with a lot of potential edge cases, but it is necessary for us to assure stability. 4. Evaluate all upstream providers to make sure they are prepared for T3 Chat's load I deeply love Convex and I know they're the right database for what we're building with T3 Chat. Outages like this still scare the shit out of me. I need to seriously evaluate them and everyone else we rely on to make sure we won't have more problems as we continue to scale up. Anyways... This sucks. Seriously. I hate outages so much. You guys use T3 Chat because it's the best chat app ever. Outages make it the worst chat app ever. Know we're taking this as seriously as possible. I expect to have a few more sleepless nights as we get everything in order to be more resilient. I'm sorry.

No other conference in the world opens up with a Rock concert 🎸 ⁦@JNationConf⁩ #java