I've always loved creating new things instead of working on the same project for years. I have 2 enterprise projects under my belt as a developer, but the rest of the projects I joined were mostly as a consultant to kickstart the project for others to continue working on it.
"I always loved creating new things instead of working on the same project years after years."
This passion drives me to help teams build solid foundations that others can continue working on. I help teams get from initial ideas to production-ready foundations.
I create tailored project structures, help with technical documentation, and set up CI/CD pipelines so teams are prepared for production deployment. While I'm mainly focused on front-end architecture, I also help with full-stack application architecture for medium projects using Node.js and serverless technologies.
I've collaborated with clients from Romania, USA, UK, Israel, France, Spain, Germany, and more. When architecting backend systems, I consult with dedicated backend developers from my network to ensure the best technical decisions.
What I do
Requirements gathering and product definition
Helping teams define clear product requirements and scope
Technical documentation and scope definition
Creating comprehensive technical documentation for teams
Front-end project structure and architecture
Building scalable front-end architectures
Full-stack architecture (Node.js + serverless)
Architecting full-stack solutions for medium projects
CI/CD pipeline configuration
Setting up deployment pipelines for production readiness
Backend developer consultation
Collaborating with backend specialists for complex decisions
My project structures are simple and follow a feature-driven pattern. I have a core folder that contains the main and shared functionalities, then a feature folder with specific features.
"It's best to be consistent with a bad pattern because it's easier to change it all at once, instead of changing your pattern from one feature to another."
This philosophy guides all my project structure decisions.
I work with a boilerplate but I keep it minimal to not be tempted to use things in a project just because I have them already setup. My project structures also take in mind the people that will continue the work.
I've worked with a lot of juniors and mid level developers and they struggled with more complicated project structures, so I always use a simple approach but extremely consistent.