friedbizkvit.npmx.social

Spearheaded the design and development of a cutting-edge Software Defined Vehicle platform accelerating architecture design, requirements management, and testing for automotive software systems. Recognized by industry leaders for enabling end-to-end traceability across vehicle hardware topologies, multi-level requirements (vehicle/system/feature), and AI-powered test automation. Key contributions: - Architected a scalable frontend foundation using a hybrid of Feature-Sliced Design (component organization) and Clean Architecture (domain/data/presentation/ui separation), enabling seamless adaptation to evolving product complexity. - Drove full-cycle development from concept to launch, including a monorepo setup with Nx and custom code generators that reduced component scaffolding time. - Integrated AI copilot capabilities for Robot Framework test generation and requirements validation, leveraging Apollo Client (GraphQL) for backend communication. - Delivered mission-critical tools: real-time architectural diagramming (xyflow), rich-text requirement authoring (slate), and hardware/emulator testing interfaces. - Championed developer experience: Implemented Apollo Server mock backend, DI patterns (diod), and PLOC state management. Technical Environment: React | TypeScript | GraphQL (Apollo Client/Server) | Nx Monorepo | Vite/Vitest MUI | React Router | react-hook-form/yup | dnd-kit | OIDC | Robot Framework Impact: Enabled automotive teams to streamline SDLC processes, achieving 10x Faster and 4x Less Cost. Explore the platform: https://v.soda.auto/ Launch Demo: https://youtu.be/rPzKWp0b7co

I was working on implementing a new architecture for frontend of the cloud diagnostic system of the electric vehicles. There was a requirement to be able to build and deploy separate parts of the UI independently. I managed to implement microfrontends approach based on webpack module federation feature (two years ago it was just released) and improved DX for day to day work with modules. We have a several version of the application - two kinds of embedded versions and a cloud version. So there was another requirement, that every page of the application should be able to use with different backends (embedded/cloud). So I've introduced the approach where UI modules were implemented with dependency inversion principle, and than for each application their own api services were injected accordingly. Stack: React, Typescript, emotion, effector, jest, webpack/rollup, babel, lerna/nx.

The main project is a system of collecting, analyzing and visualization of high-frequency updating and historical data, allowing engineers to get detailed information from data sources. - Move from javascriptMVC framework to angular.js, modern stack and further to react; - Make architectural decisions considering requirements of business; - Lead a team of 4 frontend developers; - Planning, estimation, implementation of new features; - Agile development; - Application performance improvement; - Build and deploy systems support; - Unit-testing; - Develop cut-down mobile IOs and Android versions with hybrid web technologies Other projects development: user management system, effective search of patterns in historical data, water pipes burst detection system Technologies used: Typescript, Javascript (ES6+), HTML5, CSS3, Canvas, SVG, Angular.js, Angular 6+, React, d3.js, redux, reselect, ng-rx, rx.js, lodash, mathjs, codemirror, leaflet, REST, Websocket, Webworkers, Webstorage, Jest, Jasmine, Karma, Webpack, Gulp, Grunt, Git, Mercurial, SVN, Jira, LESS, PostCSS, Babel, CSS modules, eslint, tslint, javascriptMVC, JQuery, Cordova, Ionic, Phantomjs + Casper, Cypress