Just in case you are new here, I’ve been writing about software, sharing what I learn and building things for other developers since 2018. There are over 130 articles and blog posts across my archives alone. There are open-source projects, tutorials, documentation, videos, live sessions, a community and a conference. So when someone says I “charge for every damn thing” and starts questioning whether I love software, I have to wonder how much of my work they’ve actually looked at. Let me help with that. In 2018, I was writing about what I learned at Google I/O Extended in Warri and sharing resources for people getting into programming. I was writing about CSS, Emmet, and how I recreated a button design I liked, with the code available for anyone who wanted it. I was learning, getting excited about things, and writing them down. By 2019, I was sharing how I built with Vue and Sails, uploaded files, used Cloudinary and deployed applications. There’s an article about a file-upload problem I struggled with, eventually solved, and then explained so the next developer wouldn’t have to struggle with it too. You can still read those articles: omereshone.com/articles/ I went on to write for Smashing Magazine, LogRocket and other publications. Node.js error handling. API testing with Postman. Docker volumes and bind mounts. Desktop applications with Tauri and Vue. Accessibility. A four-part Mirage JS series covering models, relationships, factories, fixtures and testing with Cypress. I wrote a Sails API tutorial that takes you through registration, login, email confirmation, password resets, testing and deployment. The sort of thing you can sit down with and use to build an application. smashingmagazine.com/author/… blog.logrocket.com/building-… Some publishers paid me for that work. Readers could learn from it without paying me. I think more developers should have opportunities like that. Getting paid to explain something well, while making it available for others to learn from, is a good arrangement. I’ve kept writing on my own blog too. Things I’m learning, approaches I’m trying, things I disagree with, and problems I’ve worked through. There’s plenty there, whether you agree with my opinions or not 😂 omereshone.com/blog/ Then there’s Sails, a framework I am obsessed with. I found a framework I enjoyed, started building with it, wrote about it, taught it and kept contributing to the work around it. In 2023, I became the lead maintainer of Sails.js. Mike McNeil created Sails. I’m part of the continuing work on it, alongside the other people who contribute. blog.sailscasts.com/announci… You can use Sails to build your application today. You don’t need to buy a course from me or pay me for permission to use it in your business. It’s free and open source. And I’ve spent years building around it. I built Sailboat to make working with Sails in VS Code easier. That later gave way to Sails Language Tools the official editor tooling for Sails, which includes the language server and the official Sails VS Code extension. Completions, navigation, diagnostics, quick fixes and generators. The things that help when you’re actually sitting in an editor trying to get your application working. github.com/sailscastshq/sail… github.com/sailshq/language-… I created The Boring JavaScript Stack because I wanted to provide a straightforward, enjoyable way to build full-stack JavaScript applications. That will cost you $0 and you can ship a whole SaaS with it, everything I have built so far is made with it and I am not the only one using it for FREE Sails, Inertia, Tailwind, and your choice of Vue, React or Svelte. A setup you can start with and get on with building your product, instead of spending all your time assembling the starting point. That code is available under the MIT licence. You can read it, use it, change it and build commercial products with it under that licence. You don’t have to buy anything from me first. github.com/sailscastshq/bori… There’s Inertia Sails, the adapter connecting Sails applications to Inertia. There’s Shipwright, the asset pipeline for Sails applications. There’s Sails Mail, for sending email from your application. There’s Quest, for scheduled jobs and background work. There’s Sails Pay, to help developers integrate payments into their Sails applications. The library is open source. You can inspect how it works and build on it. github.com/sailscastshq/sail… There’s Sounding, the testing framework for Sails and The Boring JavaScript Stack. It covers helpers, endpoints, JSON APIs, Inertia pages, email and browser flows, using Node’s test runner and Playwright. You’ve built the application. Now you need to check that it actually behaves properly. Sounding is part of the work I’m doing to make that easier for people using this stack. github.com/sailscastshq/soun… There’s Slipway, the self-hosted deployment platform for Sails applications. You can run the open-source software on your own infrastructure. github.com/sailscastshq/slip… There’s Pellicule, for creating and rendering videos with Vue components. github.com/sailscastshq/pell… These are things I build because I want to use them and because I think other developers will find them useful. The code is there. The documentation is there. Other people can contribute, improve things and use them in their own work. And people do contribute. I’m grateful for that. This isn’t me claiming I wrote every line or invented all the technology these projects use. You can explore more of the work here: docs.sailscasts.com/open-sou… github.com/sailscastshq github.com/sailshq/sails-hoo… There’s also Teach Kelvin Your Thing. I invite people to come and teach me something, and we make the conversation available for other people to learn from too. Matt Pocock teaching TypeScript. Harminder Virk building with AdonisJS. Carson Gross working with HTMX. People who know their tools deeply, sharing how they think and work. There are 67 sessions listed in the archive. You can go and watch them without paying me. omereshone.com/tkyt/ youtube.com/@dominuskelvin I love being able to ask questions and work through something with the person who understands it. Sometimes the question I’m asking is exactly what someone watching also wanted to ask. That’s a big part of the fun for me. Then there’s the Sailscasts Community. I wanted a place where people building with Sails could find each other, ask questions, share projects and help one another. We kept growing that community, and in 2025 it became the official Sails.js Discord community, through the collaboration between Sailscasts and the Sails core team. Yes, the community I started grew into the official community for the framework. blog.sailscasts.com/announci… I organised the first Sailsconf in 2021 too. It had free tickets. Three days of people sharing their knowledge, with recordings available afterwards. blog.sailscasts.com/sailscon… More recently, I’ve been building FLOSSAfrica. I want African open-source maintainers to be easier to discover and support. There are people here doing useful work that deserves attention and funding, and I’m building something to help with that. I’m a maintainer myself. I know that maintaining a project continues long after the excitement of releasing it. People keep using it. They find problems. Dependencies change. Documentation needs attention. There is always something to do. FLOSSAfrica is part of my effort to get more support behind that work. flossafrica.com/ So when you look at the writing, the teaching, the tools, the community and the work on funding maintainers, I genuinely don’t know how you arrive at “charges for every damn thing.” Do I have paid products? Of course. I sell software, courses and services. I’m building a business, and I want it to succeed. I’m quite open about that. If I build something useful and put a price on it, you get to decide whether it’s worth buying. You can decide it isn’t for you. You can disagree with the price. You can criticise the product. That’s completely fine. I don’t need to pretend I’m uncomfortable with making money from software to prove that I enjoy building it. I also don’t need every person using my free work to become a customer. Use the tools. Read the articles. Watch the sessions. Learn something. Build something of your own. That’s why I made them available. But at least look at the work before making claims about it. You might have first encountered me through a paid product or a post promoting something. There were years of work before that post, and much of it is still available for you to explore without buying anything. github.com/dominuskelvin I’ve been doing this since 2018. I still get excited tinkering with things. I still want to know how things are built. I still enjoy explaining something I’ve finally understood and seeing another developer put it to use. I have a lot more I want to build, and a lot more I want to share. You don’t have to buy anything from me, folks. But saying I don’t love software because you saw a price tag is a very strange way to read all of this.

also If one side of your app experiences much heavier traffic consistently then it makes sense to extract it to a separate service that you can scale appropriately

Service-to-Service Failure You have two backend services: Service A: Order Service Service B: Payment Service When a user places an order, Service A creates the order and then calls Service B to process the payment. Question: What could happen if Service B successfully processes the payment, but the response never gets back to Service A because of a network failure? How would you design the system to handle this scenario without charging the customer twice?

Devs ! Whats missing in this?

First day @PlanetScale today, super excited to get to work on the Postgres core team.

I can’t wait to go back to the time when we code without AI

People are treating this dangote IPO thing like it’s 2012 bitcoin

People on x be like 1. Learn HTML . 2. Learn CSS. 3. Learn JavaScript 4. Get your first job which job?😂

Designed a URL shortener that handles 100 million requests/day , built and tested it in a sim tool.

Cover letter for a job Use this template and thank me later

this interviewer told me to share my screen! the moment he saw i was using linux and cli to open my ide, he was like “let’s just skip the coding part” 😹🤝

CEO: Guys, the app is down. Backend Engineer: What changed? Frontend Engineer: Nothing from my side. Backend Engineer: Nothing from mine either. DevOps: I didn’t deploy anything. CEO: So who broke production? Everyone suddenly becomes very quiet. Intern: I changed something yesterday. Everyone: WHAT DID YOU CHANGE? Intern: The backend base URL. DevOps: … Backend Engineer: … CEO: … Assume yourself as the CEO will you get the guy sacked or not ?

Since I started my journey as a front end developer, I can boldly say this, someone who hasn’t been a designer or have a strong visual prowess cannot succeed as a front end developer.