Alejandro Perez
@AlejandroPerez92
Staff Engineer at Dataships! In love with clean architecture ❤️
- Dublin, Ireland
- www.alexpz.com/
- github.com/AlejandroPerez92
- Joined November 2026
Commit activity
11 commits in the last 30 days
longest streak 2 days
245 / 400 XP155 XP to maintainer
Fri, Nov 6
Wed, Nov 4
replying to @lucydjo
Have you tried Codex? They have weekly usage limits, though I’m not sure if it’s any better.
Tue, Nov 3
replying to @klaraneumannova
I’m curious about the process behind your second skill. What does it highlight? Do you end up reviewing the code line by line?
Nope, it's no longer possible to go through these PRs line by line. I usually start by reading the tests, and then I move on to what the skill identifies as the core logic of that PR.
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…
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…
I'm completely with you on the concerns, I'm not for all AI development, I want some control my self.
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.
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.
replying to @klaraneumannova
That book is class! https://codely.com/en has really good resources as well, but most of them are in Spanish

CodelyCodely ﹤🍍﹥ Level up: Make code more maintainable, scalable and testable ﹤🍍﹥ CodelyKeep improving with videos and courses on SOLID, Domain-Driven Design (DDD), Hexagonal Architecture, Docker, CQRS, Microservices, Kubernetes, Testing, Front-end…
That's @AlejandroPerez92's first reply.