Timothy Okooboh

@peculiarerhis "But every day, I woke up and put in the work, and sometimes, that’s all you need to do." That's fantastic!!!

@ndukwe_emeka_ @Dominus_Kelvin but are all the components it's building from scratch WCAG compliant? You can still build a UI lib for your product by letting AI build on top of an accessible headless lib like shadcn, etc. Some accessibility requirements are hard to get right when you re-invent the wheel.

@Dominus_Kelvin This, Currently building mine for my Product... I am not Shadcn UI, I'd just tell Ai what I want and it gives me the components Code.. Though I am not Vibe Coding the application, Just using AI to fasten take that might take long time

You probably don't need a UI component library thanks to AI.

@Dominus_Kelvin To avoid accessibility issues, I connect my Figma design to the agent via Figma's MCP & tell the agent to create a UI lib of the base components in the design but on top of @shadcn while leveraging my brand colors & typography. Next, a storybook app with the docs & playground.

Open any app you've built with AI. Find a dropdown. Open it. Now click anywhere else on the page. Did it close? Now press Escape. Did it close? If the answer to either is no — congratulations, you shipped an interaction bug that every single user will hit. Not a power user. Not an edge case. Everyone. This is the most common UI bug I see in every codebase I interact with. Vibe coded or not. Solo builder or big engineering team. The dropdown opens fine. Nobody built the dismissal. AI generates the dropdown in seconds. What it doesn't generate is the part where it actually behaves like a real UI element. Here's the fix. One composable or hook. Handles click-outside and Escape. Cleans up after itself on unmount. One line to use: useClickOutside(dropdownRef, () => { isOpen.value = false }) Dropdowns. Context menus. Popovers. Modals. Slide-overs. If a user can open it, clicking outside it should close it. That's not a nice-to-have. That's a contract. This is one of 8 patterns I teach in my new course — Building Durable UIs in the Era of Vibe Coding. State placement. Click-outside dismissal. Form draft persistence. Navigation contracts. The decisions AI can't make for you. → sailscasts.com/courses/durabl…

@Dominus_Kelvin 😀😀

@inspiretim24 Now go buy the course 🥹😅

The Zombie Sidebar Your user closes the sidebar. They navigate to the next page. Sidebar is open again. Close it. Navigate. Open again. Close. Navigate. Open. A loop that should not exist. localStorage fixes it in 3 lines. Build Durable UIs with this course → sailscasts.com/courses/durabl…

@Dominus_Kelvin You are welcome

@inspiretim24 Fixed. Thanks

@rielcodes @yehhmisi 😀 I can relate

@inspiretim24 @yehhmisi Failed a LeetCode test at an interview once. I was just shaking my head for like 3 days straight.

There’s this guy I recommended for a software engineering role but he wasn’t able to pass the interview. Like I’m very sure he’s a cracked dev I just can’t prove it because he’s not able to pass the interview. It’s very sad😔

@yehhmisi Hmm, that's sad

@inspiretim24 There was no DSA on this one

@Dominus_Kelvin I like your collection of books on the Christian faith. It's inspiring to see. It shows that there is more to life than always writing code.

I love how I build and write on dominuskelvin.dev

@yehhmisi 😀

Someone invited me for a live coding podcast. So the idea is to code live while people are watching me. So like I’ll just be writing code and people will be watching me😳😳😳.

@SumitM_X Pagination (offset-based) if the data does not change too frequently and it's important for the UX to allow jumping to specific pages. Infinite scroll (with cursor-based pagination) if the data changes too frequently i.e real-time e.g a news feed, comments thread, etc.

Your web application that needs to display millions of records. You have two UI approaches: Pagination Infinite Scroll When would you choose Pagination over Infinite Scroll, and when would Infinite Scroll be the better choice?

@notnulldev @SumitM_X My response had no mention of "functional programming" and nowhere did I say, "Everything that is not pure is bad." functions !== functional programming. Even classes have methods (functions).

@inspiretim24 @SumitM_X Kinda bad take. Functional programming langaues are not popular for a reason. Pure functions are good for many things but saying that everything that is not pure is bad is a big overstatement.

Option A or B ? Which is correct ?

@_jaydeepkarale That's what I've been going through for some time. Highly recommended.

Or just watch these 23 videos, they'll change how you approach backend engineering forever youtube.com/playlist?list=…

@readswithravi Build a frontend web framework (from scratch)

What book are you kicking off your 2026 with?

@MichaelThiessen "Pointless", hmm that's a strong word. I love the tips you share, especially after buying two of your courses. But I get what you mean. Now, knowledge is cheap. I think posts/courses about best practices, trade-offs, and how things work under the hood are more valuable than ever.

I used to post lots of Vue tips on here, but now that feels more and more pointless. What kind of content do you want to see in your feed?

@MichaelThiessen @vuejs I have. But later, I moved the composables to their own file, LOL.

Have you ever made an "inline" composable in @vuejs? If not, there are some good use cases for it. At the very least, it teaches you some useful things about how Vue and its reactivity works. michaelnthiessen.com/inline-composa…

@RhysSullivan I built my own way of styling Vue.js applications, and it's via a plugin that exposes a polymorphic component with built-in styling capabilities veebox.xyz

share what you built in 2025