Locomo.io

From my previous post about generic APIs - what enables us to do it? It's the separation of definition from logic. Let's talk about how this insight helps us reduce redundancy in our code. Here's what we typically write: /// ProductService 🏭 validate(data) > check if name exists checkPrice(data) > validate price > 0 getRegionTax(data) > tax calculation getFinalPrice(price, tax) > price with tax findWithInventory(id) > get stock info findForCatalog(id) > get catalog view findWithSupplier(id) > get supplier updateStatus(id) > validate transition // OrderService 🛍️ validate(data) > check items exist validateAddress(data) > verify address calculateTotal(items) > sum with tax calculateShipping(address) > shipping cost findWithItems(id) > get order items findForCustomer(id) > customer view findForAdmin(id) > admin view updateStatus(id) > validate flow // Then for Users, Inventory... We keep writing the same patterns with slight variations for EVERY entity... The key insight? Separate WHAT (your specific business rules) from HOW (the generic implementation): ProductModel = { // Your business rules stay specific fields: { name: { type: String, required: true }, price: { type: Number, min: 0 }, region: { type: String, enum: ['US', 'EU'] } }, // Complex logic stays in YOUR control computed: { finalPrice: { deps: ['price', 'region', 'discountCode'], compute: price * (1 + tax) * (1 - discount) } }, // YOUR views, YOUR way views: { search: ['id', 'name', 'finalPrice'], catalog: ['id', 'name', 'finalPrice', 'image'] } } The generic handler just handles the repetitive parts: POST /api/{entity} - creation with YOUR validation GET /api/{entity}/{view} - YOUR custom views GET /api/{entity}?filter=xyz - YOUR filters This isn't about cramming everything into models or making things generic for the sake of it. It's about keeping your business logic clear and specific while eliminating repetitive technical code. Most of our CRUD boilerplate gone and for edge cases we still can write entity specific CRUD API's. so no flexibility lost and redundant code gone. What patterns have you found to reduce boilerplate while keeping business logic clear? Will love to hear your thoughts #SoftwareEngineering #TypeScript #WebDevelopment #CleanCode #DeclarativeCode

Ever wonder why we keep writing the same CRUD APIs over and over? Here's a controversial take: Your CRUD APIs should start generic, not specific. Yes, you read that right. Here's why this matters: Instead of creating multiple endpoints: POST /api/users POST /api/products POST /api/orders GET /api/users/:id GET /api/products/:id GET /api/orders/:id PUT /api/users/:id PUT /api/products/:id PUT /api/orders/:id DELETE /api/users/:id DELETE /api/products/:id DELETE /api/orders/:id You have one generic endpoint: POST /api/:model GET /api/:model/:query PUT /api/:model/:id DELETE /api/:model/:id "But wait!" I hear you say, "What about specific business logic?" That's where the real insight comes in - it's all about well-defined database models. Your DB models should do the heavy lifting: Validation rules? In the DB model. Computed properties? In the DB model. Business constraints? You guessed it - in the DB model. It's like switching to a declarative paradigm. Instead of spreading business logic across multiple API layers, you define it once in your models. Your API layer stays clean, focused, and most importantly - reusable. And here's the kicker - you can always add specific APIs when you actually need them. But why start there? Why write boilerplate CRUD operations for every entity when you haven't proven you need anything special? We've been implementing this approach in our projects, and the results are clear: 70% less redundant code Faster feature development More consistent API patterns Easier to maintain and test It's about separating the 'what' from the 'how' - letting your logic live once in the API layer, while your domain-specific needs are expressed through definitions in your models. Your "model" is just a definition file (JSON/TypeScript/etc) where you declare everything about an model: GET /api/:model/:query // This is the game changer Want active orders? Add a query definition. Need completed orders by region? Add another query. Want admins to see all orders but users to see only their own? Define roles per query: { queries: { activeOrders: { filter: { status: 'active' }, roles: ['admin', 'sales'] // Only admin/sales can access }, myOrders: { filter: (user) => ({ userId: user.id }), roles: ['user'] // Users see their own orders } } } The API stays generic, but your model definitions make it powerful and secure. Just ask /api/orders/activeOrders and the API knows what to return AND who can access it. What do you think? Are you still writing entity-specific CRUD APIs by default? Let's discuss! #SoftwareArchitecture #Engineering #TechLeadership #SoftwareDevelopment #CleanCode

At YourStory Media's 15th Edition of TechSparks, Yogesh Agarwal, founder of Locomo.io, emphasized the crucial role of providing context to AI when using it for software development. He delved into details of why it is important to structure the information given to AI and how on Locomo output of one step, becomes input for the next. Watch the highlights from TechSparks to understand how context-driven usage of AI can transform the future of software development! #Locomo #AI #SoftwareDevelopment #TechSparks2024 #YourStoryMedia Unthinkable Solutions

Big events need big support—and we’ve got just the partners to make it happen! 🚀 As we gear up for (Un)Conference '24, we want to take a moment to introduce the amazing partners who are making this event possible. These aren’t just any partners—they’re some of the most innovative companies out there, each bringing something unique to the table to make sure this isn’t just another run-of-the-mill event. Here’s who’s got our back - 🎯 Ecosystem Partners - - Bureau – AI-powered identity decisioning for risk, compliance and fraud monitoring. - OTPLESS – Streamlining next-gen authentication for a seamless user experience. - Cashfree Payments – Simplifying payments, empowering businesses to scale faster. - Locomo.io – All-in-one project management with unmatched speed and precision. - Segwise.ai – Builds AI Agents to improve your Game's LTV - Vahan.ai – AI chatbots scaling blue-collar workforce recruitment and payroll. - Plotline – Helps product teams to make quick app changes for onboarding and adoption. 🌟 Experience Partner - Infinyte Club – Creating liquidity for ESOPs and giving access to exclusive, high-growth investment opportunities. 🎨 Creative Partner - Bombay Locale – Blends art and business to help fast-moving companies craft impactful narratives. 💬 Community Partner - Indian Financial Forum – A community hub for fintech, payment and lending enthusiasts. These amazing partners are reshaping the future of products, tech and innovation. 🚀 We’re excited to have such amazing companies, each one adding their own spark to the event! 📅 Join us on October 19th in Bangalore for a day packed with connection, collaboration and creativity. 💬✨ RSVP now: https://lnkd.in/dhs5YMFu

Prioritising data enhancement, integrating robust cloud solutions, and securing networks are fundamental steps for effective AI deployment. Industry experts from tech startups discussed this and more at a TechSparks 2024 panel discussion titled ‘Building scalable and transformative AI systems.’ Know more. Sanjay Koppikar | Yogesh Agarwal | Brajesh De | Ankur Pal | Locomo.io | EvoluteIQ | Aplazo | Blue Altair

"AI needs context to respond meaningfully. The problem is that when you use AI randomly, you need to put in a lot of effort in giving context,” says Yogesh Agarwal, Founder & CEO, Locomo.io at #TechSparks2024

#ProductManagers, are you tired of managing multiple tools, only to still struggle with getting accurate project updates? Balancing communication across teams while ensuring the project stays on track can be a nightmare when everything is scattered. #Locomo simplifies your workflow by providing: 1️⃣ Single Source of Truth: Instead of juggling separate tools for requirements, architecture, and development, Locomo lets you capture everything—from user stories to release—on one platform. No more fragmentation across different tools 2️⃣ Linked Tasks and Artifacts: Tasks aren’t isolated from your project’s technical components. Each task is linked directly to key artifacts like database models, APIs, and test cases, ensuring that work is connected to real outcomes. 3️⃣ Iterative Development with Release Units: Break down large projects into smaller, manageable release units that align with business goals, like MVPs or specific version launches, allowing your team to work incrementally without losing sight of the bigger picture. 4️⃣ Team Progress Tracking: Keep track of which team members are handling specific tasks and which release units have been deployed. This insight helps you optimize resource allocation and identify where support might be needed to keep the project on track Locomo keeps your entire software development lifecycle structured and organized, so you can manage complex projects without needing multiple platforms. 🌐 Ready to simplify your workflow? Learn how: https://locomo.io/ #ProductManagement #ProjectVisibility #StakeholderAlignment #Locomo

🚀 Locomo at TechSparks 2024! 🚀 We’re proud to share that our founder Yogesh Agarwal, will be speaking in the AI Track of YourStory Media's TechSparks 2024—India’s largest startup-tech conference! For years, Yogesh has been on a mission to make software development more rewarding (and less redundant), and we’re eager to dive into how AI can shape the future of this mission during the event. If you’re attending, don’t miss the opportunity to meet Yogesh and engage in discussions about the future of tech, AI, and innovation. Let’s connect and explore new possibilities together! #LocomoAtTechSparks #TechLeadership #AIInnovation #Locomo #TechSparks2024 #Bengaluru

🚀 Locomo is Heading to (Un)Conference '24! 🚀 We’re excited to announce that Locomo will be participating in (Un)Conference '24, organized by The Product Folks in Bengaluru! As we continue to innovate in product development, this event is the perfect opportunity to share our vision and connect with fellow pioneers. If you’re attending, stop by and say hello! Let’s connect, share ideas, and explore the future of tech together. 💡 #LocomoAtUnconference #AIInnovation #ProductLeadership #TechFuture #Locomo #Bengaluru

Every software project starts with a vision, but bringing that vision to life can be overwhelming. That’s why we built Locomo—to take the guesswork out of managing complex software projects. Locomo is a project management tool that helps teams streamline their entire SDLC—from building the backend to managing releases—without the usual chaos. Designed for product managers, developers, and fast-moving teams, we simplify complex projects, keep everything in one place, and ensure you stay focused on what matters: delivering exceptional products. Ready to transform your workflows and turn your 'What ifs?' into action? Talk to our expert: https://locomo.io/ #Locomo #SoftwareDevelopment #ProductManagement #FromVisionToLaunch