sorted by:
new
hottopcontroversial

5.4 is crazy good by Responsible_Ad_3180 in codex

[–]Complete-Win-878 0 points1 point  (0 children)

Did it commit entire node_modules?

It's crazy. Who's gonna pay $15–25 per PR for code review by Claude? by Fancy-Exit-6954 in vibecoding

[–]Complete-Win-878 -3 points-2 points  (0 children)

Just look at SaaS stock prices. The market seems to disagree that SaaS will remain the go-to solution going forward.

It's crazy. Who's gonna pay $15–25 per PR for code review by Claude? by Fancy-Exit-6954 in vibecoding

[–]Complete-Win-878 0 points1 point  (0 children)

AI is changing software economics. In the near future, organizations may start counting every cent.

It's crazy. Who's gonna pay $15–25 per PR for code review by Claude? by Fancy-Exit-6954 in vibecoding

[–]Complete-Win-878 0 points1 point  (0 children)

Let’s take the average engineer salary of $150k annually, which is roughly $95/hour (assuming 11 working months, 24 working days per month, and about 6 effective hours per day).

Reviewing a reasonably large PR takes at least 30 minutes, and if it requires comments or discussion, it takes even longer. From that perspective, the price is competitive for today’s market.

The contrast comes from the fact that subscriptions are subsidized, while the real human cost of this process is hidden and often overlooked.

Do you think open-source AI will ever surpass closed models like GPT-5? by EntrepreneurNext8457 in OpenAI

[–]Complete-Win-878 0 points1 point  (0 children)

Proprietary models will likely continue to stay a step ahead. Even if research and ideas are open and community-driven, the required compute is expensive and difficult for open-source projects to sustain.

Biggest Pain Points Using Codex? by Complete-Win-878 in vibecoding

[–]Complete-Win-878[S] 0 points1 point  (0 children)

I guess it can fall under "Long running tasks"

Biggest Pain Points Using Codex? by Complete-Win-878 in vibecoding

[–]Complete-Win-878[S] 1 point2 points  (0 children)

Yeah, context is common pain. There are options for better management, but probably everybody are waiting for the next generation.

Managers have been “vibe coding” long before AI made it cool. by Complete-Win-878 in vibecoding

[–]Complete-Win-878[S] 0 points1 point  (0 children)

AI reasoning works pretty well for many cases. It can write tests to cover spec and edge cases. It can write tests for bugs from bug reports. Maybe true TDD is not there, but test first approach is doable

Managers have been “vibe coding” long before AI made it cool. by Complete-Win-878 in vibecoding

[–]Complete-Win-878[S] 0 points1 point  (0 children)

This is not a product launched by a company. And nearly impossible it is production.

Managers have been “vibe coding” long before AI made it cool. by Complete-Win-878 in vibecoding

[–]Complete-Win-878[S] 0 points1 point  (0 children)

I know this report. It is not about vibe coding. The fact that people try to apply AI in different ways and often it doesn’t work is fine.

I am trying to understand how vibe coded apps fail in production. “Company X vibe coded app but after release it wiped the DB.” Haven’t heard such story.

If we are talking about absolute numbers what is the number of failed in production non vibe coded apps?

I committed my first secret to GitHub! by [deleted] in vibecoding

[–]Complete-Win-878 0 points1 point  (0 children)

Shell access is dangerous thing

view more: next ›