small_avatar_AdrianR3.png

thumbnail_avatar_AdrianR3.png

avatar_AdrianR3.png

Adrian

GET IN TOUCH

#### What Tools Does a Principal Frontend Engineer Use?

Welcome to the second episode of our **“Developer’s Tool Set”** series, where we dive into the technologies and workflows that power our engineering teams. Today, we’re focusing on the toolkit of a **Principal Frontend Engineer** - the key tools they rely on to build, maintain, and scale applications efficiently.

This article takes the form of an interview with one of our senior developers, offering firsthand insights into their daily workflow. We’ll explore not only the technical stack - backend frameworks, frontend libraries, cloud infrastructure, and DevOps tools - but also some more casual topics. Expect answers to questions like: What’s your favorite mobile app? Which browser do you use? Do you prefer dark mode or light mode?

Whether you’re an aspiring Principal Frontend Engineer or just curious about our tech ecosystem, this guide will give you a behind-the-scenes look at how our team works.

Let’s dive in!

#### Adam Misiorny, Principal Frontend Engineer

I have been coding for **over 20 years** now. I started my developer journey writing **PHP** code, mostly using the [**Symfony**](https://symfony.com/)framework and **good old [jQuery.](https://jquery.com/)**

Halfway through my career, I fully shifted to the **JavaScript stack,** focusing mainly on the frontend.

Nowadays, I’m part of the platform team in one of our projects, where I deal with frontend architecture, automation, optimization, and technical debt - all to help our frontend teams work as efficiently as possible.

#### Essential Tools

I recently migrated from [**Visual Studio Code**](https://code.visualstudio.com/) + [**Copilot**](https://code.visualstudio.com/docs/copilot/overview) to [**Cursor,**](https://www.cursor.com/) mostly for its AI capabilities.
As for extensions, I’m using plugins for [**ESLint,**](https://eslint.org/) [**GraphQL,**](https://graphql.org/) [**Docker,**](https://www.docker.com/) [**Cucumber,**](https://cucumber.io/) environment variable file highlighting, [**GitHub Actions**](https://github.com/actions) and pull request integration, as well as [**GitLens.**](https://www.gitkraken.com/gitlens)

#### Languages & Frameworks

I work mostly with **TypeScript/JavaScript.** I try to do as much as possible in my editor: [**Cursor,**](https://www.cursor.com/) but for the terminal and running apps, I’m using [**Ghostty.**](https://ghostty.org/)

Since I work with **a three-monitor setup, I use one monitor for the editor and browser, and another purely for the terminal.**

For browsing and debugging, I use Google Chrome.

For Git management, I use [**Sourcetree.**](https://www.sourcetreeapp.com/)

I mainly work with the **React** library and frameworks like **Next.js** and [**Modern.js.**](https://modernjs.dev/en/)

A must-have for me is [**GraphQL Codegen,**](https://the-guild.dev/graphql/codegen) which allows us to generate all the code for backend communication based on the schema, with proper types.

For Slack integration, I use [**Bolt.js.**](https://tools.slack.dev/bolt-js/)

For monorepo management, I use [**Turborepo.**](https://turbo.build/)

#### Code Management & Collaboration

- Git
- Github
- Slack
- Jira
- Confluence
- Figma


#### DevOps & Deployment

We currently have several legacy workflows in the project on [**CircleCI,**](https://circleci.com/) but for all new workflows, we use **GitHub Actions,** as it is more convenient to work with.

And also, we use:
- [**Grafana**](https://grafana.com/) for infrastructure monitoring,
- [**Sentry**](https://sentry.io/welcome/) for error reporting,
- [**Jaeger**](https://www.jaegertracing.io/) for tracing,
- **Google Cloud Logs** for logging.

#### Debugging & Testing

Depending on the situation, I use the **editor debugger, browser debugger,** or even **good old console.log** when it gets the job done.

For testing, I use:
- [**Jest**](https://jestjs.io/) and **React Testing Library** for unit tests,
- [**Cypress**](https://www.cypress.io/) for full-stack end-to-end tests, 
- [**Playwright** ](https://playwright.dev/)for frontend-only E2E tests.

#### Productivity & Workflow

I use [**Raycast**](https://www.raycast.com/) with multiple plugins and shortcuts to simplify and speed up common tasks, and **I rely on the right mindset - always questioning why something is happening or not working to get to the root cause and solve it effectively.**

#### Learning & Self-Development

Everywhere I can find useful, high-quality information - online courses, YouTube, X (formerly Twitter), Medium, etc.

Recently, I’ve really been into watching [**Theo**](https://www.youtube.com/@t3dotgg) and [**ThePrimeTime**](https://www.youtube.com/@ThePrimeTimeagen) on YouTube.

Lately, I've been using [**Bolt.new**](https://bolt.new/) for some quick experiments with new code.

#### All-Time Favorite Tool

[**Cursor!**](https://www.cursor.com/)

#### Quick Questions
- Operating system? → **MacOS**
- Light mode or dark mode? → **Dark mode** everywhere where possible
- Browser? → **Chrome** / [**Brave**](https://brave.com/)
- Favorite browser extensions? → [**React Developer Tools,**](https://chromewebstore.google.com/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi) [**Last Pass,**](https://www.lastpass.com/) [**GraphQL Network Inspector,**](https://chromewebstore.google.com/detail/graphql-network-inspector/ndlbedplllcgconngcnfmkadhokfaaln) [**Apollo Client Devtools**](https://chromewebstore.google.com/detail/apollo-client-devtools/jdkknkkbebbapilgoeccciglkfbmbnfm)
- Your favorite app? → [**Raycast**](https://www.raycast.com/)

large_blog_cover_highAdam.png

medium_blog_cover_highAdam.png

small_blog_cover_highAdam.png

thumbnail_blog_cover_highAdam.png

blog_cover_highAdam.png

Developer’s Tool Set part 2: Principal Frontend Engineer

Frontend Engineering

UX/UI Design

Research & Discovery

AI For Your Business

Services

Case Studies

About us

Blog

Adam Misiorny is a Frontend Engineer and Tech Lead at Bitnoise. Since Adam is one of the most experienced software developers on our team, we thought he would be the perfect person to offer insight into how our different developers cooperate during their work.

#### You are a leader, but what exactly is your role in your current project?
At the moment, I’m a Frontend Principal Engineer in a long-term project with JOIN. This means I have the most detailed knowledge of the project and the associated systems. As a result, I’m the one who makes decisions regarding development directions and front-end architecture. It’s a big responsibility. Sometimes, I work on developing the platform itself, but mostly, I’m in a leadership role.

From the perspective of the front-end developers working alongside me, my task is to accelerate product development and render it as efficient as possible. Since I am tasked with ensuring efficiency, I also get in the trenches and help solve complex problems should the situation require it. I’m always of use to other developers.

#### As a Frontend Principal Engineer, do you take part in onboarding new developers at Bitnoise?
Indeed, I often introduce new developers to the project. I take an active role so that each developer can get started working on our products quickly and eliminate onboarding uptake time.

Part of this onboarding task is to acquaint developers with our application architecture and coding standards. This helps light the path forward for quality work to get done. Under my watch, developers familiarize themselves with the common processes we use with each project. These range from pull requests to production deployment.

#### And how do you work with new developers in the project?
I assign each of my junior and middle-tier developers a senior “coding buddy” who assists them with their daily tasks if necessary. As the Principal, I supervise the developers at the review stage with an emphasis on the initial stages to ensure that we set the right tone. Should any of my developers have an inquiry, I am quick to answer them and assuage their doubts.

My role as a consultant is one of the most critical parts of my job. I need to give every developer context as to why we approach each problem a certain way. Less experienced developers soon absorb our general programming ethos at Bitnoise as a result. Understanding is the key to growth.

![ ](\uploads\Blog_artykul_Adam_React.js_02_BZ72URItqw8KOX2g07eZS.jpg)
#### What surprises you about working with less experienced developers? What attitude do you expect from juniors and mids?
While I am usually busy shepherding young developers, it’s not uncommon for me to learn a thing or two from them myself. My experience is a major asset, but that can sometimes mean that my programming approach is rather fixed. I benefit quite a bit when I receive fresh perspectives from young computer science graduates. Our work is enriched when I can look at an issue from a different angle.

Above all, I prize developers who have a passion for learning. Anyone who hungers for knowledge can be taught anything, making them more adaptable as programmers. It’s no use trying to force-feed solutions to a disinterested developer. You can lead a horse to water, but you can’t make it drink.

#### What keeps you in Bitnoise for so many years? If I'm not mistaken, this year we'll be celebrating your 10th anniversary at Bitnoise!
It’s a fantastic atmosphere. Isn’t it? After 9 years of working here, I still haven’t tired of my role. And I’ve grown along with it. Even as Bitnoise has evolved and grown, the team spirit has never changed.

When I was a young programmer, I worked on several projects with diverse topics. Consequently, my breadth of programming knowledge skyrocketed, and today I am happy to say that I have experience that ranges the entire spectrum of software development.  Once Bitnoise assigned me as the leader of a long-term project, I appreciated the new stability. It felt as though I had been preparing for years for this role given my work in so many different fields. After 4 years of working with JOIN, I still haven’t grown bored of the project – it keeps me on my toes as I learn new ways to solve the problems we encounter.

If you’re looking to work for a stable company where you can grow your programming skills, I highly recommend working at Bitnoise. The atmosphere is, as I said, top-notch. Personal development is a priority for all of us.



Developer’s Tool Set part 2: Principal Frontend Engineer

Adam

How do mid and senior React.js developers cooperate at Bitnoise?

Adam

GET IN TOUCH