When I recieved a request from Personal Trainer I was quite interested as sports is one of things I love doing in my spare time. Working on www.sadowskitrenuje.pl offered me a great opportunity to learn more about Next.js.

It is a fairly simple design with some practical features like contact mail form and included payment links. My primary focus was laid on reflecting the design the client demanded.

I hope end-users will be as satisfied with using this website as I was from the effect.

As NorthGravity employee, I was involved in building the core product offered by the company.

Work was wrapped in two week sprints, during which I did my best to deliver particular pieces I was assigned with.

It usually included implementing features requested by clients or proposed by the R&D team and then showcasing those to the stakeholders.

My superiors appreciated my attitude towards our clients as well as communication skills and marked them as one of my strengths.

One of my first tasks, which helped me to get into real life development was creating an important part of the application my company was developing, which is Knowledge Center.xxx

I co-build most of the features in this subproject, which enables the platform users to understand how to use it and where to find particular tools and features.

It was important especially for the new users or future clients to see the full potential of the website.

While working on this project I learned a lot, especially about implementing search calls support as well as navigating and scrolling to particular headers of a blog article or documentation page.

One of my biggest responsibilities while working for NG was to introduce unit tests into the frontend part of the application.

For sure, I can say that I learned a lot about setting up test environments for projects using Webpack and Rollup and preparing tests of course.

I prepared tests for the custom components library, as well as those checking API handling methods.

Unit testing with Jest is quite a modern way to secure the components from unnecessary failures while being used in views and pages of the application. The testing framework features were additionally extended by other useful methods from Testing Library, which helped me render and rerender components, as well as mock user interactions in a nice and clean way.

I hope we all can agree that tests make applications more reliable . Going further, I believe that the time I spent on these tasks was the next pebble on the road to achieve reliable and safe code.

Apart from building components and creating new functionalities, my work also focused on fixing bugs which were reported by testers or found while further development of the application.

In order to do that, I needed to read a lot of code, quite frequently spread across the project. I find it really useful for deeper understanding of how different parts of the application works.

Reading code builds a firm idea on how data flows through the application , which I believe I have.

My tasks sometimes included working with legacy code also.

The majority of application code I worked with was built using functional React components, although some of them, especially older parts were coded with JS classeswhat probably occur a lot in projects developed for couple years already.

I learned how this approach can give us some advantages (eg. using specific boundary components to pass redux props to their children).

To the contrary, the most challenging task in terms of handling solutions used in the past, was to prepare HTML/FTL templates to be used with Outlook 2013 and older versions of this popular software.

Tasks like that seem annoying and boring but I do approach these in different manner. I believe them to be challenges, which can be cracked with use of some extra time and effort and can give us valuable lessons and help value more modern solutions.