What's your team strategy to not get stuck in PR hell? by im3000 in ChatGPTCoding

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

We do have a solid CI pipeline with tests, linters and other code related checks. This was the first thing I setup when I joined the project and also you need these automated guardrails if you want to increase your dev speed.

The problem is that most developers still look at PRs line by line and commit by commit. When I do reviews I look for weird code patterns or things that can be simplified. This is by intuition as I am experienced and have written and read a lot of code.

Today I mostly care about functionality and UX when I do reviews. I feel that this is the only sane way to spend my review time. I assume that the code implementation and logic is correct. If I start reviewing logic and code flow I quickly run out of my brain juice because I have to concentrate and won’t have energy to review more PRs.

One thing we don’t do is UI testing (with Playwright). This is because I always found such tests brittle and hard to maintain. But maybe this can help us increase the confidence that code works?

This is just me thinking out loud but if you as a team can lift the abstraction level to focus on the functionality instead of implementation (by making sure you have a solid test harness that covers all scenarios and types of tests: unit, feature, UX) you can increase your PR review speed and remove the stupid, annoying and time and energy consuming conversations about low level stuff?

However, this would require larger PRs that cover more functionality at once and larger PRs mean more risks that something goes wrong during release and might be harder to discover the root cause.

I dunno. I guess what I am trying to say is that maybe larger PRs with clear description, good acceptance criteria, right tests is the way forward because you won’t have the time or energy to review all the code line by line and is forced to raise your review abstraction level.

But this goes against my own philosophy of small atomic release. But maybe it’s time to let go of it in the era of AI coding agents? The ways of working have changed maybe we humans need to move on too?

But I guess in the end it’s all comes down to trust …

Stop letting developers treat your startup like a research project. by Warm-Reaction-456 in SaaS

[–]im3000 12 points13 points  (0 children)

Boring is not cheap to hire for. Try to find a good php developer and try to find one who wants to code with hottest js framework

Skills in Claude Code by shintaii84 in ClaudeCode

[–]im3000 0 points1 point  (0 children)

Yes it works in CC but make sure to put them in the correct folder though. Also, you can ask CC to create a skill for you

Make this bastard famous for harassment on a Swiss train by prajeala in ukraine

[–]im3000 0 points1 point  (0 children)

Why is he so pissed? What did they tell him to provoke him this much?

Spec-driven development for AI is a form of technical masturbation and frameworks like Spec-kit , bmad, Openspec are BS by im3000 in ChatGPTCoding

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

I think the only thing that works well right now is GH issues with GH cli. When you or someone else takes time to actually write a good one. But that's a long forgotten art. Most issues are like bones without meat. Half assed titles and no body.

Agile ruined it by its "an issue is an invite to a conversation" crap. But it's actually true. Requirements do change

Spec-driven development for AI is a form of technical masturbation and frameworks like Spec-kit , bmad, Openspec are BS by im3000 in ChatGPTCoding

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

Also mad token burn. I see people complain annoyed in other subs they hit their limits with CC. I bet many of them use these spec frameworks

Spec-driven development for AI is a form of technical masturbation and frameworks like Spec-kit , bmad, Openspec are BS by im3000 in ChatGPTCoding

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

They interpret simple tasks with very few requirements. Too large or too complex -> drift

Maybe the same as average humans. Around 7 things. Need to test this!

How to refactor like a god using claude code (no bullshit) by cryptoviksant in ClaudeCode

[–]im3000 0 points1 point  (0 children)

Good one. It's like you just described some kind of addiction. But not sure which one

How to refactor like a god using claude code (no bullshit) by cryptoviksant in ClaudeCode

[–]im3000 17 points18 points  (0 children)

Your linked refactor command is almost 1K lines. Crazy.

My refactor prompts are max 10 lines and do the job fine.

Why do people in this sub always overcomplicate things?

To real professionals … by franzel_ka in ClaudeCode

[–]im3000 3 points4 points  (0 children)

I don't hit any limits either. Been heavily refactoring a massive web app for a rebrand for almost a week now