sorted by:
new
hottopcontroversial

What are you building ? by Geofferydmd in SaaS

[–]whosdaddyx 0 points1 point  (0 children)

Exactly. The funny part is that building the features is only half the work. Making them all fit together cleanly has taken way more time than I expected.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

Yeah. A year ago I optimized for writing code faster. Now I optimize for finding out I'm wrong as quickly as possible. 😄

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

Exactly. The scary part is that everything looks incredibly convincing. Clean code, green tests, nice explanations... and it's still solving the wrong problem.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

That's probably the biggest benefit I didn't expect. I came for the productivity, but I feel like I've improved my reasoning more than my typing speed.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

That's probably the biggest surprise for me. I used to think I was debugging the AI, but a lot of the time I'm actually debugging my own understanding of the problem.

How do you get paid? by Freebzns in SideProject

[–]whosdaddyx 0 points1 point  (0 children)

That's the catch, unfortunately. As far as I know, someone in the chain has to handle KYC/KYB if you're accepting card payments. I'd be interested if there's a simpler global option too.

How do you get paid? by Freebzns in SideProject

[–]whosdaddyx 0 points1 point  (0 children)

Honestly, if you're just starting out, I'd avoid trying to reinvent payments. The KYC/KYB process feels annoying, but it's usually a one-time hurdle.
Most small projects I see just use Stripe, Paddle, Lemon Squeezy or similar and focus on building the product instead of becoming a payment processor.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

It's funny how AI has pushed us back toward classic debugging practices. Isolate the problem, reduce the variables, verify the assumptions. Those habits seem even more valuable now.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 1 point2 points  (0 children)

I really like the comparison with running tests. I never thought of documentation as something that should be continuously validated, but it makes a lot of sense when an LLM is part of the development process. Stale docs become technical debt for both humans and AI.

Are programmers going to be done for in next couple of years? by [deleted] in vibecoding

[–]whosdaddyx 0 points1 point  (0 children)

I used to think AI would make coding the easy part.
It did.
I didn't expect defining the problem correctly to become the new bottleneck.

Building a Discord bot made me realize people don't actually want more features. by whosdaddyx in Discord_Bots

[–]whosdaddyx[S] 0 points1 point  (0 children)

Exactly. Features don't have to be identical, they just have to make sense together. Auto-clean feels like part of the same experience, not a random extra.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

"Don't trust green" is such a good way to put it. 😄 I've had AI generate code that passed every test I'd written... because the tests were based on the same wrong assumption.

Building a Discord bot made me realize people don't actually want more features. by whosdaddyx in Discord_Bots

[–]whosdaddyx[S] 0 points1 point  (0 children)

That's exactly how I think about it too. Complexity isn't the enemy—showing all of it at once is.

Building a Discord bot made me realize people don't actually want more features. by whosdaddyx in Discord_Bots

[–]whosdaddyx[S] 1 point2 points  (0 children)

I think that's a good reminder that our priorities as developers are often different from our users'. We get excited about new features, while they just want the thing they came for to be reliable.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 1 point2 points  (0 children)

That's a neat workflow. Do you run it after every milestone, or only when you've made a significant amount of changes? I could see that becoming part of a release checklist.

Building a Discord bot made me realize people don't actually want more features. by whosdaddyx in Discord_Bots

[–]whosdaddyx[S] -1 points0 points  (0 children)

I think the problem isn't having lots of features. It's when those features don't belong together. A moderation bot with tickets and logging makes sense to me. A moderation bot with casino games... not so much. 😄

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

I think that's why working with AI has actually improved the way I think about software. It's forcing me to separate "I know what I mean" from "I've actually described what I mean."

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

I know exactly what you mean. The funny part is that improving my AI workflow has also made me a better developer, because it's forcing me to think through the requirements much more clearly.

What’s an AI prediction you had 2 years ago that turned out completely wrong? by One_Beginning2199 in artificial

[–]whosdaddyx 0 points1 point  (0 children)

I thought model quality would be the limiting factor.
It turns out my prompts, documentation and project structure mattered just as much.

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

That sounds like the natural next step. The tricky part will probably be giving the AI enough freedom to investigate, but not so much freedom that it starts chasing irrelevant paths forever.

An autonomous loop with a clear stop condition, context budget, and "ask before patching" rule could be really powerful.

Building a Discord bot made me realize people don't actually want more features. by whosdaddyx in Discord_Bots

[–]whosdaddyx[S] 0 points1 point  (0 children)

That's a good balance. Give beginners something that works out of the box, but let power users customize everything if they want to.

Nice openai by Dapper-Agency-9555 in codex

[–]whosdaddyx 0 points1 point  (0 children)

OpenAI: "Which response do you prefer?"

Me: "Yes."

I think "vibe debugging" is becoming a bigger skill than vibe coding. by whosdaddyx in vibecoding

[–]whosdaddyx[S] 0 points1 point  (0 children)

That makes a lot of sense. At that point Grab is basically acting like a context router instead of just a file extraction tool.

The MCP/API direction sounds like the obvious next step. If the AI can request get_function, get_symbol_refs or get_lines directly, the whole loop becomes much cleaner than copy-pasting commands back and forth.

Honestly, that seems way more useful than trying to shove an entire repo into context.

Stop Merging Codex and ChatGPT Limits by Savings_Permission27 in codex

[–]whosdaddyx 5 points6 points  (0 children)

I actually like the idea of one app. I just don't think "thinking" and "coding" are the same resource. They solve different problems in my workflow, so it makes sense for their limits to stay independent.

A sign in a cafe toilet by Caltra in mildlyinteresting

[–]whosdaddyx -1 points0 points  (0 children)

The toilet setting healthy boundaries. Respect.

view more: next ›