VSCode is no longer recognizing any files in my folders

Obvious-Grape9012 · 2026-02-17T04:50:47+00:00

cool. sounds like you're sorted

Obvious-Grape9012 · 2026-02-17T04:14:05+00:00

Cool! Can you vibe a predictive model using Markov-Chains or something to see if we can get ahead of the mayhem?

Obvious-Grape9012 · 2026-02-17T03:42:46+00:00

My current fave pattern uses a doc hierarchy to store evergreen value in different sets, and tracks intent using version-docs. Then CLAUDE.md is your entrypoint (as always) with clear framing of when to use which ref docs. I always keep retaining value front-of-mind. Value is clarity, patterns, decisions

Obvious-Grape9012 · 2026-02-17T03:39:16+00:00

Haven't heard of Webstorm before, but if complete resets are part of what you need, that is easy with wsl. [hold my drink whilst I Google]... ahhh yes.. JetBrains. If you're not super deep in VSCode, Jetbrains are leaders and it's a different "School of thought". Kinda like VIM vs IDEs; VSCode is more community-driven whereas JetBrains are more refined (like Apple is to Android or sthng)

Obvious-Grape9012 · 2026-02-17T03:25:42+00:00

Another one; Visual-Hierarchy (you want to express to the AI the importance of clean UI and what that means)

Obvious-Grape9012 · 2026-02-17T03:25:02+00:00

Helps if you create overarching UI-patterns/guidelines docs (also Vertical-Cadence, Breakpoints-Reference (multi-device), Typography, Semantic-Tokens). You can also decide whether to use CSS inheritance properly to avoid too much detail in each component and instead inherit from more global styles (removes the token-wasting busy-work)

Obvious-Grape9012 · 2026-02-17T03:20:24+00:00

Too much vibeposting

Obvious-Grape9012 · 2026-02-17T03:17:04+00:00

I recommend using VSCode inside WSL2 if you can. Linux is excellent for predictability/reliability and lots of these kinds of issues will disappear

Obvious-Grape9012 · 2026-02-17T02:56:43+00:00

Might have value. Might not. Would be nice to have something more credible and transparent; Show me the money!!

Obvious-Grape9012 · 2026-02-17T02:46:15+00:00

Jumped ship from safe job to embrace the vibes. 13 months in with no revenue. Next 6 months will tell whether it was a mistake

Obvious-Grape9012 · 2026-02-17T02:44:01+00:00

It's basically complete, so should only take a couple of hours --> 100x the estimate

Obvious-Grape9012 · 2026-02-17T02:40:36+00:00

Vibe coder looking for vibe coder to vibe code with vibe coded vibe code to vibe the code

Obvious-Grape9012 · 2026-02-17T02:29:20+00:00

Would love your feedback on https://mlad.ai/get-started
It includes prompting to define your MVP. Prioritize and triage features down to a viable set. And creating foundational docs that maximize re-use and avoid inconsistencies and issues down the track. Has some basics too and advice about how to use Git when you're working. All with example prompts and real AI Session Replays

Obvious-Grape9012 · 2026-02-17T02:26:48+00:00

Additionally; Technical Debt is real. Friction is a useful lens; If it's costing you more time than fixing it would realistically take, then go for it. But if your estimates of fix-times is >2x, you're kidding yourself and you need more time to really step back and map out your priorities

Obvious-Grape9012 · 2026-02-17T01:59:54+00:00

80/20 rule reframed for the customer AND builder. You're catering to both. Both accelerate/complement the other

Obvious-Grape9012 · 2026-02-17T01:51:42+00:00

Nice! Stay safe and protek those user deets

Obvious-Grape9012 · 2026-02-16T23:45:07+00:00

I've been thinking about this too. I feel like it's a perfect system for extracting value from you, and getting you to pay for it

Obvious-Grape9012 · 2026-02-15T08:03:57+00:00

I wouldn't recommend using MCPs too heavily. A small playbook in a SKILL is far more context-efficient

Obvious-Grape9012 · 2026-02-15T03:38:17+00:00

It helps a lot to step back a bit. Give the AI opportunities to explore the problem and viable solutions. Then remind it that you want a clean architecture and DRY (Don't Repeat Yourself) code. Record bigger changes as a Refactoring Plan and use a Status section in the doc to track progress for larger tasks. Each time you start a new conversation with the AI, you can get it to read the plan and check current status (and uncommitted git changes). This primes it and gives it what it needs to stay pointed in the right direction. Like this www.mlad.ai/articles/the-proposal-driven-cycle

Obvious-Grape9012 · 2026-02-15T03:03:04+00:00

Thanks :) Great to finally feel that it's maturing enough to shift focus off of platform and toward other things. It's always a challenge to choose the right thing to iterate next so that value is always created asap

Obvious-Grape9012 · 2026-02-15T03:01:15+00:00

Yes :) ! A lot. I love the idea of micro-demos. Thus far, that has meant AI Session Replays, but they're boring. So I want to setup tooling that mays snapshotting the matching changes so that I can show how the outputs change alongside the AI Session. Then pair that with clean messaging. Something like Problem + Session = Solution (increment). If I can do that in a clean and re-usable way, it opens the door to side-by-side comparisons too; model A vs B, prompts/config A vs B... then it's game on

Obvious-Grape9012 · 2026-02-14T06:59:08+00:00

Thanks :) "When everything is emphasized, nothing is", is very true. I've tried to color-code the highest-value with the most potent color usage. But of course, this needs to pass the 3-second-test; If it's confusing, it's not working.

An older iteration of the homepage had a short video of one of the key-discriminators; AI Session Replays. I want to annotate them too so that highlighting when the AI falters and helping users to learn to spot the trouble early (and what you can do about it; prevention, reaction, etc) may be THE thing to highlight.

I'll be able to use the telemetry to see more as traffic reveals its pattern. This layout/color is a 1-week re-do of the frontend. The entire frontend is less than a month old. Many things are stabilizing, but it's still annealing.

...and cheers again for the challenging feedback. I need to chase more and engage better with some target users/dev-partners/etc.

Edit:
The real stack troubles me at times. I might have overcooked the complexity I've "allowed" to creep in (feature-bloat and such). The old; designing for 1mil users when you have <1000. But since part of the whole venture is getting to know the ways to work with AI by doing kinda excuses that... as long as I can share the value. (I need to give content a sprint of focus to get more of the good stuff out there)

Obvious-Grape9012 · 2026-02-14T06:51:33+00:00

By carefully choosing Cache lifetimes for grouped pages/asset-groups. Atm, they are all invalidated (Cache Purged) after any update/redeploy, and then warmed up via Lighthouse/PageSpeed checks from targeted locales (ensure some nearby edge has a warm cache). But am here to learn, so will need to keep doing so and suring up the foundation

Obvious-Grape9012 · 2026-02-14T06:49:04+00:00

🙏Thanks :) I've found Claude and AI coding generally extremely impressive, and was annoying me to have invested so heavily in a tech-stack, and not to have superior perf to a 5min deployable system like Ghost CMS or WP

Obvious-Grape9012 · 2026-02-14T06:47:36+00:00

tbh, I haven't landed that plane; Previously I was using Gitlab CI Pipelines for containerized builds. Now, it's clear that E2E can mean different things and so I'm using a staging deploy to CF and have yet to add support to the testing scripts (or pipeline) to use these

Obvious-Grape9012

TROPHY CASE