WerBn
Résumé/CV: https://files.pampilosmutantes.pp.ua/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.
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/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.
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/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.
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.
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.
Remote: Required
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://vault.pampilosmutantes.pp.ua:8443/#/send/IDLRmgNfTBa...
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.
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.