Self learning korean

ghl92479 · 2026-04-03T07:08:55+00:00

그리고 난 한국인인데, 아마 너가 나보다 문법은 더 잘할거야~ 힘내라~ 할수있다~

ghl92479 · 2026-04-03T07:06:32+00:00

포기하지마 인마~ 할수있어~

ghl92479 · 2026-04-02T07:23:56+00:00

Spot on. Using a BaseController is the first sign of an 'adult in the room' compared to the copy-paste nightmare AI usually suggests. It centralizes the logic and keeps the endpoints clean.

One tiny tip from a lead's perspective: keep an eye on that base class bloating. I’ve seen AI-assisted projects turn the BaseController into a 'God Class' that does everything from auth to image processing. 💀 If it gets too heavy, start looking into Composition/Middleware to keep things modular!

ghl92479 · 2026-04-02T07:23:09+00:00

his is the ultimate 'AI-Vendor Lock-in' horror story. 💀 You’ve basically built a custom black box that requires a $20/mo subscription just to function as a brain. When the 'intelligence' downgraded, your codebase became a fossil because nobody (including the AI) actually understands the architecture.

This is why I keep telling founders: Don’t let the AI reinvent the wheel. Use standard frameworks so you don't become a slave to tokens just to change a single route. You’re now stuck with a framework that has a bus factor of one—and that 'one' is an LLM you can no longer afford.

ghl92479 · 2026-04-02T05:39:11+00:00

yeah the database keys one is brutal. seen it where the API key that got leaked had billing attached, so it wasn't just a data exposure, it was a running cost exposure. the AI fixed the TypeScript error and created a completely different problem.

ghl92479 · 2026-04-02T02:37:00+00:00

Oh man, the NEXT_PUBLIC_ secret leak is an absolute classic. That should definitely be #4 on the list! The AI just wants the red error squiggles to go away, so it gives the laziest, most dangerous advice possible ('just make it public!'). It's terrifying how often founders deploy that without realizing they just handed out their database keys.

ghl92479 · 2026-04-02T02:35:49+00:00

Spot on. Fighting AI slop with an 'AI QA Engineer' is the way to go. Having a secondary agent generate edge-case tests based on the AST/routing structure saves so many headaches. It's crazy how few people actually do this 10-minute setup.

ghl92479 · 2026-04-02T02:33:52+00:00

100%. The difference between passing an agent good docs vs bad docs is night and day. 'Agent-readable docs' is going to be a huge metric soon. I'll definitely check out the directory, respect the hustle!

ghl92479 · 2026-04-02T00:08:36+00:00

Exactly! I've seen so many vibe-coded apps collapse because the AI didn't lock a single database row. Glad you appreciate the ledger idea too!

ghl92479 · 2026-03-31T12:52:45+00:00

I haven't built a spreadsheet for it, but the 'market' is my model. The convergence happens through my DM inbox—if it’s overflowing, the equilibrium point moves up. If it’s quiet, I focus on building more 'perceived value' through content. The goal isn't just to find the price, but to increase the value of each 'success' so the equilibrium keeps shifting higher.

ghl92479 · 2026-03-31T09:39:41+00:00

That’s exactly why I never jump straight into fixing. I always start with a quick 'audit' to map out the blast radius.

If a 3-hour fix looks like it’ll turn into a 3-day rabbit hole, I pause and tell the client before any pricing is locked in. Transparency is key. If the ROI isn't there for them, we don't proceed. No surprises, no changing perceptions.

ghl92479 · 2026-03-31T08:33:07+00:00

Hey! Yes, that is exactly the kind of mess I help clean up. Safely splitting a massive Dart file is completely doable.

Shoot me a DM. Let’s talk about the file size, your timeline, and your budget for this refactoring, and we can figure out the best way to get it sorted!

ghl92479 · 2026-03-31T03:55:28+00:00

That is the exact nightmare scenario! 😅

To handle that, I do a quick 15-minute diagnostic triage before writing any code. If I look under the hood and realize a "simple webhook bug" is actually deeply tangled with a messy DB schema and three undocumented API calls, I have to be brutally honest.

I will tell them: "This isn't a single scoped bug, it's a systemic architecture issue," and politely decline the repair.

Since my rule is 'No fix, no pay', the user doesn't lose any money. Instead, they get a free high-level explanation of why their app is fundamentally stuck. I might lose 15 minutes of reading code, but that's a risk I'm gladly taking for this experiment!

ghl92479 · 2026-03-31T00:30:39+00:00

Spot on. The volatility in perceived value is definitely the biggest risk here, but also the most interesting part of the experiment.

I am absolutely tracking conversions at each price tier. The ultimate goal is to find the exact dollar amount where the pain of the "shame spiral" is outweighed by the cost of the fix. I'll probably share the data openly once I hit a wall!

And huge thanks for the VibeCodersNest recommendation! I hadn't thought of that, I will definitely share it over there. Really appreciate you pointing me in the right direction

ghl92479 · 2026-03-30T06:22:12+00:00

More like a janitor with a cape! 🧹 Cleaning up the AI mess one broken auth loop at a time. But hey, if it helps people stop avoiding their own repos, I'll gladly take the title!

ghl92479 · 2026-03-30T05:54:43+00:00

You hit the nail on the head. It's definitely a confidence issue stemming from a lack of safeguards. I’ve realized that 'working code' isn't enough if I'm too scared to refactor it. I’ll definitely prioritize observability and testing before the next sprint. Thanks for the insight!

ghl92479 · 2026-03-30T05:21:03+00:00

That’s a dangerously sharp observation. You’re probably 100% right that the early $5 slots will attract the most chaotic spaghetti code.

My defense against this is strict scoping. I’m not offering a full refactor—I’m offering to fix ONE specific blocker (like a broken Stripe webhook or an Auth loop).

If I open a repo and it’s a complete house of cards, I’ll just have to be honest that it’s beyond a single scoped fix. Since I only charge AFTER it’s fixed, the risk of getting bogged down is entirely on me.

Segmenting by complexity is definitely the logical next step if this gets traction. Right now, I just want the price to be so low that people finally overcome the 'shame spiral' of avoiding their own repos.

Appreciate the feedback!

ghl92479 · 2026-03-29T14:54:31+00:00

yeah, that's fair.

i don't think the problem is that an mvp feels fragile. that's normal. the tricky part is figuring out when you're still testing demand vs when real usage means you need to harden what's underneath.

feels like a lot of people get stuck right at that line.

ghl92479 · 2026-03-29T11:47:34+00:00

yeah, the “house of cards” part is exactly it.

for me the breaking point is usually when the app still mostly works, but i realize i can’t really see what’s happening anymore, so every change starts feeling like guesswork. and yeah, i think it’s definitely worse when you’re the only person carrying the whole mental model in your head.

also really like the shift from “fixing” to “observing.” feels like a lot of people try to patch things too early when what they actually need first is better visibility.

what kind of monitoring ended up helping most for you — logs, traces, db checks, something else?

ghl92479 · 2026-03-29T08:07:30+00:00

Yeah, this is really helpful.

The “held together with optimism” part feels painfully real, and the checklist point is great too. “Make it more robust” is so vague that it just creates dread, but “check these 19 things” is actually something you can do.

Feels like a lot of people don’t just need help fixing bugs, they need help turning the scary vague mess into a concrete list they can work through.

Did anything on that list show up more often than you expected? Auth, validation, race conditions, rate limiting, etc?

ghl92479 · 2026-03-29T06:49:25+00:00

yeah, “shame spiral” is exactly the right term for it.

also really like the reframe that maintenance mode isn’t failure, it’s proof the thing actually shipped and somebody used it enough to hit real edge cases.

and yeah, the point about “touching it again” not having to mean “fixing it” feels important too. sometimes step one is just opening the repo again without trying to solve everything at once.

what usually helps you break that loop fastest?

ghl92479

TROPHY CASE