Wrote a bit on how I built 🟠Orin
The architecture, the voice pipeline, and the trickiest part: getting the personality to actually sound human
Full writeup here: https://t.co/AU9yVfl6Iu
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.
This is generated without a single decorator, with zero doc-blocks and all through inference.
We never had an OpenAPI spec generator, because I was never a fan of shallow docs (just print the routes) or write docblocks which very quickly goes out of sync from the actual code.
But, not anymore. Building on top of the great work done by @andrejadamcik
@darasoba Because i'm trying to learn while i'm building the feature - taking notes, asking the AI questions that take me deeper into the rabbit hole and this takes time but someone that already knows what they want to do because they know the fundamentals, just gives the AI specifics.
@darasoba From my personal experience, learning the fundamentals would help you move faster with AI. Every single time i've had to rely on AI to generate code for a feature I have no technical knowledge about, it end up spending longer time (which ends up being the same as writing by hand)
@hyojun_at just tried it and onboarding was a little buggy for me - slow, clunky and saw some error screens during onboarding and no tab groups yet? :(
@BHolmesDev Been looking for this man, I needed something to help me document what I learn as I build with agents, was using obsidian and had to create a skill so my agent could also contribute to my notes but it was really slow and tedious, would try out hubble. Thanks
Ask Nexus UI anything — right in the docs.
I built an AI chat panel across the docs site: open it with the floating button or ⌘/, ask in plain language, and get a streamed answer that is grounded in the actual documentation.
Under the hood, I implemented a RAG pipeline that chunks and indexes every doc page, the Nexus skill reference, and component source code — then pulls the best chunks into context before the model replies.
If something’s missing, it can run a local search tool to pull more before finishing.
Built with @nexus__ui and @shadcn primitives, @aisdk, and FlexSearch.
Like I will always say - when it comes to these conversations, we have moral responsibilities to keep our voices loud.
What happened last week is horrific. Children under the ages of 2 are still kidnapped.
It isn't normal.
@seyimakinde what is going on?
Just shipped: an OpenAPI generator for @adonisframework .
Drop it into your app, get a spec out. Works with your existing routes, validators, models. No annotations needed.
Open source, built at @madebyoutloud .
https://t.co/4CXW39GYb3
Being a "backend engineer" is not a skill.
It's a department.
Moniepoint posted roles, struggled to find qualified Nigerians, and Nigerians on the internet showed their displeasure.
But still, nobody touched the actual problem.
This thread will make some of you uncomfortable.
That's fine.
It's only a problem for people who don't read with an open mind.
After 3 days of claudemaxxing I've successfully built a home grown openAPI generator for my @adonisframework project that documents itself from the source code and this means 0 decorator usage.
It just scans the controller and automatically generates accurate specs.