- lead the development of an open source React design system
- improved experience for many developers in the team as a frontend platform developer
- refactored and managed set of projects into a monorepository
migrated documentation to Gatsby
- developed booking of travel tickets with a lot of end-to-end tests

Senior JavaScript Developer

- developed a GIS React app
- used Flow for type checking
- refactored code using codemods with jscodeshift
- mentored junior developers

React Developer

- worked with a remote team of 60+ developers
- developed a Phoenix project (an MVC framework in Elixir)
- enhanced the stack with modern frontend practices

Frontend Developer

- worked with skilled graphic and motion designers
- built many static web sites, and started specializing in SSG
- as this was the advent of Node.js I continuously explored all the latest tools

- developed a Rails dating app
- eventually started moving away from Ruby

I worked with React in all sorts of ways, building apps, generating static sites, building presentations, designing emails… I'm on the lookout for best React frameworks, which is for me currently Remix, but I familiarized myself with Next.js as well because it's the most popular one at the moment.

Responsive design is so much more than just media queries, it's loading best images, providing progressive enhancement, ensuring accessibility etc. I've kept a close eye on this field and learned how to test as much as possible.

Through technologies like Remix and Prisma I'm learning a lot about full stack development. It hasn't been long, but it has been intense. Developing with Remix has helped me become a much better developer by focusing on user experience using native web technologies and edge computing.

When I was building static sites, I started using Node.js heavily, familiarizing myself with all kinds of build tools. Since then I've always been a fan of automating tedious tasks and making the development experience as best as possible.

When I started building apps I used it for a long time, I learned as much as I could about the API, but after a while it became quite messy, and other bundlers started showing up, so I switched to those.

I'm a huge fan of styling with Tailwind and I know just about everything about it and I've used it in many personal projects. I haven't had a chance to use it professionally yet as it's quite controversial, but I hope to in the future.

Frontend testing technologies took a long time to develop, but today they are great, I use many of them for personal and professional projects. Testing Library was quite a revolution in frontend testing and made it easier for everyone. I learned and taught both unit and end-to-end testing, writing tests now comes as second nature to me.

Learning TypeScript was easier for me because I already knew Flow, but it was still quite a transition. I used it professionally for years, refactoring Flow projects to TypeScript, teaching it to others etc. While I do think it's ultimately better, error messages were infinitely better in Flow. 😄

Git is one of the first technologies I learned, and thanks to my good mentor I seem to like it more than most developers. I'm always happy to learn new tricks, like using bisect to find the commit that broke something. I even wrote a series of four blog posts on maintaining a better Git history.

I've been involved with open source pretty much since the beginning of my career. I've contributed to many different projects, some even as a core developer. I acquired many skills that way, like Git, publishing packages, communicating, planning etc. It made me into the developer I am today.

Since the beginning my editor of choice was Vim. When I used editors like Atom and VS Code, I eventually installed Vim keybindings because I was much faster that way.

Personal details

Matija M.

Summary

Technical skills

Work Experience