Daniel Andrade
I've been a developer for quite some time now and have sailed the tides of technology far and wide. My language language of choice is TypeScript these days, but I can roll with most of the common ones.
I'm also particularly good at the design level, when it comes down to actually understanding the business requirements and translating that into a solution. I've worked across quite a few domains and know how to get acquainted with their intricacies, what questions to ask and where to prod.
So, if you're in need of someone who's probably already trodden this road before, be it that crazy code you inherited from a legacy codebase and for some reason won't work anymores or that crazy thing the designers came up with and now it's time to make it into a reality, hit me up!
REVIEWS FROM CLIENTS
I work with the front-end team to create a sustainable evolution for the entire application ecossystem, making sure that the requireme...
I work with the front-end team to create a sustainable evolution for the entire application ecossystem, making sure that the requirements by the Product and Design teams can be met in an incremental fashion while continuously delivering value.
Curently I'm overseeing a migration from the legacy frontend to a modern approach by using microfrontends in Vue.
I've also spearheaded the develoment of the company's mobile app using React Native, laying the foundation for a solid architecture where the frontend team could work and taking on the most technically demanding features.
I mostly focused on user experience editing rich content for their CMS-like features, giving the clients more options when it came to ...
I mostly focused on user experience editing rich content for their CMS-like features, giving the clients more options when it came to authoring content.
- Continous evolution of our rich-content editing components to be used throughout the CMS system, from UX/UI exploration up to implementation.
- Developing reusable components for rendering said content, making sure the content got rendered consistently to spec in a broad range of frontends.
- Providing documentation of said features for other team members to implent them elsewhere.
I worked with the core team to develop the main functionalities of their web application, including the architecture around the front-...
I worked with the core team to develop the main functionalities of their web application, including the architecture around the front-end deploy cycle, but also covering any backend work needed.
- Designing the frontend architecture for the main product, a highly-horizontal SPA that would be developed by several teams concomitantly and, thus, had several unique needs.
- Developing new features end-to-end, collaborating with the team from exploration and user research, specification and design steps to make sure when implementation began everything had been aligned and it could run smoothly.
- Implementing and evolving our design system to ensure we had a flexible and consistent range of components to use as building blocks throughout the application, which involved not only the implementation but also working alongside the design team to make sure we were aligned and figma designs could be easily interpreted back into code, whether through predetermined design tokens or whole components.
- Building documentation for components using Storybook and some custom code to pull components from a few different packages.
- Improving frontend performance for SEO, I tried to sound the alarm as soon as possible concerning how Google's SEO ranking was going to start taking frontend performance into account and led efforts to make sure we were within a certain range for all Core Web Vitals metrics when it came around.
- Sharing knowledge with the team by organizing bi-weekly study sessions where we'd implement together a given feature while discussing thoroughly the decision process on how to go about it so that not only technical knowledge got shared, but also the complex heuristics used to decide when it came to tradeoffs