Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Optimizing for Efficiency: How Rails Helps Elim...

Avatar for Ganesh Kunwar Ganesh Kunwar
September 12, 2025
6

Optimizing for Efficiency: How Rails Helps Eliminate Development Waste

Software development is often slowed down by hidden waste; things like tech debt, team dependencies and poor communication. In this talk, we’ll explore how to spot these inefficiencies and Rails framework helps to eliminate those waste and boost efficiency of development team

In this talk, we’ll explore the common sources of waste in software development, and how they impact project timelines and costs. We’ll discuss practical strategies for minimizing waste, improving team productivity, and delivering high-quality software more efficiently and effectively with Ruby on Rails framework.

Avatar for Ganesh Kunwar

Ganesh Kunwar

September 12, 2025

Transcript

  1. F/E DEV React, Vue, Nextjs, or Angular? Should I use

    TypeScript or plain JavaScript? How to structure the project? Feature- based, component- based, or by domain? Should I mock APIs or wait for the backend team?
  2. B/E DEV Should we use Node.js, Go, Python, or something

    more scalable like Java or Elixir? REST is simple, GraphQL is flexible, gRPC is fast—what suits the product best? Should I wait for the frontend to finalize requirements or start building based on assumptions?
  3. Is Design Ready? BISHAL (F/E DEV) Let me check; SANTOSH

    (DESIGNER) Is API Ready? HIRA (B/E DEV) Give me 2 Hours.
  4. B/E DEV Hi, Could you please review my PR? I’m

    having lunch, Give me 10 Minutes. ANOTHER B/E DEVELOPER
  5. What’s the best way to run this locally? I’m getting

    a bunch of errors. New Member What is the issue? Sr. Developer connection to server on socket "/ tmp/.s.PGSQL.5432" failed: FATAL: database “ganesh12" does not exist Give me 10 minutes, I will check.
  6. RITESH (PM) Hey, Are features ABC, XYZ ready for release?

    There are 3 small bugs, I just reported. BIMAL (QA)
  7. RITESH (PM) Hey, did you get confirmation from client? NIHAL

    (BIZ DEV) Sorry Man! I’m still waiting for client. NIHAL (BIZ DEV) Hey John, Is there any update for me? JOHN (CLIENT) Hi Nihal, Give me few more days. Thanks BISHAL (F/E DEV) SANTOSH (PD) Is API Ready? HIRA (B/E DEV) Give me 10 Minutes. One parameter is still missing in API! Is Design Ready? Client is Reviewing it. HARI (B/E DEV) Hi, Could you please review my PR? I’m having lunch, Give me 10 Minutes. RITESH (PM) Hi Bimal, Are features ABC, XYZ ready for release? There are 3 small bugs, I just reported. BIMAL (QA)
  8. Unnecessary Meetings Its better to add QA list in Kanban

    board. Design column list as well. Lets create Review List to list all items. Ad-Hoc Problem Solving Meeting
  9. Its better to add QA list Design column list Lets

    create Review List Ad-Hoc Problem Solving Meeting Hey, Mr Ritesh Let’s use Client Meeting Lets Try, ClickUp Lets use GitHub Action Dev Team Meeting 20% Sprint Meeting Unnecessary Meetings
  10. Hey, just checkin what’s the main Agenda of this meeting

    today? Who is taking notes? We’re 30 minutes over—should I join my next meeting? We’ve covered a few agendas already— should we wrap up or continue to the next one? Most of the meeting
  11. Waste Waste is something which consumes unexpected: - Time -

    Cost - Resources in Software Development Complex Process Waiting Meeting Poor Planning
  12. - Monolith Architecture, All-in one stack, no Need for separate

    Frontend & Backend - Action Cable: Built in webSocket Support for Real-time Features - Inbuilt Testing Framework: No separate framework/libraries needed for automation - Hotwire/Turbo/Stimulus: Less JavaScript, More Speed - Rich Ecosystem of Ruby Gems - Easy to learn: Beginner friendly, Developer-productive - Kamal: Makes DevOps feel simple—even for small teams. What Rails Offer Us?
  13. } No More Dilemma for framework selection Any Developer can

    review anyones codebase Reduced Team Waiting Time No more meeting needed for anything Codebase is readable, anyone can pick any project
  14. No More Dilemma for framework selection Any Developer can review

    anyones codebase Reduced Waiting Time Codebase is readable, anyone can pick any project No more meeting needed for anything }Reduced New Dev Onboarding Time }
  15. No more meeting needed for anything Reduced Meeting Time }

    No More Dilemma for framework selection Any Developer can review anyones codebase Reduced Waiting Time } Codebase is readable, anyone can pick any project } Reduced New Dev Onboarding Time
  16. No more meeting needed for anything Reduced Meeting Time Reduced

    Waste } } No More Dilemma for framework selection Any Developer can review anyones codebase Reduced Waiting Time } Codebase is readable, anyone can pick any project } Reduced New Dev Onboarding Time
  17. We Do Mistake as well: - Miss to Follow Best

    Practices - Fail to Update README.md and other documents - Overusing Scaffolding Without Cleanup - Messy, Unstructured Code ("Vibe Code") Pollutes the Product. - Inconsistent Code Style - Not Updating or Locking Gem Versions - Neglecting Test-Driven Development (TDD) Due to Laziness.
  18. - You can not eliminate 100% waste; You can reduce

    waste. - Waste in software development are not visible, You have to open your third eye to see those waste. - Feeling like your software process is getting out of hand? Start by identifying and eliminating waste. - Automate whenever possible - Keeping the Waste in mind, explore technology/frameworks and help to improve them Final Thoughts
  19. About Me - Ganesh Kunwar - Co-founder & Director of

    Project Delivery - Maintainer #BuiltWithRuby - 13+ experience in building Software Product & Product Teams - Ruby Nepal Community Member - Agile Nepal Community Member - Atlassian Nepal Community Member