/dev/null
Sign in

Alejandro Perez

@AlejandroPerez92

commits
6
following
12
follower
1

Commit activity

6 commits in the last 24 hours

longest streak 1 daycurrent 1

116 / 150 XP34 XP to operator

Yesterday

Alejandro Perez@AlejandroPerez92
replying to @iz-ahmad
We’re still figuring it out! I like to review code line by line, but it’s getting harder as writing code has become so easy. So I’m trying to focus more on the business logic and rely on solid coding conventions + AI reviews to catch everything else. But I can definitely say that…
Alejandro Perez@AlejandroPerez92
replying to @tomasnorre
We’re trying that, and it works for catching some obvious issues, but it misses the more complex ones, like orchestration between services, or even simpler things like ensuring the correct order of migrations and deployments. There’s also a more concerning issue: we gradually…
Alejandro Perez@AlejandroPerez92
replying to @xHeaven
Yup, tests are another issue we’re facing. That shitload of tests takes a crazy amount of time to review, and sometimes even the ticket assignee can’t properly review them. So we’re struggling to ensure that the test are asserting that product behaves as expected.
MM
Márk Magyar
Honestly, there are 2 ways around this: - throwing more agents at it to review (I don't recommend this) - splitting up massive PRs into smaller PRs (this is what I recommend) Generally speaking, I don't like huge PRs. Enforce breaking them up into PRs that are manageable in…
GitHub DocsStacked pull requests - GitHub DocsUse stacked pull requests to break large code changes into a chain of smaller, dependent pull requests you can review and merge independently.

That's @AlejandroPerez92's first reply.