This year, in September, I was finally (after the COVID “dark times”) able to attend the real conferences. This one took place in the city of Lodz (Poland) and it was a 2 day event.
In this short summary I will describe the main topics of the conference and I will point to some good talks I’ve seen.
The question I’d like to openly ask today is: why do you attend IT conferences? Is it for talks or is it for people? Let’s try to find out what the answer is 😉
After attending NDC Porto 2022, my first in-person conference for 4 years, I thought it would be nice to sum up the most talked-through topics. This will be a subjective summary and my feelings after attending ~20 sessions and talking to dozens of people. Let’s see what people talk about at programming conferences in 2022.
After 4 years of not attending an in-person IT conference, I finally did. I had a chance to attend NDC Porto 2022 conference, which took place from 27th until 29th of April 2022. How did it feel? What did people say about seeing each other in person again? Let’s find out 😉
![webpack code showing [cached] everywhere](https://blog.yumasoft.pl/wp-content/uploads/2021/11/Yumasoft_webpack_watch_cached_not_refreshing_bundles-1.png)
If you use webpack as your JavaScript bundler, you might have experienced an issue with webpack --watch not refreshing your bundles when modifying the source files. In this case, webpack’s output after changing the file is similar to the following one:
![Webpack output showing [cached]](https://blog.yumasoft.pl/wp-content/uploads/2021/11/2_WebpackWatchNotRefreshingCache-1024x87.png)
As you can see, there are some [cached] mentions there in a few places and no [code generated] statements at all. The effect is that your bundles are not rebuilt at all. In order to have them refreshed, you need to restart the building process, which takes time and makes your development flow painful. If you want to know how to solve that problem, read on 😉
As you know, at Yumasoft, we are proponents of remote work. We think that, as long as the work is done, our colleagues can work from any place they want.
The development of remote work has increased significantly in the recent months. How is that affecting the world and politics? Have governments already defined who a digital nomad is? How do countries see remote workers – are they welcome or not? What about visa problems for digital nomads – is it being solved, or is still kept in the gray area? 😉
In today’s essay, I’m trying to answer these questions and make some predictions on how the future of remote work will look like.
Have you ever heard about TypeScript types narrowing? Have you ever seen such an error in your TypeScript code:
Even tough, you really knew that the name property exists on the person object? How did you solve this problem? Did you cast the variable to the expected type?
If the answer to at least one of those questions is yes, you might read on. There are better ways of determining the type of local variable in TypeScript. What’s more, TS compiler does a lot of stuff for us by leveraging types narrowing. In this article, we are going to see how it works and how it can be useful 🙂
Some time ago we talked about 7 reasons to start using Test Driven Development. As soon as you learn it and start practicing it on a daily basis, it might be tempting to always be TDDing. However, TDD is not always a good fit. There are some cases when it might not be worth using TDD. Let’s explore them today 🙂
If you’re thinking about working remotely as a digital nomad, Yumasoft is one of the companies allowing that. We leverage remote work to make the most of it, also allowing our employees to travel.
However, as with everything, being a digital nomad has its dark sides. In today’s article, I’m exploring the most annoying digital nomads problems. Read on to be well-prepared for this lifestyle before you decide to take it on! 😉
Why should you start doing Test Driven Development (TDD) today? What are the benefits of TDD, and how can it help the developers and business? Let’s explore 7 reasons everyone should be TDD-ing 🙂
