Position: Front-end developer (React)
Category: JavaScript
English level: upper
Years of experience: 4

- Pushing modern, pragmatic tech & migration paths with walls of text and justifications to get more productivity for devs
- Adjusting development processes to reduce mental overhead, allowing spending it doing more important things, like thinking about actual user interface :)
Most notable projects:
- Large ads management platform for employees, where rendering huge amounts of tabular data, charts and maintaining good performance through optimisations was the usual.
- Inner platform for managing employees and their workloads in the sphere of design outsourcing, where along with tables, forms and charts we also created composable and reusable custom components focusing on UX and keyboard accesibility.

On the developer's path I've been:
- Constantly learning & improving, applying critical thinking to specific situations and processes as a whole
- Being proactive & vocal about problems, thinking of edge cases and mitigation strategies, keeping big picture in mind
- Seeking ways to improve development processes & productivity considering team composition peculiarities
- Raising the bar of product quality, spotting bugs that like to hide, finding ways of improving usability
- Reducing barrier of entry into the codebase
- Praising the concept of trade-offs and case-based decision-making
- Mentoring & helping teammates, brainstorming technical solutions, being a morale booster
- Refining development tools
- Working with foreigners in a distributed team
- Writing API specs and data structures
- Documenting migration paths for deprecated tech
- Collaborating with UX/UI designers to ensure best user experience, diving deep into usage scenarios
- Applying my sense of web design
- Achieving a degree in React optimisations and black belt in googling :)
I am interested in working with a team of people that mostly improve in practice, applying critical thinking and evaluating situations. People, who understand exactly why they do certain things, and not the others.

My choice is TypeScript & React, because clever guys in React's ecosystem don't stop exploring and coming with easier, more productive ways of achieving goals.

I belive that developer happiness directly correlates to the delivery rate, and I like achieving that by carefully introducing new tech that solves real problems, without requiring you to relearn everything or remake everything for scratch.

I prefer working on new projects, maintaining tooling and keeping them up to date.

Legacy flat-structured projects with heavy interconnections are no-go. :)

Modular legacy projects could be worked on iteratively, introducing migration paths, but only if reducing tech debt and making a modern, welcoming codebase is in line with business needs.