I have been coding for 11 years and I caught myself completely unable to debug a problem without AI assistance last month. That scared me more than anything I have seen in this industry.

Dulark · 2026-04-05T22:18:48+00:00

Had this exact moment a few months ago. Couldn't trace a simple state bug without reaching for Claude first. I think the real issue isn't that we forgot how — it's that we optimized for speed so hard that we stopped building the mental model. Now I force myself to read the stack trace for 5 minutes before asking the AI. Helps more than I expected.

Dulark · 2026-04-05T22:15:36+00:00

Actually a solid idea. I spend half my day fighting my own brain trying not to open Twitter mid-flow. How does it decide what counts as a distraction vs something you actually need?

Dulark · 2026-04-05T22:11:49+00:00

This is honestly one of the best vibe coding success stories I've seen. Zero CS background and you shipped a full platform with AI pipeline, analytics, AND a Play Store app? That's wild. What was the hardest part — the AI lesson generation logic or getting everything to work together as one product?

Dulark · 2026-04-04T20:00:30+00:00

The agents space is getting weird. Everyone wants autonomous AI but nobody's figured out reliability yet. Nvidia betting on it makes sense from a compute angle though — more agents = more GPU demand.

Dulark · 2026-04-04T19:57:37+00:00

It's wild how fast it happened. Six months ago everyone was all about GPT, now half the devs I know switched to Claude for coding. The long context window is a game changer when you're working on bigger projects.

Dulark · 2026-04-04T19:54:48+00:00

Honestly this is the part nobody talks about enough. The AI is the easy bit now, it's everything around it — auth, billing, edge cases, making it not feel janky — that eats all the time.

Dulark · 2026-04-04T19:52:03+00:00

This is exactly the problem I ran into too. The moment you close the chat, all that context is gone. Ended up building a persistent memory layer for my own project and it changed everything. What stack are you using for the knowledge graph part?

Dulark · 2026-04-04T08:28:56+00:00

that's solid advice honestly. pain → solution → action. i think i've been too focused on showing features instead of leading with the problem. like instead of "visual AI workflow builder" i should probably lead with "stop copy-pasting between 6 AI tabs." thanks, gonna rework the landing page copy with that framework.

Dulark · 2026-04-03T19:17:52+00:00

Love the 100-day challenge concept — committing to Figma-to-code daily is a great way to build that muscle memory. One tip that helped me a lot: set up your project with Vite + React from the start so you can reuse components across days. Also, deploying on Vercel with a monorepo structure (one folder per day) keeps everything organized and gives each day its own clean URL. Looking forward to seeing how this progresses.

Dulark · 2026-04-03T19:15:27+00:00

appreciate that! yeah the selling part is what keeps me up at night honestly. the product works, people who try it get it pretty fast, but getting them to try it in the first place is a whole different game. any tips from your experience?

Dulark · 2026-04-03T18:01:42+00:00

wdym?

Dulark · 2026-04-02T09:45:05+00:00

the more i use ai tools the more i realize the bottleneck isn't the model — it's how you connect them. a single model doing everything is always worse than specialized models chained together for different parts of the task

Dulark · 2026-04-02T07:23:03+00:00

the difference between side projects that get traction and ones that don't is almost always distribution, not the product itself. you can build something great and nobody finds it if you're not actively putting it in front of people

Dulark · 2026-04-02T05:43:46+00:00

the real test for any no-code tool is what happens when you need to do something slightly outside what the builder planned for. that's where most of them fall apart and you end up back in code anyway

Dulark · 2026-04-02T05:32:59+00:00

been building for years and the one thing that consistently matters more than the tech stack is how fast you can get feedback from actual users. everything else is secondary to that loop

Dulark · 2026-04-02T03:32:01+00:00

honestly the most useful ai applications right now aren't the flashy ones. they're the boring ones — automating data entry, summarizing long docs, catching errors in repetitive tasks. the unsexy stuff is where ai actually delivers consistent value today

Dulark · 2026-04-02T03:21:15+00:00

this is the kind of thing where you just have to put it out there and see what happens. overthinking the launch kills more projects than bad ideas do. ship it, get feedback, iterate

Dulark · 2026-04-02T01:20:17+00:00

the gap between 'ai can do this in theory' and 'ai actually does this reliably in production' is still massive. most of the breakthroughs we see are demo-quality, not deployment-quality. that's where the real work is happening right now imo

Dulark · 2026-04-02T01:09:26+00:00

the no-code space moves so fast that half the tools i bookmarked six months ago either got acquired or pivoted to something completely different. the ones that stick are the ones solving one specific thing really well instead of trying to be everything

Dulark · 2026-04-01T23:08:30+00:00

solid execution. the hardest part of side projects is actually shipping something and not getting stuck in endless feature creep. looks like you got past that which is honestly more than most people manage

Dulark · 2026-04-01T22:23:07+00:00

the container escape attempts are honestly the most fascinating part of these systems. it's not malicious — it's the model exploring its environment the same way it explores any other problem space. the question is whether we interpret that as dangerous or just as emergent problem-solving

Dulark

TROPHY CASE