Following along with a tutorial makes building full-stack applications look simple, but staring at an empty code editor right after is where the real panic sets in. You understand the architecture and API endpoints while watching someone else build it, but designing your own schema and handling edge cases from scratch feels completely different. Most people get trapped consuming one roadmap or course after another without actually finishing an independent project. For those who broke through that initial wall, what helped you transition from following guides to actually shipping your own software?

🚨 **Spring Boot developers — I need your opinion on a production problem** I’m working on a Spring Boot application with **JPA + PostgreSQL + Kafka**, and I’ve hit a problem that took me way deeper than I expected. Imagine this: ```java @Transactional public void createOrder(Order order) { orderRepository.save(order); applicationEventPublisher.publishEvent( new OrderCreatedEvent(order.getId()) ); } ``` The event listener then publishes the event to Kafka: ```java @Async @TransactionalEventListener( phase = TransactionPhase.AFTER_COMMIT ) public void handle(OrderCreatedEvent event) { kafkaTemplate.send("orders", event.orderId()); } ``` At first glance, everything looks fine. But here's the problem: Sometimes the Kafka event **isn't published**, even though the order was successfully created. And if the application crashes at the wrong moment, we can end up with: Database ✅ GOOD Kafka ❌ NO Now I'm wondering: Would you use **Transactional Outbox** here? Is there another Spring-native approach you'd prefer? How would you guarantee that the database state and Kafka event don't get out of sync? I'm specifically interested in how you'd solve this in a **real production system**, not just theoretically.

I like projects that start with: “We know what we want to build, but we’re not sure how to build it properly.” I’m a senior software engineer and most of my work sits somewhere between full-stack development, AI, automation, mobile, and backend architecture. A few examples of things I can build: → An AI agent that reads documents, makes decisions, calls APIs, and takes actions instead of just answering questions → A SaaS product from rough idea to a working MVP with authentication, subscriptions, admin tools, and deployment → WhatsApp/Discord/web assistants connected to CRMs, internal data, calendars, and business workflows → Existing systems that need to be untangled, stabilized, sped up, or prepared for real production traffic → Mobile + web products sharing the same backend → IoT/robotics systems connecting real hardware, sensors, cloud services, and AI My usual stack includes TypeScript, React/Next.js, Node.js, Python/FastAPI, PostgreSQL, Redis, React Native/Flutter, AWS, Docker, and LLM/RAG tooling. I’m not only looking for neatly written project specs. If you have an unfinished prototype, a half-working product, or even an idea where the technical direction is still unclear, send it over. I’m happy to look at the problem first and tell you how I’d approach it. No sales call required.

I use youtube.com when I need to understand something, github.com for my code, and lately floment.ai to keep track of what I'm building and what I need to tackle next. It sounds simple, but having an actual project to move forward makes learning feel way less random. Instead of "what tutorial should I watch next?" it becomes "what do I need to learn to finish this feature?" For the devs here, do you learn better following a structured roadmap or building something and figuring things out along the way?

3 years ago I had 47 open tabs, notes in 5 apps, and zero projects finished. Today I ship production code. The shift? → One place for all notes (Notion) → One roadmap, not 12 courses → Build > Consume (even ugly projects count) The devs who make it aren't the smartest. They're the most consistent.