LinkedIn: I want to keep this private so my current employer doesn't know. Just contact me and I'll send you. Or get it from the cv. Thanks for understanding.
Email: rodolfopolicarpo117[at]gmail.com
About: Senior Backend Engineer | 9 years experience | Node.js/TypeScript
Currently building a multi-channel dispatch pipeline (scheduling, queuing, rate-limiting, retries, idempotent execution) on GCP Cloud Tasks + Cloud Run at scale.
LinkedIn: I want to keep this private so my current employer doesn't know. Just contact me and I'll send you. Or get it from the cv. Thanks for understanding.
Email: rodolfopolicarpo117[at]gmail.com
About: Senior Backend Engineer | 9 years experience | Node.js/TypeScript
Currently building a multi-channel dispatch pipeline (scheduling, queuing, rate-limiting, retries, idempotent execution) on GCP Cloud Tasks + Cloud Run at scale.
I relate so much with this article
I've had a previous experience with a backend monolith repo, and these days I have to deal with a backend that has 20+ repos. It is hell. Duplicated code, duplicated logic, duplicated tests, duplicated settings, an hell to introduce newbies to the architecture, async calls to external basic APIs that could've been just simple method calls.
I think that the one major disadvantage of having a big monorepo, is that with those multiple entry points, you might end up with a bunch of unused dependencies. But even that is manageable I think: you can have different package dependencies definitions whilst using the same codebase.
I've always worked with small teams (max up to 5 or 6 developers) and that's another point in favor of monorepos. I understand that big companies might want to have different teams working on different repos, for organisation reasons.
I have no children, but I find this an interesting topic, because I have small cousins and friends with children.
I find it quite disturbing to see the kids online, with their eyes on screen all the time they are not sleeping. It is concerning and it doesn't look healthy, both for their bodies/minds but also for their future. Don't tell me children learn something useful in TikTok, albeit some creative ideas, but in long term, most of it is crap.
I honestly look at these children, and can't quite fathom what their future will be. Hopefully they will pop out/unplug off their drug, but... yeah.
Willing to relocate: No
Technologies: Node.js, Javascript, TypeScript, Express.js, MongoDB, PostgreSQL, GCP (Cloud Run, Cloud Tasks, VM, Network, Cloud Functions, Storage), Docker/Docker swarm, AWS (S3, ECS, EC2, ECR), RabbitMQ/AMQP, GraphQL, Redis, GitHub Actions, Terraform, Linux, event-driven architecture, distributed systems
Résumé/CV: https://files.pampilosmutantes.pp.ua:8443/cv_nc.pdf
LinkedIn: I want to keep this private so my current employer doesn't know. Just contact me and I'll send you. Or get it from the cv. Thanks for understanding.
Email: rodolfopolicarpo117[at]gmail.com
About: Senior Backend Engineer | 9 years experience | Node.js/TypeScript
Currently building a multi-channel dispatch pipeline (scheduling, queuing, rate-limiting, retries, idempotent execution) on GCP Cloud Tasks + Cloud Run at scale.
Eager to help someone else and learn new stuff.