I’m looking for the right remote role for the next five years. Not because I’ve stopped building independently. Because I want to experience what becomes possible when the range I’ve developed is combined with an ambitious team, global distribution, serious resources, and problems operating at scale. Today, I: • Lead Sails.js, actively maintaining the framework, shaping its direction, and growing the ecosystem around it • Build The Boring JavaScript Stack • Build Slipway, a deployment platform for Sails applications • Run Sailscasts, where I teach developers to build full-stack JavaScript applications • Publish The African Engineer, covering how technology is built across Africa • Build Hagfish, an invoicing product for creators and independent professionals • Consult with companies on engineering, architecture, products, and developer experience • Write, teach, speak, lead, and build in public I have spent years operating across software engineering, open source, infrastructure, education, media, product, community, and business. Now I want to bring that experience into the right global technology company. I’m looking for a role where I can build software, lead technical initiatives, improve developer experience, teach developers, write, speak at conferences, shape products, and help grow an ecosystem around important technology. I do my best work in an environment that is: • Remote and async-first • Low-meeting and high-trust • Flexible rather than rigidly 9-to-5 • Built around deep work and strong written communication • Focused on outcomes, quality, and impact • Compatible with responsible open-source and independent work I don’t want to perform productivity. Give me meaningful problems, clear context, ownership, talented teammates, and the freedom to deliver excellent work. Above all, I want to work on something I’ll be proud to attach my name to. I’m especially interested in Developer Experience, Open Source, AI Developer Platforms, Staff Engineering, Developer Relations Engineering, Developer Education, and Technical Ecosystem roles. If your company needs someone who can build the technology, understand the developer, explain the product, teach the market, and grow the ecosystem around it, let’s talk. Reposts appreciated.

Week 8 of building Kuda's core banking system. Visible progress: Zero endpoints. Zero APIs. Zero features. CEO's patience: Running thin. Most teams would panic. Ship something. Show progress. Kuda's engineers held the line: "After this foundation phase, it will be boom boom boom. We'll sprint features out quickly." They were right. The next 4 months: Rapid feature delivery. Today: Same foundation serves 10 million customers. The lesson? Mission-critical systems need invisible work first: • Service contracts • Database schemas • Observability stack • Deployment pipelines Budget 30-40% of project time for "nothing to show." It's not nothing. It's everything. africanengineer.com/i/kuda-n…

It always gladdens my heart to see folks using the free open-source gift that @mikermcneil has given us in Sails—along with my little addition, The Boring JavaScript Stack—to build actual products, not just demo apps. Bravo, @Julius_Java00!