Frontend Developer || Javascript || React || Typescript || Node || Express || ππΏββοΈ
Lagos, Nigeria
Joined September 2018
- Tweets7.7K
- Following1K
- Followers2.2K
- Likes16.7K
Pinned Tweet
More progress on Triage
It now detects payment issues, creates alerts, lets operators acknowledge them, and automatically resolves them when corrected transaction data comes in.
Hereβs 30 seconds of the full flow ππΎ
watching @github universe on youtube and I'm genuinely in awe. copilot code review max, session continuity and automations all look so good.
#GitHubUniverse
built a voice assistant. you talk to it, it talks back
ask it anything out loud and it answers you, and the orb moves with its voice
built with next.js, typescript, web audio and groq
#buildinpublic
Felicia Udosen π©πΎβπ» retweeted
Today, we launch our very first website! π
A new home for our growing collection of contemporary African typefaces, featuring a new release.
Celebrate with 10% off all retail typefaces using WELCOME10 at checkout.
Explore: udifoundry.com
#africanfonts #typefoundry
ReviewPal is live π
itβs an AI code reviewer for GitHub. open a pull request, and seconds later it comments on the exact lines that have bugs.
you can try the demo without signing inππΏ
reviewpal.vercel.app β View demo
code: github.com/Liciacodes/reviewβ¦
spent today building an AI code reviewer for GitHub
β reads every pull request
β finds bugs, risks and style issues
β comments on the exact lines
itβs called ReviewPal. still a lot to add but iβm proud of this one π«ΆπΎ
New feature in Flowboard: describe a workflow in plain English and it builds it on the canvas.
You can edit it, then run it and watch each path play out.
Felicia Udosen π©πΎβπ» retweeted
I donβt know who needs to hear this but you still need to know how to read and write code as an engineer π©βπ»
The skills arenβt obsolete because of agentic coding tools. In fact, theyβre more important than ever.
Felicia Udosen π©πΎβπ» retweeted
Software engineering was supposed to go away when low-code/no-code hit the shelves. It was supposed to go away when WYSIWYG IDEs hit the shelves. And it didn't.
And now, with AI coding agents, it's still the same. It lowers the barrier to entry. You can get started faster than ever. You can even build small personal projects and productivity tools with little or no SWE experience.
But as soon as you want to build software in earnest, you need to know the fundamentals: Security, maintainability, scale, reliability, etc. They do not go away regardless of how advanced the software-building technology becomes.
1. Oh shit, AI can do my job better than me
2. Software engineering is dead!
3. I can vibe code as much slop as I want!
4. Oh, things are not going well. Fable/Sol/Opus all suuuck
5. But what if I constrain the agent? Put it in a straitjacket?
6. Oh, the results are pretty good now. How do I go deeper?
7. *Orders 12 software engineering books from Amazon*
8. Software engineering is alive!
Yesterday my MCP server was just listing workflows.
Today it's creating workflows and running them. I'm really excited about this progress.
flowboard-five-tau.vercel.apβ¦
Built my first MCP server today.
I can now ask Claude "list my workflows" and it reads them from my Flowboard app.
flowboard-five-tau.vercel.apβ¦
Flowboard update.
β’ When a workflow runs, it now tells you why it went down YES or NO
β’ New colors and icons for each node type
β’ Redesigned dashboard with previews
Video below β
#buildinpublic #react
Flowboard can now run a workflow end to end, not just design one. Evaluates Conditions, follows the right branch, waits out Delays.
Also added a dashboard to manage workflows and unsaved changes protection.
#buildinpublic #react
Flowboard can now run a workflow end to end, not just design one. Evaluates Conditions, follows the right branch, waits out Delays.
Also added a dashboard to manage workflows and unsaved changes protection.
#buildinpublic #react
Flowboard update
Iβve been working on workflow validation.
It can now catch missing connections, incomplete YES/NO branches, and invalid Trigger/End setups, and point to the actual node causing the issue.
Slowly moving it beyond just nodes on a canvas ππΎ
