small_avatar_AdrianR3.png

thumbnail_avatar_AdrianR3.png

avatar_AdrianR3.png

Adrian

GET IN TOUCH

Welcome to the next episode of our **“Bitnoise Tool Set”** series, where we dive into the technologies and workflows that power our teams. Today, we’re focusing on the toolkit of a **UX/UI Designer** – the essential tools they use to design, prototype, and deliver intuitive, scalable digital experiences.

This article takes the form of an interview with  our senior designer, offering firsthand insights into their daily design workflow. We’ll explore not only the creative toolkit – **design software, prototyping tools, and collaboration platforms** – but also some more casual topics like **sources of inspiration, favorite side hobbies, and personal productivity hacks.**

Whether you’re an aspiring **UX/UI Designer** or just curious about our tech ecosystem and design, this guide will give you a behind-the-scenes look at how our team works.

Let’s dive in!

#### Łukasz Berliński, UX/UI Designer

I’ve been part of the design industry for **over 17 years.** My first commercial web design projects date back to my university days. Although I hold a degree in Automation Engineering, I fully transitioned into the design field early in my career.

Today, I specialize in designing both **desktop and mobile applications,** though I also have experience in other areas of design.

Outside of work, I’m passionate about 3D printing, retro gaming consoles, and Lego.

#### Essential Tools

- My everyday toolkit includes **Figma, Miro, After Effects, Photoshop,** and **Illustrator.**

- In terms of hardware, I work on a MacBook Pro with high-quality monitors to ensure precision and clarity.

#### Design Systems

I regularly work with design systems – ranging from standardized frameworks like Google’s Material Design, to custom systems developed for clients. **I’ve also created several systems from scratch,** both simple and complex, depending on project needs.

#### Prototyping and Testing

I primarily use **Figma** for prototyping – it’s fast, efficient, and allows for immediate feedback. **Prototypes are a standard part of my process** and help clients preview the application’s functionality before development begins. **This early validation step is crucial for aligning expectations and preventing issues down the line.**

For usability testing, I tailor the approach and tools based on the project, but always prioritize quick iterations based on real user feedback.


#### Collaboration

In the past, I used **[Zeplin](https://zeplin.io/)** during the **[Sketch](https://www.sketch.com/)** era, but nowadays I rely almost exclusively on **Figma.** Its **Inspect** and **Dev Mode** features are more than sufficient for efficient handoff.

For more complex projects, I always schedule alignment meetings with developers to make sure we’re fully synced on interactions, animations, and overall design intent.

For communication and project management, I’ve worked with tools like **Slack, [Trello,](https://trello.com/home) [Asana,](https://asana.com/) and [Notion](https://www.notion.com/)** – whatever best fits the team setup.

#### File Management & Backup

I take file security seriously. As the saying goes: _There are two kinds of people: those who back up their data – and those who will._

After learning the hard way years ago, I now maintain both local backups (via **NAS with an off-site mirror**) and cloud backups to ensure nothing gets lost.

#### Automation & Productivity

Absolutely – **AI has been a game-changer.** Tasks that used to take hours can now be done in seconds: generating avatars and illustrations, filling prototypes with sample user data, or extending and adapting images for better composition. What was once tedious manual work can now be done with just a few clicks.

#### Workflow Optimization

I constantly **explore new tools and workflows that improve efficiency,** especially for task management, time tracking, and team collaboration. Custom keyboard **shortcuts, Figma plugins, and smart templates** are part of my everyday workflow.

#### Learning & Growth

I make it a point to stay current with new features in design tools and evolving UX trends.
I regularly listen to design-related podcasts from **[Design Practice](https://open.spotify.com/show/7Ln0idf6W9q6M7CEyWS3Xb?si=2LIXBnpsRxSuI92jpe6C9Q&nd=1&dlsi=f01ceb0c3491469d),** **[product dissign](https://open.spotify.com/show/22rEcROWUO4tqcvwSOSB84?si=IoiAfBtSSOKO50U7VhVi9w&nd=1&dlsi=a6c90f76021d4761),** **[UX po Godzinach](https://open.spotify.com/show/1SOUA8UPfusGYKE1oj2YTC?si=pDq9G1k5QJKmJMi2fa2LjA&nd=1&dlsi=dc65ae24f8854740),** read industry articles, and follow YouTube channels and Reddit communities focused on UI/UX.

#### All-Time Favorite Tool

Today, it’s probably **Figma** – but deep down, old-school **Photoshop CS3** still holds a special place in my heart.

#### Advice for New Designers

Learn by observing those with more experience. Creativity is essential, but many design problems have already been solved – **don’t waste time reinventing the wheel.**

And most importantly: **communicate.** Early in your career, it might feel like designers and developers are on opposing teams – but **with clear, respectful communication, that barrier disappears.** In the end, you’re working toward the same goal: **delivering a great product.**

#### Quick Questions

- Operating system? → **MacOS,** although my phone is a **Pixel with Android.**

- Light mode or dark mode? → **Dark mode**

- Browser? → **Firefox**

- Favorite browser extensions? → **[Bitwarden,](https://bitwarden.com/)** **[FontsNinja,](https://fonts.ninja/)** **[SVG Gobbler](https://svggobbler.com/)**

- Your favorite app? → **[GoodNotes](https://www.goodnotes.com/)** (iPad), **[Spotify](https://open.spotify.com/)**

large_blog_cover_ŁukaszB.png

medium_blog_cover_ŁukaszB.png

small_blog_cover_ŁukaszB.png

thumbnail_blog_cover_ŁukaszB.png

blog_cover_ŁukaszB.png

Bitnoise Tool Set, Part 3: UX/UI Designer

Frontend Engineering

UX/UI Design

Research & Discovery

AI For Your Business

Services

Case Studies

About us

Blog

There comes a point in nearly everyone’s career where they feel that it’s time to make a switch. At times, the feeling comes out of the blue - completely unprompted. On the other hand, you could spend years considering whether to change your specialization without making a move.  Today, you’ll get some insight from Tomasz, who switched from Java to become a senior Node.js developer when he joined our team at [Bitnoise](https://www.bitnoise.pl/)
. The jump seemed risky at first, but in the end, Tomasz settled in beautifully. Here’s what he learned.

#### Tomasz, what is your technical and educational background?
My technical and educational background are quite intertwined. While I always wanted to work with computers, my story didn’t really start until I attended the Poznań University of Technology. I graduated from there with a Master’s degree in Computer Science. During this time, I completed a successful stint as an analyst and research programmer at the university, which helped me grow a lot as a programmer.

Most of my studies focused on C#, which was the programming language preferred by the majority of universities at this time. That said, I also took a course that covered Java. From that point onward, my career centered around Java development.

#### How did your career as a software developer start?
By the time I graduated University, I knew I wanted to be a software architect. However, I was still pretty naive. I didn’t realize that before becoming a software architect, you must spend significant time in the trenches as a developer first.

I scoured the internet for architect job postings. There were a few, but none that I was qualified for. Meanwhile, I found dozens of good job offers for Java developers. I quickly realized that I had no choice but to work as a developer first. I thought to myself “why not?” as I accepted my first job working for PayU.

#### What were your first steps in commercial software projects?
I took my first steps during my university years. PayU was also pretty active in hiring junior developers at my university. I cut my teeth on my first commercial software projects there.   These projects weren’t simple. If you weren’t aware, PayU is a major online payment platform. Nowadays, Naspers Corporation owns it. As employees, our project managers held us to a high standard. And the company was extremely well organized, which I appreciated.

In my three years working for PayU, I evolved into a full-fledged developer. I credit the company and the people who worked there for much of my growth as a developer.

#### But you still worked with Java, how did you switch to Node.js?
While working at PayU, I became a little restless and decided it was time for a change. I had a friend who worked at a small local company, so I decided to take my talents there. One of the advantages of working at this company was that they gave me a lot of freedom. My natural curiosity prompted me to learn Node.js. This was a boon to my growth as a developer.

Coincidentally, one of my tasks at this company was to build an API gateway. We decided to use Node.js for this purpose because it was far simpler and quicker to implement than Java.

#### So, two major factors influenced the change: opportunity and willingness to experiment.
No doubt. It’s one thing for you to play around with new programming languages all day, but necessity is the mother of all invention. If one of your higher-ups at your job has the open-mindedness to try a new technology, the world is your oyster. You can begin taking on bigger and bigger challenges with new approaches each time.

I think it’s always fun to challenge yourself. However, not everyone dares to leave their comfort zone. In this case, their tech stack. You could spend years using the same language and never truly grow as a programmer. In this industry, it’s important to constantly try new things and take the opportunities that present themselves. That’s how you get an edge both at your current job and when you’re trying to find a new one. 

#### What were the next steps in your journey toward Node.js?
After working for this smaller company, I transferred to a software development company named Espeo. Once again, I was happy that my superiors at Espeo were technologically agnostic. When we worked on projects, we wanted to use the right tool for the job, rather than choosing the same one because we always used it.

I worked with Java, Python, PHP, and Node.js. Not to mention, I did a bit of work with blockchain technology as well. Given that Node.js has one of the most extensive Ethereum libraries around, it only reinforced my positive impression of it.

At this point, I had built up 7 years of programming experience working with a variety of programming languages. I would say that Java still dominated my work, but Node.js was probably second. If you asked me what kind of developer I was back then, I would have told you I was a Java developer for sure.

#### And then Bitnoise called you…
Indeed. The pitch got me pretty excited. Most companies have clients, but they don’t get to be nearly as hands-on with projects as Bitnoise is. Not to mention, I appreciate that Bitnoise prizes experienced senior-level employees. As a result, they offered me a role as a senior Node.js developer. I thought this was quite a coup, considering that Node.js wasn’t even the main technology I worked with.

One of my first projects at Bitnoise involved an HR Tech startup called JOIN. Working with such a fast-growing firm is incredible. The best part was, JOIN’s CTO is extremely open-minded too. As a result, he accommodated the fact that I’m not a Node.js specialist.

I’ve already been working with JOIN for three years, and I’m still as passionate about the project today as I was the day I started, if not more! Growing alongside Join and my colleagues at Bitnoise has been extremely rewarding. Watching a startup evolve into a major player is a bit like watching your nephew or niece grow up.

#### Let’s focus on the challenge of switching from Java to Node.js - although it seems frictionless in hindsight, were there any initial fears or challenges?
As I mentioned before, I was now designated as a senior developer in a programming language I didn’t specialize in. I certainly had reservations about starting from a lower level. It felt a bit like I was back at square one, I lost a lot of the confidence I built up during my 7 years in the industry. It forced me to work harder than I ever did before to prove myself.

Imagine moving from Manchester United to Real Madrid. You already know you’re a good player, but you still need to impress the new fans. In this case, I knew I was a good developer, but I still needed to impress my colleagues and our clients. This type of competitive mentality is rewarding; I learned lots of new things and emerged with newfound confidence. Switching to a new environment also changes your perspective.

#### What would you tell a fellow senior backend developer considering a switch?
A good developer understands that the programming language you use is merely a tool. As you gain experience, you realize that the same problem-solving skills underlie each language you use. Eventually, these tools become interchangeable. And you don’t need to worry that Node.js is a newer language. You can use it for the same purposes that you would for Java. I promise any developer that switching to Node.js won’t make you feel inadequate.

Of course, Java and Node.js are quite different. However, the difference is more comparable to playing for two different football teams than it is to the difference between playing football to basketball. Any developer worth their salt can make the switch if they put in the effort.

#### Besides the tech stack, what are some important reasons for a senior developer to move to a different project?
I’ve already covered the technology part, that’s really just about adding a new tool to your arsenal. I actually think that work culture is by far the most important determinant of a project’s success, so I look at that. Above all, I prefer working in a Test-Driven Development environment (TDD). Essentially, it means that we prioritize product quality above all else. We run lots of tests before we write the code.

There are other elements that some might consider superficial, but which I find quite relevant. For instance, you need to have a degree of flexibility in all approaches, not just with coding. We recently switched from Scrum to Kanban to organize our JOIN project because we felt it would improve our efficiency in the long run.

I’ll share one last bit of philosophy with you. I’m not someone who thinks that software development is an art. Rather, it’s a means to an end. That end should be twofold: to increase your business’s value and to provide your users with the best possible experience when they use your products.  That’s the great part about working with Bitnoise, we don’t try to glorify our tools. Rather, we aim to elevate our clients and the users that they support. I think it takes humility for a company to recognize what’s truly important.

#### Thank you, Tomasz, for sharing your experience with us!
You’re welcome. The pleasure is entirely mine!

#### Tech summary
During our interview with Tomasz, we discussed Java and Node.js at length. Let’s dive into some of the specifications of these two backend technologies. They’re both quite popular, but Java is quite a bit older. Java’s initial release was in 1995 while Node.js didn’t come out until 2009.

Node.js is part of the JavaScript stack; it’s a JavaScript runtime environment. Meanwhile, Java is a full-fledged programming language that aims to have few dependencies. You can use both languages to build sophisticated backends for web and mobile applications. That said, these languages have substantial differences that we’ll investigate further.  

**Java** 

Java is one of the first languages that come to mind for any programmer. It’s been established as one of the best technologies for developing applications and is considered a heavyweight by almost everyone in the industry.

Originally, developers used Java to create desktop applications. However, Java has gained popularity for many other purposes. Many large and complex applications like social media platforms tend to appreciate Java. Not to mention, banking applications, metaverse games, ERP solutions, and CRM applications use the language for their backend too. Spotify, Twitter, and Minecraft are all examples of popular apps that were written in Java.   

**Node.js** 

While we can consider Java to be one of the heavy hitters among programming languages, Node.js is a more lightweight tool. Ryan Dahl created Node.js in 2009 to serve the community’s need for a friendlier, lighter backend technology. The platform is based on JavaScript and is open-source; there are several free Node.js libraries that can help with your use case.

Of course, since Node.js is based on Javascript, it’s extremely easy for Javascript developers to learn this technology. As a result, many startups have opted to use Node.js over similar options since the learning curve is quite minimal in comparison to other languages.   

**Advantages of Java** 

There’s a reason why Java has been widely trusted by developers since 1995. It has a rigid structure that stands the test of time. Consequently, Java helps you build extremely stable applications. Any software you create with Java will be durable and you’ll easily minimize the risk of errors.

Another advantage to Java is that it’s a statically-typed language. Once again, this reduces the chance of errors since every variable, object, and so on is well-defined. To achieve this level of definition in Node.js, you would need to use TypeScript in tandem with it, since TypeScript requires you to define the type of variable each time that you set one.

**Advantages of Node.js** 

Even with Java’s reliability, Node.js possesses several important advantages of its own. The main one is speed of development - writing Java code is quite a bit slower than most native languages because it uses compilers.

Furthermore, Node.js employs an event loop mechanism that allows servers to respond to requests without blocking input and output operations. As a result, Node.js is extremely scalable, which makes it perfect for startups that need room to grow.

Of course, with all these advantages, many developers are eager to learn Node.js. Some, like Tomasz, have already learned the language at work. There are others that have spent years working with the technology already. Due to its popularity, it shouldn’t be hard to find a quality developer willing to make the switch to Node.js.  

#### The start-up’s dilemma - Java or Node.js?
When you first found your startup, you have some serious decisions to make. Your initial choice of technology could be the most important of them all. Choosing between Java and Node.js will have a major impact on the success of your application or SaaS. Choose wisely.

You can rest assured that you will have no problems developing a stable backend with either of these technologies. However, since Node.js is a lightweight technology and draws heavily from JavaScript, it’s far easier for most developers to train in or switch to Node.js than it is for them to switch to Java. After all, Java has a pretty high barrier to entry. There are a lot of technical details you need to learn which makes switching to Java a rather uncommon event.

As a result, recruiting Java developers becomes a bit of a pain. The difficulty of the language means that there is a deficit of Java developers available on the job market. We mentioned that quite a few largescale applications use Java. Guess who you’ll be competing against when recruiting Java developers? The likes of Spotify and Twitter will be in on the action, as will be large banks and insurance companies. For most startups, this is a rather intimidating proposition.

Based on our experience at Bitnoise, we encourage founders and CTOs to use Node.js for their backend. Node.js will help you get the job done just as well as Java in 99.9% of cases. And even if you’re already a Java developer, building a solid team of Java developers around you will be arduous and expensive.

As Tomasz proved, it’s not too challenging for a Java developer to switch to Node.js. Many are eager to make the jump. Given an enticing opportunity at your startup, you’ll have few problems attracting Node.js developers, even at the senior level.

![ ](\uploads\Blog_artykul_TomekC_Java2NodeJS_blog_02_4u5EhT3eltrHOSjoUwieyy.png)
#### Why switch to Node.js as a developer?  
- It’s relatively easy to switch if you already know other backend technologies  

- Node.js is growing in popularity and many startups use it as their primary technology

- It can achieve almost the same results as other languages

- Using Node.js helps see results faster than Java, among others


![ ](\uploads\Blog_artykul_TomekC_Java2NodeJS_blog_01_50tuNqSJuA9HWdB0ty5tsl.png)


large_Blog_artykul_TomekC_Java2NodeJS_cover_high.png

medium_Blog_artykul_TomekC_Java2NodeJS_cover_high.png

small_Blog_artykul_TomekC_Java2NodeJS_cover_high.png

thumbnail_Blog_artykul_TomekC_Java2NodeJS_cover_high.png

Blog_artykul_TomekC_Java2NodeJS_cover_high.png

Switching from Java to Node.js as a senior developer - Tomasz’s story

#### What Tools Does a Senior Full Stack Developer Use?

Welcome to first 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 **Senior Full Stack Developer** - the key tools they rely on to build, maintain, and scale our 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 full stack developer 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!

#### Łukasz Duraj, Senior Full-Stack Developer.

I have **13 years of experience.** I mainly program in **PHP** and **NodeJS.** Additionally, I have worked commercially with Java and Python on the backend, as well as with various frontend tools - from jQuery and Angular 1 to React, React Native for mobile, and React frameworks like Remix and Next. I also focus on application architecture on the backend and cloud infrastructure (AWS/GCP).

#### Essential Tools

I use the entire IntelliJ suite - **PHPStorm, WebStorm, IDEA,** and **PyCharm.** These tools provide a very rich feature set. The most important tool for me is always the **debugger,** whether it’s **XDebug integration in PHPStorm** or running applications with built-in framework tools. It’s crucial for me to be able to step through an application from checkpoint to checkpoint.

Additionally, integrations with **Docker, databases,** and **Git** (such as performing Code Reviews directly in the editor) are indispensable.

#### Languages & Frameworks

It depends on the project. **I prefer working without a framework or with micro-frameworks.** In PHP, these would be **Symfony-based micro-frameworks,** and in Python, Flask. However, I most often work with:
- **Nest.js** in NodeJS
- **Symfony/Laravel** in PHP
- **Django** in Python


#### Code Management & Collaboration

I only use **[Git](https://git-scm.com),** as SVN is rarely used nowadays.
I’ve worked with **[GitHub](https://github.com), [GitLab](https://gitlab.com),** and **[Bitbucket](https://bitbucket.org),** and I don’t have a strong preference between them.
For team collaboration, it depends on the project. I mainly use **[Slack,](https://slack.com)** but I’ve also worked with **[Discord](https://discord.com)** and even [Gadu-Gadu](https://en.wikipedia.org/wiki/Gadu-Gadu) back in the day.

For project management, I’ve used many tools, including **[Jira](https://www.atlassian.com/software/jira), [Trello](https://trello.com), [Asana](https://asana.com), [Phabricator](https://phacility.com),** and **[YouTrack.](https://www.jetbrains.com/youtrack)** However, **[Linear](https://linear.app/) has recently won me over with its fantastic process automation features.**

#### DevOps & Deployment

**I work extensively with CI/CD** and have set up CI/CD pipelines from scratch using **GitHub Actions, GitLab CI/CD, Bitbucket Pipelines, CircleCI,** and **Jenkins** - depending on project needs.

For monitoring and logging, I primarily use **[Sentry,](https://sentry.io/welcome/)** but I also rely on AWS **[CloudWatch](https://aws.amazon.com/cloudwatch/)** and **[GCP](https://cloud.google.com/)** logs. I’ve worked with **[Datadog](https://www.datadoghq.com/) and [Grafana](https://grafana.com/)** logs as well.

#### Debugging & Testing

**The IDE debugger** is my primary tool - I try to use it **always and everywhere.**

I test using libraries built into the respective environment, such as **[PHPUnit](https://phpunit.de/index.html)** for PHP and **[Jest](https://jestjs.io/)** for NodeJS.

#### Productivity & Workflow

I use **Google Keep** for quick notes and **Google Calendar** to manage everything I need to remember or schedule.
I’ve tried many productivity tools, but none worked for me in the long run.
At one point, I also used the **[Pomodoro technique](https://en.wikipedia.org/wiki/Pomodoro_Technique)** quite often.

#### Learning & Self-Development

Mainly conference talks. I also buy books on software architecture and take courses from **[DevStyle.](https://devstyle.pl/)**
I follow materials published by **[Bottega IT Minds.](https://bottega.com.pl/)**

#### All-Time Favorite Tool

**[Docker](https://www.docker.com/)** ❤.
That's my primary tool. Except the NVM for managing NodeJS versions, I don’t have any installed tools - I set up everything locally using Docker.
This allows me to virtualize any environment and tools I need. Most tools also have Docker images, so testing them is as easy as pulling the right image.

#### Quick Questions
- MacOS, Windows, or Linux? → **Linux**
- Light mode or dark mode? → **Dark mode**
- Which browser do you use? → **Chrome**
- Favorite browser extensions? → **[Grammarly](https://www.grammarly.com/), [Simple Translate](https://simple-translate.sienori.com/)**
- Your favorite mobile app? → Recently fell in love with **[BookBeat](https://www.bookbeat.com)**

large_ŁDblog_cover_high.jpg

medium_ŁDblog_cover_high.jpg

small_ŁDblog_cover_high.jpg

thumbnail_ŁDblog_cover_high.jpg

ŁDblog_cover_high.jpg

Developer’s Tool Set part 1: Senior Full-Stack Developer

#### 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/)

Bitnoise Tool Set, Part 3: UX/UI Designer

Dominika

Switching from Java to Node.js as a senior developer - Tomasz’s story

Tomasz

Developer’s Tool Set part 1: Senior Full-Stack Developer

Łukasz

Developer’s Tool Set part 2: Principal Frontend Engineer

Adam

GET IN TOUCH