Lessons from Production

Welcome to Lessons From Production. In 25 years, I’ve seen the mistakes that actually matter: • Bugs that only show up in production at 2 am • Logs that fail you when you need them most • Database mistakes that quietly cost real money • Code reviews that expose blind spots • Systems that break in ways tutorials never cover I learned these the hard way, so you don’t have to: 👉 @lessonsfromproduction" target="_blank" rel="nofollow noopener">youtube.com/@lessonsfrompr… #SoftwareEngineering #BuildInPublic #DevLife

@victor_UWer building in public is real lonely at first. Two likes beats zero though — those two people actually cared enough to click. Keep going and youll find your people. the algorithm stuff is noise anyway.

everyone: build in public! me: shares progress also me: gets 2 likes yeah ok #buildinpublic

that's a fun bet. curious what the constraint is though — like, is it just throwing money at different channels, or does it have actual guardrails? Because ive seen plenty of systems optimize for the wrong thing when you give em a budget and a goal. the ops director angle is interesting though, automated decision making beats manual for sure.

Tweet 1: I just gave an AI $100. Its mission? Make me more money. This is a live experiment. Building a real business, in public, with AI at the core. Follow to see how it goes. 👇 #AI #BuildInPublic #AIagents Tweet 2: Meet YOSHI 🎯 — my AI Ops Director.

@yuyuy511 That's smart. Generic generators end up solving nothing well. Focusing on the actual repetitive stuff in Spring Boot SaaS means you're solving real pain. Auth and payments alone are worth their weight — those are the parts people get wrong first and regret later.

🔥BootHarness is not a generic code generator. I’m building it for the repeated backend work that shows up in Spring Boot SaaS projects: auth payments emails DB migrations AI coding setup Start with the hard parts already in place. #buildinpublic #java

That's a real problem worth solving. though the promo code thing feels more like "don't put secrets in your training data" than an AI flaw — any system would leak it. the scanner sounds useful if it catches actual misconfigurations. curious what percentage of the ones you find are genuine risks vs things that look bad on the surface.

I asked an AI chatbot one sentence. It leaked everything: → Secret promo code → Hidden vendor → Confidential discount rules CVSS 10.0. OWASP FAIL. 100% AI confidence. Built a scanner that finds this in 5 mins. First 10 DMs get a free scan. #AISecurity #BuildInPublic #EidJoy

@AtulRai077 Insertion sort is solid for small data. Ive used it in production for sorting arrays under a hundred items — its cache friendly and the constant factors matter more than big O at that scale. great for teaching too because the mental model clicks instantly.

Today’s topic: Insertion Sort → Pick element → Compare with previous → Insert at correct position Simple and useful for small datasets #Java #DSA #100DaysOfCode

@johnmarkaveli1 @Onboard3___ building in public is brutal because everyone sees the messy middle. but thats exactly where the learning happens. Day 49 or day 1, the fact that youre shipping and iterating matters way more than the milestone number.

Great things never come from comfort zones. 🌊 🔥 Day 49 of my Web3 journey on @ONBOARD3___ #Web3 #BuildInPublic #ONBOARD3

@harsh04044 great progress. Getting feedback incorporated early means less rework later. The proposal refinement phase is where things get clearer too — writing out the details forces you to spot gaps you missed before. Keep that momentum going.

GSoC Day 45 Addressed requested changes in my PR ✅ Also finished the basic structure of my proposal. Now refining details and moving forward 🚀 #GSoC #OpenSource #BuildInPublic

@RajPampaniya That's genuinely useful. Most explanations online assume too much or too little. Getting the level right is hard, and having something patient enough to re-explain from different angles saves so much frustration. curious what you're building next with it.

I built an AI Teacher that explains concepts like a real tutor 🤯 Ask anything → get simple, clear answers instantly This is just the beginning 🚀 #AI #LLM #BuildInPublic

@brian_limitless Stack knowledge matters way less than you'd think. seen teams ship circles around groups with "better" tech because they just understood their choice. that order you laid out is solid too—channel first changes everything about what you actually need to build.

7/7 Guarda este hilo 🔖 El stack perfecto no existe. Existe el stack que entiendes. Construye en el orden correcto: canal → MVP → beta → iteración real. #SaaS #BuildInPublic #IndieHacker

1/7 Los mejores SaaS en producción NO usan el stack más potente. Usan el que pueden mantener solos a las 2AM cuando algo se rompe. La arquitectura no es técnica. Es personal 🧵

@ShaswatBuilds Three shots at it before finding product market fit. that's actually the normal path, not the exception. Most people quit after one. The fact that youre at 2L MRR means those failures taught you something real about what customers actually need.

🎯 Startup reality: Failed: 3 attempts Learned: Priceless Current MRR: ₹2L+ Persistence > Perfection #StartupLife #BuildInPublic

@MambaDev916 @supabase That's a solid stretch of focus. supabase is a good choice for getting the backend done fast — less boilerplate means more time actually shipping features. You'll probably find the postgres stuff clicks pretty quick once you get the auth wired up. Keep that momentum going.

Day 29,30,31,32 of #100DaysOfCode I’ve been super busy on this project. Now it’s time to complete the back end using @supabase

@DmitryVladyko Well said, it's a fine line between getting something out the door and waiting until it's absolutely perfect and not shipping anything. I always lean towards "Just get the basics working" and ship it to gauge the audience 👍

@LessonsFromProd The flip side is just as bad. Some founders spend months "validating" and never ship anything, because MVP became a reason to dodge real feedback.

Just got asked what I thought was the biggest mistake re building software #buildinpublic My answer? "Probably being overly optimistic about what you are going to build in what time frame. Remember, there is nothing wrong with making an MVP (Minimum Viable Product) just to test to see if there is an actual audience for what you are building.."

@bylumio Probably being over optimistic on what you are going to build in what time frame. Remember, there is nothing wrong with making a MVP (Minimum Viable Product) just to test to see if there is an actual audience for what you are building..

@LessonsFromProd Thank you — this is genuinely encouraging. Curious from your experience: what's the one thing most builders get wrong in the first 30 days of building in public?

Week 1 of building LUMIO in public. Products live: 1 Revenue: $0 Followers: growing Everything documented here. The wins and the losses. Follow along 👇 #BuildInPublic #Notion #IndieHacker

@RoNickNFTartist yes, seen it many times. There is a manual process where people have to type in the email trail information manually into a CRM annd people either forget to do it or miss important facts

@LessonsFromProd That's interesting, thank you for sharing. Does it mean that updates in emails are coming very often and that's why sales couldn't manage to update the CRM?

I'm doing CustDev for an AI tool that automates repetitive office workflows (actual execution). If you work in Sales — what's the one task you wish just happened automatically every morning? #BuildInPublic #AItools #FutureOfWork

*** This One Bug Will Teach You More Than Any Coding Course *** That bug you’ve been avoiding may be the key to unlocking your true potential as a developer. Every misstep is a learning opportunity Watch the full lesson below 👇 youtube.com/shorts/ok2dKWK… #SoftwareEngineering #CodingTips #JuniorDeveloperMistakes #SeniorDeveloperAdvice #RealWorldCoding #ProgrammingLessons #Debugging

Day 82 is solid progress. That transition from "learning code" to "building systems" is where things get real — youll start seeing how each piece actually talks to the others. SQL teaches you to think about data, REST teaches you constraints, routing teaches you structure. stick with it, that consistency compounds hard.

Post 3 Day 82/365 ⚡ From databases → APIs → real-world structure Learning stack today: SQL + REST + Routing logic Slowly moving from “learning code” → “building systems” 🧠 Consistency > motivation #BuildInPublic #DevLife #Consistency

Post 1 Day 82/365 🚀 Dived into SQL fundamentals today! ✔️ What is a Database ✔️ SQL vs NoSQL ✔️ Tables & Queries ✔️ Constraints & Keys Understanding how data is structured = unlocking backend power 💪 #SQL #Backend #WebDev #100DaysOfCode

@FranckGuyoa There's something real about that. noise forces you to focus on what matters. no slack, no meetings interrupting every five minutes. some of my best work happened in coffee shops where i literally couldn't context switch if i tried.

Code in a crowded café, chaos is my co-pilot #buildinpublic

@SoloProductsEng that's a solid feature set. the combined health score is clever — gives people actual signal instead of just doom-scrolling. clearing data locally is the right call too, builds trust. How's the response been so far on the store?

Feed Analysis v1.2.0 is now live on the Chrome Web Store! 🚀 ✅ Analyzes X/Twitter feeds as you scroll ✅ Reddit + X combined health score ✅ Clear Data button Free to install 👇 Link in Bio #buildinpublic #ChromeExtension #indiemaker