I am an experienced Full Stack Developer, during the decade of my career, I saw the technology change at incredible speed, making me learn a new stack every year.
I started working during the time when iframe and tables were "cool", and PHP was "the language of the future". I adopted Node.js in the moment that I saw that was superior to PHP and I never regretted that, from that day every project I develop, was with Node.js.
During that time, not only my choice of database transitioned from MySQL (major choice in PHP) to MongoDB and finally to Postgres, redis and Mongo (choosing the right one for the right project), but I also learned that a successful website doesn't use simple queries, but also need that the database needs to execute some code on its side (triggers, functions, ...).
I also made big jumps on the front end. Starting with vanillajs (badly), move to jQuery, then Kendo, then Dojo (a light version of jQuery), moving back to vanillajs because those frameworks had terrible performance, and finally discovering the joy of the uber-complicated first version of Angular. At the end, I discover React, and that has become a big part of my stack.
I've been always passionate about my job, and I really enjoy what I do and learn new things. Many of the things that I learned during these years I didn't mention here, just because aren't relevant, or because the description will be too long.
(At some point during all of that I also discover TDD and Docker)
At WIX, my job responsibility is to build new functionalities for the form platform. The stack I’m currently using at WIX is React and...
At WIX, my job responsibility is to build new functionalities for the form platform. The stack I’m currently using at WIX is React and Typescript, living on top of a proprietary ecosystem.
At Revel Systems, my job responsibility was initially to build new functionalities and fixing bugs on our codebase built with React, N...
At Revel Systems, my job responsibility was initially to build new functionalities and fixing bugs on our codebase built with React, Node.js and Python. Successively as the company grew I led the inside project to build a micro-fronted architecture that makes it possible for multiple teams to work independently on the now bigger codebase and release their code without the waiting for other teams to release their work too. My work made it possible for other teams to reduce their cognitive load by reducing the codebase they need to work to a smaller one,improved productivity and reduced conflicts between teams. Now my job revolves around maintaining and improving this architecture, including understanding what other teams need and help them solve architectural dilemmas.
During my day to day job at Moneyfarm, I work on a variety of tasks, mostly based on the team I'm on.
My job responsibility i...
During my day to day job at Moneyfarm, I work on a variety of tasks, mostly based on the team I'm on.
My job responsibility is to create new functionalities, improve the existing ones and refactor the code from an old legacy codebase to a new living codebase.
Currently, at Moneyfarm, I have improved the frontend architecture by moving from three different frontend apps, into one single app composed of three micro frontends. This improvement has reduced the page transition time on an average of 90% and in best cases of 99.99%. It also opened the road to have a proper progressive web app.