Built two internal dashboards for two different clients in just two days. The speed did not come from AI alone. It came from having structure before writing any code. Clear product docs defined features, goals, and constraints early. Separate coding standards for frontend and

Experimented with a video editing tool that detects filler words, and silences, then cuts them automatically. Built with VAD, speech-to-text, and simple timeline editing. Surprisingly effective for speeding up rough cuts.

Build it once, build it right, and spend your energy on your customers, not your codebase.

Designers will be able to code Coders won’t still be able to design

Tailwind’s biggest underrated win was standardizing relative units. Without it, half the web would still be hardcoded in pixels because many devs ignored the difference between px and relative units. Tailwind made the better way the easier way.

If changing one feature feels risky, the problem is not the feature.

LLMs are so habituated to lucide-react that switching to any other icon library is a constant battle. Tell Claude to use phosphor-icons? It’ll forget in 3 prompts and try installing lucide again. Ask it to use heroicons? Two iterations later, lucide imports are back. It’s like

Started my morning by shipping a mobile app to production. Either I'm getting really good at this or I'm about to learn what I forgot to test. 🤞

Steve Jobs revealed the secrets of taste and craftsmanship:

AI can write frontend code fast. Shipping it to production is a different story. I reviewed a dozen AI-heavy projects and documented the most common performance, UX, and maintainability issues I kept seeing, plus how to avoid them. Read here 👇 karishma.dev/blogs/ai-gener…

2026 is off to a good start. Let’s see how long I can keep the streak alive.

I was talking with a client recently who was frustrated with their previous site build. They had a custom brand identity ready to go, but their developer pushed back on almost every detail. The reason? "It’s better to stay within the default theme settings so nothing breaks."

Every year there’s a phase where I’m like: “Maybe I should just become a designer.” 😅 Then I open Figma… and go back to my terminal.

Thinking you know everything is the fastest way to become obsolete.

Search bars and filters on empty pages make no sense. There is nothing to search, nothing to filter, nothing to sort. Yet many products ship their empty states with the full UI anyway, because it is just the same screen template with no data. From a new user’s point of view,

Didn’t realise Gemini Flash could code in Chinese now 😭😭....

With AI everywhere, I keep wondering: will websites and apps remain primary, or will chat interfaces slowly take over most user flows?

I turned off my WiFi to see which apps actually planned for offline. Most didn't. Infinite spinners for content that was just on screen. Blank states for articles I was literally reading 5 seconds ago. But two apps handled it extremely well: - Amazon shows a dedicated offline

Have you ever gotten annoyed by the Back button on a website? It's usually not broken. It's just built around the wrong mental model. Developers usually think of a "new page" as a new route in code. Users don't think like that. For users, if a view looks different enough or

😂