small_avatar_AdrianR3.png

thumbnail_avatar_AdrianR3.png

avatar_AdrianR3.png

Adrian

small_avatar_Grzegorz.png

thumbnail_avatar_Grzegorz.png

avatar_Grzegorz.png

Grzegorz

GET IN TOUCH

Seemingly it is better not to stay in the port during a storm, at least that hypothesis was presented by Robert Zemeckis in "Forrest Gump". In the film the only boat that has stayed on the open sea during a hurricane was the one that belonged to Forrest and Bubba. Thanks to this, it survived and monopolized the shrimp catchers market in the region.

Today, small companies are just like small independent boats. The decision-making process is maximally simplified, and thus, they are agile and flexible. They find themselves better in a dynamic situation and when they see the opportunities they can immediately take action.

At the beginning of the pandemic crisis, the business world held its breath, some for a shorter, time others for a longer time. Some could not or did not want to stop, others were stopped by force, and still others held their breath for so long that they either suffocated or lost their momentum so much that now they are trying hard to come back to reality.

We have taken this opportunity and talked about what is happening here and now during the conversation with Adrian and Łukasz Roth, the founders of Bitnoise, but we also talked with Martyn Roberts, a Scot who lives in Berlin, where he runs Squareball, which is in the top 10 digital studio in the UK (the company's second headquarters is Manchester) and with Luisa Tatoli, an Italian who has been living in London for 7 years and is the managing director of Roll Studio - a digital agency that has cooperated with brands such as Universal, Google, Ikea or Unit9.

We have gained a multicultural perspective and several answers to all the questions that are now bothering us. We have also confirmed that we are in the right place and that, although we are like everyone shocked by what is happening in the world, both we and our partners are relatively well.

Bitnoise's stable position on the market has been strengthened by going virtual. Thanks to the fact that practically the whole world is in the same situation, it is easier for us to communicate, we can share experiences and count on understanding from others, not only within our company, our city but also in the world.

What was repeated in our conversations was the fact that, although we have been ready for the digital revolution for a long time, we needed an impulse in the form of a crisis that forced us to take advantage of already available solutions.

The situation of individual companies in the IT sector depends on many factors, such as the company's current strategy, location of clients, partners on the market, cooperation with specific sectors. Adrian and Łukasz Roth emphasized that the stable position of Bitnoise is a consequence of the strategy of customer diversification and shifting the center of gravity from project-only work to a greater share of stable and long-term contracts. Martyn Roberts noticed that realistically speaking, for many companies in the IT sector, little has changed. Remote work was commonplace, and what other sectors had to deal with, was obvious to those related to IT. Everyone agreed that the basis of a well-functioning company is mutual trust and respect. Luisa Tatoli talked about the unique position of Roll Studio, which is based in Italy and in Great Britain, which are two countries most affected by pandemics in Europe. From her perspective, the policy of the British authorities was completely incomprehensible, since they saw closely what Italy had gone through, while in London the approach to a pandemic, despite the huge number of infections, was very reckless. Roll Studio itself used the Italian experience and prepared well for the onset of a pandemic in London. They switched to 100% remote working mode, took care of their employees, gave up actions that could pose any threat earlier than it was expected by the authorities. And, like people around the world, they locked themselves in their homes. That last aspect of the pandemic turned out to be much less burdensome than one could have been expected. Flexible working time, smooth reconciliation of home and work life, more time with loved ones, and the invaluable impact of a pandemic on the environment are repeated as a big positive of the current situation.

If you want to listen to the whole interviews, you will find them on the [Bitnoise page on Linkedin](https://www.linkedin.com/company/bitnoise/)
.

An unexpected contradiction arises from the pandemic situation. The world may have taken a few steps back in terms of social activity or mobility, but technology has moved with impetus and made us aware that we are ready for professional and social functioning in the virtual world.

With the conversation with Luisa Tatoli, we have concluded sub-section “is IT crisis” and we are heading towards the “digital revolution” with different examples of solutions and tools that can help us with a smooth transition into virtual reality. 

We would also like to talk about the change within us and how to prevent digital exclusion.



small_Blog_artykul_Forrest_cover_high.png

thumbnail_Blog_artykul_Forrest_cover_high.png

Blog_artykul_Forrest_cover_high.png

How does Forrest Gump relate to the pandemic situation?

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)


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

In this blog post, I will explore the responsibilities and significance of a Chief Technology Officer (CTO) role in startups and scaleups and the factors that should be taken into account when deciding between employing an in-house CTO or opting for the services of an external consultant ([CTO as a Service](https://www.bitnoise.pl/services/cto-as-a-service)
). 

**Let's begin with a fundamental question: What is the role of a CTO and what does their operational environment encompass?**

My focus will center on two primary contexts: startups during their initial financing and development phase, and established organizations during the scaling phase. While I acknowledge the existence of other possibilities, the purpose of this post is to offer insights rather than provide an exhaustive list of technological roles. Furthermore, I assume that the distinction between CTOs and Tech-Leads is less significant at this stage, as these roles often interchange and the nomenclature arises more from chance than deliberate decision-making.

#### **The most important qualities of a good CTO**
A Chief Technology Officer (CTO) is a highly skilled professional who assumes overall responsibility for the technological aspects of your startup. They bring extensive experience and expertise in understanding the inner workings of your solution and delivering value to end-users. However, it is essential to consider additional dimensions of this role.

**CTOs come from diverse backgrounds, often having held positions as software developers, tech leads, DevOps specialists, project managers, or even academic personnel.** Within your startup, their responsibilities may encompass technological leadership, research and innovation, business and technology development, product development, and the recruitment of key technical specialists.

Given the wide range of competencies required, finding the right person for the job can be challenging. During the MVP stage, when numerous pressing issues demand attention, the decision to hire a CTO can be overlooked. However, as your startup progresses beyond the MVP stage, effective technological management becomes crucial, especially when addressing any technical debt accumulated during the initial product phase.

What are the most important qualities of a good CTO?

**A leader in technology** 

The CTO plays a critical role in making architectural decisions, ensuring infrastructure scalability, and selecting the most effective tools to achieve both client and company objectives. They may also have greater control over the implementation of tech solutions. 

**Research & development for innovative solutions** 

The CTO holds a unique position in driving innovation by defining key directions for technological advancements. They inspire and motivate teams to think creatively, fostering an environment that encourages innovative ideas and thinking outside the box. 

**Hiring Talent**

Finding qualified candidates in the IT industry can be increasingly challenging. Involving the CTO in the recruitment process for development teams can enhance efficiency and satisfaction for both parties, as they possess the technical expertise to identify suitable candidates. 

**Product & development**

As the representative of the tech team, the CTO must effectively demonstrate how innovation and technology align with customer needs. Collaborating closely with the Chief Product Owner, the CTO ensures the creation of tech-enabled products that meet market demands. 

**Business & technology enabler** 

Working closely with both the in-house tech team and clients, the CTO serves as a bridge between business requirements and technical execution. Their deep understanding of both domains allows them to effectively translate business needs into a comprehensive technical plan.

Having identified the key qualities of a competent CTO in a startup, let us now shift our attention towards examining the benefits and drawbacks of employing an in-house candidate versus opting for the expertise of an external specialist.

#### **Pros and cons of in-house CTO** 
The in-house solution for a CTO has its own advantages and disadvantages. On the positive side, having an in-house CTO provides proximity and familiarity with the organization, but it can be costly. It is particularly beneficial for complex projects involving big data, AI, or large data volumes, whereas it may not be cost-effective for less advanced applications. 

An in-house CTO holds a crucial role within the organization as they possess extensive knowledge of internal processes, strategies, and the target market for product development. This internal perspective fosters a sense of organization, motivation, and deep involvement among team members. Furthermore, this model offers the advantages of high flexibility, simplified organization of agile workflows, and reduced response times for quick issue resolution.

![ ](\uploads\Blog-post_recyklning_ebooka_01_post01_3Ee3fEqUXYzqHJZIusGPIv.png)
#### #### **Pros and cons of CTO as a Service**
CTO as a service provides several advantages and disadvantages. The outsourced CTO is responsible for managing your company's technologies, engineers, IT support, and tech partners, ensuring proper diligence operations. They can work on a part-time, full-time (for a specific project or the entire company), or hourly basis, offering flexibility in decision-making. CTO outsourcing services are particularly beneficial for medium and small companies that don't require a permanent CTO but still need temporary leadership and technical supervision during specific software development cycles or for developer teams. Additionally, CTO as a Service is generally more cost-effective than hiring a full-time expert.

![ ](\uploads\Blog-post_recyklning_ebooka_01_post02_2IDrEsR6eIvGLMp07rarvM.png)

Naturally, the process of hiring a competent CTO poses its own set of challenges, and this blog post may not provide a definitive answer regarding the ideal CTO fit for your business. However, it can certainly help you evaluate the stage of your journey and identify experts best equipped to assist you in progressing further. Several crucial considerations need to be made when determining the type of CTO you require and the necessary skill set: 

1. **Business partner or technical manager:** Do you need a business partner with technological expertise to scale the business, or someone solely focused on managing the technical aspects without involvement in other areas of company development?

2. **Development stage:** Is your business in the early stages, requiring process organization and alignment of business goals with technology? Or are you post-MVP, seeking someone to plan and lead further technological development while building a reliable team? 

3. **Future goals:** If you plan to outsource part or all of your technological team in the future, an in-house CTO would be advantageous. However, if you already have a skilled team and only require part-time technical leadership, CTO as a Service may be sufficient. 

4. **Budget:** Consider the financial resources you are willing to allocate to the CTO position. 


Once you have determined the ideal solution for your organization, you can begin searching for suitable candidates or outsourcing services. 

___
#### **Summary** 
In this blog post, we explore the role of a Chief Technology Officer (CTO) in startups and scaleups and discuss the decision between hiring an in-house CTO or using a CTO as a Service. A good CTO possesses leadership in technology, drives innovation, helps in hiring talent, oversees product development, and acts as a bridge between business and technology.

Having an in-house CTO offers proximity and familiarity but can be costly, while CTO as a Service provides flexibility and cost-effectiveness for smaller companies. Factors to consider include whether a business partner or technical manager is needed, the development stage of the business, future goals, and budget.

Ultimately, finding the right fit for your organization requires careful consideration. Once you determine the ideal solution, you can start searching for suitable candidates or outsourcing services.

If you found this article interesting, we invite you to explore our ebook tailored for CEOs, founders, and product managers. It offers invaluable insights into the product development process, providing you with valuable knowledge and expertise.

[Link: The Product Journey: building application that scale](https://theproductjourney.bitnoise.pl/#form)




small_how-does-remix-enhance-hydrogen-shopify-front-end-development-framework.png

thumbnail_how-does-remix-enhance-hydrogen-shopify-front-end-development-framework.png

how-does-remix-enhance-hydrogen-shopify-front-end-development-framework.png

CTO as a Service or in-house CTO? Which is best for you?

How does Forrest Gump relate to the pandemic situation?

Martyna

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

Tomasz

CTO as a Service or in-house CTO? Which is best for you?

Łukasz

GET IN TOUCH