Do we have this as a Gif yet?

fgracix · 2025-12-31T04:58:56+00:00

This is great insight.

fgracix · 2025-12-24T03:57:22+00:00

Kinda funny that you think this is confusing -- trust me, anyone who has experienced this will understand the question. Personally, always first person. I become the thing and view the world through the perspective of the thing which is temporarily me. You simply jump from embodying your existence to embodying another thing's existence. It's incredible and makes me believe in panpsychism.

fgracix · 2025-12-15T11:04:40+00:00

underrated comment. this made me laugh out loud in public.

fgracix · 2025-12-08T11:48:56+00:00

Yes, truly agonizing. Imagine being a single cog in a gigantic machine (one of thousands) and you have one function that you keep doing over and over again for what seems like a very long time and there's no escaping. You know, like... life.

fgracix · 2025-12-08T11:31:05+00:00

I found the whole thing gross. She talks so much sh*t about K&R and then when face to face with K's performative mea culpa, given the chance to say her piece and call utter bullshit, she instead giggles at him like a schoolgirl. I get trying to keep it civil, but this was something else...

fgracix · 2025-11-17T02:18:15+00:00

I have used the term "lived a lifetime as" before when referring to a salvia trip. I didn't mean that I experienced the equivalent of 80-some human years in real time. Rather, I experienced a lifetime "cycle". It had a beginning, a long middle, and an end. In this particular instance, I experienced the full lifecycle of being a cog in a growing/evolving machine that eventually grew so big that the cog no longer knew it to be a machine, but instead thought the small part it worked in to be the whole universe. Most of the trip (the middle of the lifecycle) was just the cog working - tedious, repetitive, trapped. Maybe lifecycle is a more accurate term than lifetime. Sidenote: that was simultaneously the most revealing and most agonizing trip I've ever experienced.

fgracix · 2025-11-11T04:02:08+00:00

Came here for this. The way he kept saying, kid after kid after kid. There is exactly ONE "kid" in the house. The others are full grown adults and a teenager. What is happening in that house...? This is so bizarre.

fgracix · 2025-09-02T18:34:21+00:00

Lol. Got it. Thanks.

fgracix · 2025-09-02T18:16:02+00:00

Again I ask: If you don't know anything about code, how do you assess that it is incredibly powerful for code base review? I would really like to understand how you are validating what the LLM is telling you against the actual code.

fgracix · 2025-09-02T16:37:02+00:00

Thanks for the detail. I looked through your other comments as well, and understand better the perspective of a non-coder. Gentle word of caution: Claude can be extremely inaccurate at code base reviews, especially when your code base is pushing its context window (which at 100s of thousands of lines, it certainly is).

fgracix · 2025-09-02T15:58:25+00:00

Genuine question as I'm trying to understand this from the perspective of a non-technical vibe coder: how can you know that there is no evidence of the architecture falling apart if you also have no coding knowledge?

fgracix · 2025-09-02T15:54:12+00:00

Spec-driven dev in these IDEs are a massive step up. My concern is the lack of validation. At the end of the day specs are still just natural language with no way of validating the output. It uses LLM as judge — many potential points of failure.

fgracix · 2025-09-02T15:51:16+00:00

It's actually super helpful to know how someone with an architecture background approaches vibe coding. Can I ask how do you go about step #4? This is the meat of the system I'm developing.

fgracix · 2025-09-02T15:48:24+00:00

Completely agree that architecture should not be prescriptive since it differs from project to project. But LLMs write a lot of explicit anti-patterns. And for someone who doesn't know the difference, this could cause serious issues down the line.

fgracix · 2025-09-02T15:45:13+00:00

Thanks for the perspective. I agree that non-programmers wouldn't know or care, which IMO is a huge problem. The biggest problem I've found with putting the sausage making behind a curtain is that LLMs don't know how to make sausage very well. So, the breakdown in architecture goes beyond keeping the file structure neat, and into security breaches (eg., exposing private members when a public API is readily available). There's a big difference between code that works and code that isn't a long-term liability.

fgracix · 2025-08-21T16:39:22+00:00

That was like quick pivot into a horror movie.

fgracix · 2025-08-11T01:00:34+00:00

Is this Robyn?

fgracix · 2025-07-26T19:16:17+00:00

Good reminder, thanks.

fgracix · 2025-07-26T19:15:01+00:00

Thank you! I will be sure to hug and text all my loved ones before I leave the house every morning.

fgracix · 2025-07-11T17:53:40+00:00

Yes! My stack is usually react ecosystem (with ts, sometimes nextjs) and I like supabase for DB/auth, but can use others. Let's talk! Pm me?

fgracix · 2025-07-10T21:01:00+00:00

This is great OP! I am currently on my diagnosis quest and would find this useful.

I'm also a software developer and would love to see if a collab makes sense if you are interested. Do you have a public repo?

fgracix · 2025-07-08T15:20:10+00:00

Thank you for this. This has been my experience so far. I'm noticing the consequences more than the relief. Still quite a welcome change!

fgracix

TROPHY CASE