The product of those meetings are technological perspectives for Yumasoft and our clients in the coming months. In this article, I’d like to share some of the technologies we are going to look into in 2023.

AI

Artificial Intelligence is one of the technologies that’s been getting a lot of hype recently. Mostly thanks to OpenAI opening its GPT-3 playground and chat. This is all fun, but companies started looking into how to use this in their businesses. We are also looking on how to leverage these new findings in AI to make our customers’ businesses easier. We think that AI can make end users’ life smoother, allowing them to focus on what is the most important.

The fact is that in many applications we develop for our clients, there is a lot of data. We have quite rich experience in developing various document and quality management systems. The data in those systems can be generally classified as documents. The documents contain tons of information. This information is currently manually enriched with metadata by the end users. In AI, we see a huge potential to automate this part of people’s jobs. NLP is very promising in this manner. It is also worth looking into the technologies like Haystack and ML.NET. The goal is that the end users can focus on their most important tasks, i.e. providing business value to companies they work for. Manual work should be limited to supervision and “teaching” the AI algorithm to perform better.

At Yumasoft, one of the technologies we are looking at in 2023, is definitely Artificial Intelligence. We think it’s a way forward in most applications of software development, especially those including big data. What’s more, implementing AI is a great marketing leverage

Guide-based forms/wizards

Diving into AI, we got inspired by how algorithms can help users fill the data online. We think that instead of presenting the end user with an old-school form containing dozens of input fields, we can ask him/her a few relevant questions and prefill the form based on the answers.

Firstly, when performing an operation in the system, the user is asked several questions in a wizard/step-by-step guide form. Finally, our algorithm analyses the user’s answers and present the user with a prefilled HTML form. The user’s ultimate role is to verify the data. What’s more, if the form’s values are corrected manually by the user, the algorithm can learn from those editions to propose better values in the future.

At Yumasoft, we think it’s better to sometimes lead the users by hand, instead of presenting them with complex, old-school forms. We’ll be exploring such ideas in the coming months.

Minimal UIs

Nowadays, we are generally overstimulated. The marketing is omnipresent. Still remember these 3-weeks-long Black Friday sales? And the week-long Cyber Monday ones just after? We don’t want our applications to make people even more distracted in today’s world.

Similarly to simplifying the forms, we think creating KISS UIs is crucial. We can also call them the minimal UIs.

For instance: let’s assume we have a dashboard. The dashboard shows many things: new procedures, unread documents, some actions to take, people to call, notifications, company events… Usually, you as a user are only interested in what you actually need to do – now and today. The typical dashboard may contain too much information to easily spot the really important things requiring your immediate action. A solution to that could be presenting a simple indicator, like a colored, pulsating dot in a place that is central to the user:

The goal is to clearly see, in a single place, whether you have something to do for now or not. This is the only thing you’re really interested in.

Such an approach simplifies working with the system and saves a lot of users’ time. It is also based on showing as little information as possible to get the job done.

React

As per The State of JS 2021 survey, React is currently the most popular front-end framework on the market. We’ve already been working with it for a long time, but it seems that we will be exploring React even more. At the moment, React is our default choice for new projects.

SaaS

For some of our customers, we are still maintaining heavy desktop clients, including Windows applications. These programs require quite good hardware, as well as manual installation and maintenance. If the application we develop makes use of external desktop tools like Microsoft Office, this also adds the costs of licensing for every end user.

As a consequence, the businesses are expecting to move the software into the cloud. SaaS looks like the preferred model. Web apps only require a modern web browser and Internet access to be used. Additionally, end users don’t need to worry about licensing. Most of UI and other frameworks are licensed per application or per developer. This is a huge difference to desktop applications, where every end user must possess a proper license for the operating system and used programs.

Finally, it’s much easier to maintain SaaS-based systems. The updates are provided to everyone in a timely manner. It adds some complexity on the development and infrastructure, like keeping the backwards compatibility, but it seems to be worth the effort. Heavy clients are fading away and becoming unwanted in most use cases.

Cloud

Last but not least, at Yumasoft we are looking to more integration with cloud services like Microsoft Azure, AWS and Google Cloud. This goes together with betting on SaaS. Delegating the infrastructure to the cloud makes the maintenance much easier and smoother. Moreover, cloud computing services provide AI platforms and tools. The examples include Google’s Document AI or Azure Cognitive Search.

Of course, moving the data into the cloud comes with challenges. Data anonymization and security should be of a great concern here.

Summary

All of us – the technical teams as Yumasoft, our clients, their customers and finally – the end users – will have to go through a transformation which is happening right now. AI will bring a lot of improvements into most areas of our lives. Cloud computing will challenge all of us in terms of privacy and willingness to share our data with external companies. Will we trust them? Will we decide to go with the innovation flow, sometimes sacrificing our current beliefs?

We are so excited about the coming months. We look forward to 2023 and can’t wait to get our hands on these technologies!

The post Technologies We Are Looking At In 2023 appeared first on Yumasoft.

My conferences story

Back in 2015-2019, I used to attend conferences in person only. My first events included GET.NET in Łódź and WROC# in Wrocław. Then I attended .NET Developer Days in Warsaw two times in a row. This one was the first big-size programming conference I took part in.

Back then, I was a newbie junior programmer. I was also a bit shy to talk to people. Probably I had a huge impostor syndrome, as I thought everyone there was better in programming than me. I attended many sessions, even though I didn’t understand many technical aspects and never used them in real life.

I also always used to go to conferences and even meetups with someone I know (a colleague most of the time). If no one was going, I didn’t go alone. This didn’t help in becoming less shy and starting to talk to people I didn’t know ?‍

And then it happened. In 2018, I decided to go to InfoShare conference. Alone ? I still wasn’t very open to talk to anyone encountered, but I was a little braver. I talked to a few awesome speakers, including Michał Szafrański and Marek Jankowski. Those guys really were inspiring to me before, so it was an awesome feeling to talk to them face-to-face ?

InfoShare conference changed my life. It was another booster to make significant changes in my life and become a digital nomad. Several months later, I started working fully remotely for Yumasoft and traveling the world ?

There were some awesome guys like Michał Śliwiński speaking about a fully remote companies at that time already:

I also felt great after attending the NDC Porto 2022. After not seeing fellow programmers in person for more than 4 years, it was awesome to finally be more open and talk to many people at the conference. I was also alone this time.

Talks or people?

What can we take from my conferences’ story? As you read it, you can easily notice that the only things I remember are people. Either talking to one or two speakers or chatting with many people attending the event. That’s what I remember from the event. Technologies and tools come and go, but people stay. You stay connected with them on Twitter/Instagram. Think how nice it would be meeting them again at another conference by coincidence!

On the other hand, I remember almost nothing from Boiling Frogs 2021, which I attended online. That’s how it works for me.

I have to go back to the blog post or my notes to get something from it. This is also useful – that’s why I make notes. However, for me, this is not the real goal of attending a conference. All sessions are anyway recorded and in most cases available for free online after the conference. The community, interactions, Q&A sections and conference parties cannot be transferred to the online world and provide the same value. For me, it simply doesn’t work.

Conclusions

For me, conferences are the people. Not the talks.

However, I had to learn it throughout the years of attending several conferences, both offline and online. That’s why I wanted to share my story with you at the beginning of this article. To give you my perspective.

If you are about to take one thing from this article – please open yourself and talk more to people at the conferences. Try going to a conference alone, or if you go with someone – don’t stick with your fellows all the time. I know this is going out of your comfort zone. I still feel uncomfortable doing that, but I’m trying to improve little by little. If each of us makes a little effort, it will overall become much easier for everyone. Maybe next time I’m walking around the conference room getting stressed on selecting a random person to talk to, you’ll reach me and initiate the conversation? ?

The post Why Do You Attend IT Conferences – For Talks or For People? appeared first on Yumasoft.

.NET

This is going to be the longest section of this article ? I think it’s a bit specific to NDC Conference (“.NET” is the first one on the list of proposed topic for an NDC talk), but there was a lot about .NET. There were quite a few speakers either working for or associated with Microsoft.

I think the most discussed .NET topic was Blazor. There were many sessions discussing various aspect of the Blazor framework, its new features and development. MAUI was also mentioned several times.

Except that, .NET developers and speakers seems interested in issues related to the new versions of .NET (.NET 6/7) and generally this whole new ecosystem that’s being formed. Topics included gRPC/gRPC web, as well as Roslyn compiler possibilities.

Another important area of .NET was the multi-platform thing. It seems to be very important to the teams at Microsoft and contributors to related projects to make everything working on as many platforms as possible. Including desktops (Windows, Linux and Mac), web and mobile (Android and iOS). There were at least few multi-platform solutions discussed several times: Uno, Avalonia, Blazor and MAUI. All seem to be solving similar problems, but each has different entry costs and technologies used.

Software architecture

From software architecture topics, the most popular seemed to be everything around DDD. Not only the fully religious implementations of DDD were discussed, but also some of its simplified forms or just few concepts extracted from it.

It seems it’s all about understanding our end users better. I like it ?

Cloud

Possibilities of various cloud providers were discussed at almost every talk I attended. What I liked about that, is that it was not only Microsoft Azure discussed everywhere as it used to be few years ago ? Cloud is now seen more as a concept rather than concrete cloud providers’ possibilities.

While we still need to support on-premise deployments, cloud seems an inevitable way to go for many applications.

Web

WebAssembly and accessibility. There were the two topics discussed very often in terms of web technologies. Some sessions touched on React, but rather briefly. I even didn’t hear about JavaScript very often, which is actually weird ? TypeScript was also a topic, as well as some frontend testing techniques/frameworks.

UX

I attended two sessions about UX. This is quite interesting for me, as I think we can do much better in terms of usability of our software for the end users.

In general, I love the concept of designing and implementing the application from the user’s point of view. Maybe it sounds obvious, but it’s not always like that. Especially in corporations, when there are several layers between programmers and end users. Each layer adds its own filtering. This process makes the final solution sometimes far away from end users’ expectations.

Soft skills/team leadership

Not only technical stuff at programming conferences in 2022? Sure ?

I also enjoy team leadership and light-management topics. Although not many programmers I talked to especially love those talks. Except the ones who have actually managed people. There were, however, quite a few sessions on that, and I liked them. I think leadership is translatable to everyday life, not only work.

Conclusion

My general feeling after NDC Porto 2022 is that we all want to be focused on people. We want to take care of our end users, but also of ourselves ? The main message was to make everyone feel welcome in IT. Especially after the pandemic, which increased anxiety and reduced the importance of social aspects in software development. I think programming conferences in 2022 should cover these topics.

Technical stuff is important – without that we can’t make anything. However, we are all people, and we need to take care of ourselves first, so all of those awesome tools can be used effectively and to everyone’s satisfaction ?

The post What Do People Talk About At Programming Conferences In 2022? appeared first on Yumasoft.

My last conference was the online Boiling Frogs event, which I attended remotely from Indonesia. As you could read here, I was generally happy with the sessions, but something was missing. This missing piece was community. A real one. Physical. The community you can touch. And talk to ? I didn’t even realize how much I missed that. Until I attended #NDCPorto 2022.

Firstly, Porto is an awesome city for an in-person conference. It offers a mild climate, especially by the end of April. The temperatures were around 24 Celsius degrees during the day. It also does offer wine, of course ? It all means that you can enjoy a technical event during the day and still have some fun and socializing in the evening.

I lived in Porto for 2 weeks in September 2020 and really loved the city. It’s charming, not overwhelming and very appealing. It’s also a students’ city, so you can feel that young vibe – lot of street bars, people drinking beers or wine starting late afternoon until very late night.

All right, let’s get to the point. NDC. This great, first in-person conference I attended since 2018. I will not talk about the sessions here. I will talk about the people.

I tried to list the most-talked-through topics from this conference. The only real conclusion I can make, is that everyone I talked to, at some point said “It’s so great to be back in person”, or something very similar. The pandemic has taken a lot from us. Now it’s time to get it back.

I didn’t realize it, but the remote work time made me a little anxious with talking to people ? I’m not talking about pandemic, because I was fortunate enough to spend most of it in Indonesia (yes, Yumasoft is fine with you working from another continent!). Before I started working remotely, I used to be a Team Leader. It made me talk to so many people at the office every day. I always thought I’m rather extrovert than introvert. However, I was very curious to see how it is to interact with people again.

Before going to NDC Porto, I promised myself I will be starting chats with random people. Especially that I was going alone and didn’t know anyone there (except a few of the speakers). At first, I felt a bit stressed to just chit-chat to random people at the conference ? But then, after I started talking with the first 1 or 2 people, it felt great. It was so awesome to exchange opinions. Not only on coding, but also on pandemic, remote work and everything it changed in our lives.

There was also a great opening keynote by Scott Hanselman. He covered few very important topics related to pandemic times. Scott mentioned burnout, anxiety and onboarding issues while working remotely. Of course, he also proposed few solutions everyone can implement quite easily. Just watch it yourself.

During the conference, I also attended two socializing events. The first one was a diner with wine tasting after the 1^st conference day. It was an additional event everyone could sign up to, but was not officially part of the agenda. I’m very happy I went there, as it was another chance to meet some great people, including few of the conference speakers. On the 2^nd day of the conference, there was an official NDC Party. Very well organized, again allowing for socializing and exchanging views on various topics. Not only software ?

Conclusion

My conclusion is that the online events will never be a substitute for in-person ones. They are just different. I don’t feel the community and interactions at online events. There might be a chat, but it’s not the same.

I encourage everyone to attend in-person events from time to time. It doesn’t need to be a big in-person conference in a foreign country like NDC is (although I definitely recommend that!). Look for local meetups in your city or smaller conferences in your own country. Go there and overcome your fears and anxiety about talking to people. Just do it – talk to random people you don’t know. You will feel awesome, believe me ?

Attending a conference not only makes me wanting to try 10 new frameworks which I will forget about in a week. It makes me feel that we have an awesome programming community. That we are not alone in what we do. That others face the same pains we all have, like impostor syndrome or feeling stagnated at work. I got to know that other developers are not magicians and geeky coders who don’t use StackOverflow. Not every programmer’s job is his/her hobby. They are just normal people like me, with their own pains and fears. And that is awesome! ?

The post How Does Attending An In-person Conference Feel After The Pandemic? appeared first on Yumasoft.

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 ?

webpack watch cached files

We have struggled with this issue for quite some time. It starts with launching webpack with --watch option. Such build script can be defined in your package.json in the following or similar way:

The effect you would expect is for webpack to rebuild your bundles as soon as you make any change in the source code.

When the webpack watch cached issue occurs, the first change you make in a file is properly reloaded by webpack and looks similarly to that:

However, as soon as you change the file for the second time, the output looks less promising:

As soon as you see some of these [cached] things, it probably means that webpack cached something and did not generate new bundles. Especially if there are no [built] and [code generated] statements in the output. You notice that your files are not refreshed, so your last change is not reflected in JS bundles ?

Hotfix: disable webpack cache

The first hotfix solution – especially if you can’t easily find the cause – is to disable webpack cache completely. In order to do that, you should set cache to false in your webpack configuration file:

This will work, and webpack should now rebuild your bundles on every source change. However, it comes with a significant performance cost. Disabling the cache will make webpack actually rebuilding all your bundles on each change. This solution is actually a shortcut for restarting the build from scratch. Not what we really want ? Let’s see how to find the cause and solve webpack watch cached issue properly.

Wrong casing – the real cause of webpack watch cached issue

In our case, the problem turned out to basically be wrong casing when importing stuff.

The general advice is to find how given file you are modifying is entered into your webpack’s build flow. It can be imported or required directly. Maybe it’s used via webpack alias. I know these are quite general statements, so I’ll show you two examples.

Wrong casing in import

First, we had a problem of webpack watch not refreshing bundles after making changes in a single file. This file is named questionnaireCorrectTemplate.tsx. It exports a single React component called QuestionnaireCorrectTemplate.

In order to use this component, we imported it in another file in the following way:

Have you already noticed the problem? Note that the import contains the module name with capital letter: “./QuestionnaireCorrectTemplate”. As soon as we changed it to a small letter, so exactly as the questionnaireCorrectTemplate.tsx file’s name:

Everything started to magically work ? Since this change, webpack watch is properly rebuilding our bundles after changes in the affected file ?

Wrong casing in webpack alias

We had another issue with webpack not refreshing the bundles when we made changes in a Site.css file. This is a file in which we store custom CSS for our React app. The issue was very similar to the previous one. After starting webpack watch, the first modification of Site.css file triggered a proper rebuild of bundles:

However, all subsequent modifications to the Site.css file causes the webpack watch cached issue:

The reason was wrong casing again. However, this time we found out that the Site.css file was included as an alias in webpack configuration file:

I guess you can already see what is the problem ? The file was included as site.css, instead of Site.css. As soon as we changed this part of the webpack.config.js file to the one with proper casing:

Everything started to work correctly. Since this change, webpack watch correctly refreshes the bundles after each modification of Site.css file ?

Webpack watch cached – summary

I hope this article helps you solve your webpack watch refreshing issue ? Webpack is still kind of magical tool for me and it surprises me very often. Such issues can be really painful – that’s why I wanted to share our solution to this problem with you.

The general advice is to find how the problematic file is imported/required/added to webpack build flow. It’s very probably that you have the wrong casing somewhere. I hope it saves you some pain one day!

The post Webpack Watch Cached And Not Refreshing Bundles appeared first on Yumasoft.

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.

Remote work in 2021

First, let’s see a few statistics. We’ve already taken a brief look at them, but it was more related to digital nomads. Let’s see, what can we say about the current state of telework.

This is quite interesting. As we all know, COVID increased the number of remote workers significantly in 2020. Now we can see the employees in the United States are slowly, but steadily, going back to offices. Even though, in June 2021, when the economy has already been going back on track for quite some time, 35% of employees are remote workers. Before the pandemic, this was only 7%.

In addition to that, 30% of people work in hybrid mode (few days in the office and few days working from home). That all means that 65% of the US workforce is capable of doing their work remotely.

These people will still want to leverage workations and living in different places than their employers or clients are based. This is especially true for those employed in big cities, where costs of living are relatively high. Often, by moving to a lower-cost area, these people can save a lot of money.

We know the scale, but what about quality?

As you can see, with time passing, more employees and employers think remote work increases productivity.

This makes sense, because with time, companies are refining their telework policies, getting used to using proper communication tools and techniques etc.

Fine. Now it’s clear that the working out-of-office has got really popular in the last 2 years. Employers and employees were forced to switch to this working mode, which was far from ideal at the beginning. However, in the end, they made it better. Tools improved and work’s quality followed ?

Sovereign Individuals – the new social class of the digital age

It might be surprising to most of you, but this scenario (common telework, physical borders losing their meaning etc.) was predicted in a 1999-book The Sovereign Individual: Mastering the Transition to the Information Age. The authors provide a wide context on how societies change when a new era is coming. The modern era – information age – has been predicted to be the fastest-coming revolution in history. That’s exactly what we can see today, and this phenomenon is often called the digital era ?

One of the most significant predictions made by Sovereign Individual authors is that the nation states and governments, as we used to know them, will become obsolete and less significant in XXI century. As people can now easily vote with their feet, countries should start competing for digital workers, referred to as sovereign individuals.

I don’t want to go into too many details here. If you want to know more, I strongly recommend reading the book.

However, let’s try to see whether the governments really care about remote workers.

How are governments attracting remote workers?

Currently, in my view, governments can divided into 2 types from remote work point of view:

• completely ignoring the fact of digital workers’ existence and their troubles, keeping telework in the gray area
• seeing huge potential in remote workers and going ahead of their needs, welcoming and encouraging them to move into their countries and work remotely from there.

Still, most governments prefer the first, gray area option ?‍ Fortunately, there are more and more countries attracting digital nomads, offering tax incentives and easy visa processes. Let’s see a few of the most interesting examples in the next sections.

Georgia

Georgia (the country) has launched heir Remotely from Georgia program in the middle-2020 to attract digital workers from around the world. Citizens of 95 countries were allowed to enter the country and legally work remotely while in Georgia. All this happened during the global pandemic, when most countries in the world were closed to foreigners.

Would you ever think, that such a small country like Georgia proposes such a solution? It’s not common, even within the most popular digital nomad destinations, to give legal work permit in such an easy way. The only requirement was $2000 earnings per month for covering expenses while in the country.

What’s even more interesting, Georgia is offering very attractive tax rates for freelancers – you can pay as little as 1% tax on your income.

Portugal

Portugal has become a digital nomads’ hub in Europe in the last few months. It seems that the mild climate, quite affordable living costs and nomads-friendly attitude of government officials attracted a lot of digital nomads into the country.

In the recent interview, Portugal’s Minister of Labor and Social Security said:

Telework can be a ‘game changer’ if we profit from the advantages and reduce the disadvantages (…)

We consider Portugal one of the best places in the world for these digital nomads and remote workers to choose to live in, we want to attract them to Portugal.

Ana Mendes Godinho, Portugal’s Minister of Labor and Social Security, source

It is very nice to hear that some countries are welcoming digital nomads, a phrase that can’t often be heard in South-East Asia, for instance ?

EU citizens can easily travel to and work remotely from Portugal based on EU laws. However, what’s interesting is that Portugal is offering the D7 visa also to non-EU citizens. The requirement is to have a passive income equivalent to €7,620 per year. This allows anyone to live and work legally in Portugal, opening a business there or qualify for Portuguese citizenship after 5 years in the country.

Malta

Malta is another country which is very open to remote workers. They have launched an official program called Nomad Residence Permit. As long as you are employed by a foreign company, are a freelancer or owner of an offshore company and can work remotely, you qualify for the nomad permit. You must also have a gross monthly income of 2,700 EUR.

An interesting point here is that the digital nomads earning money remotely while in Malta are not subjected to personal income tax. You only need to pay the tax in the country where your income is generated (or where your tax residency is, but not in Malta).

Costa Rica

In August 2021, Costa Rica approved a law to introduce digital nomads visas. You need to earn at least $3000 per month (or $5000 per family). If your application is successful, you can stay in Costa Rica for up to a year, with a possibility to extend it for another year. Previously, a tourist visa allowed people from most countries to stay only for 90 days.

Similarly to Malta, digital nomad visa holders are exempt from paying local income tax in Costa Rica. Teleworkers can also easily open a bank account in the country.

Taiwan

Coming back to South-East Asia… As I already mentioned, countries in this region of the world still keep digital nomads mostly in gray area. However, there’s a tiny island which seems to have noticed the potential ?

This island country is Taiwan. Within their Gold Card program, foreigners can obtain resident visa and work permit in the country. The card allows you to work legally in Taiwan, but also work remotely for offshore clients or companies.

To be eligible for the Taiwanese Gold Card, your professional skills must be related to one of the following areas: Science and Technology, Economics, Education, Culture and Art, Sport, Finance, Law, or Architecture. As long as you can prove your skills in one of them (e.g. by presenting an academic thesis or work experience proof), the card should be given to you without bigger issues. As programmers, we are a perfect fit ?

Gold Card valid for 1 year costs around $160, while the one valid for 2 years costs around $200. You can also bring your spouse, who can also apply for residence and work permit in Taiwan. You will also be eligible for public healthcare after 6 months waiting period.

In addition to all that, for the first 3 years of living in Taiwan with Gold Card, half of your income up to around $110,000 will not be taxable. Sounds good, doesn’t it? ?

What about the most popular digital nomad destinations?

What’s surprising for me, most of the most popular digital nomads destinations and not doing their homework here. It seems they don’t see (or don’t want to see?) the potential in remote work and the changes that happened very quickly in the last few months.

A great example is Indonesia, the country which normally attracts a lot of teleworkers into its island Bali. They have recently announced to launch a digital nomad visa in the near future. However, the planned requirements are insane. You will have to deposit around $143,000 (or around $179,000 for family) in an Indonesian bank account in order to be eligible for the visa… ?‍

In my opinion, such countries will lose a lot in the years to come. Remote workers have a huge potential for bringing a lot of money into the country. The countries that realize that soon enough will be the winners.

The future of remote work

I think that more and more countries will realize the potential of telework. They will start defining who digital nomads are and how their income should be taxed. Easy-to-obtain work visas for remote workers will be more popular. As national borders are beginning to have much less meaning, countries will need to start competing for location-independent professionals. Digital workers will seek for a state in which the taxes they pay are proportional to the value they get.

Will the residency and associated benefits become a free market good? Will the governments be competing with each other, offering “a better residency package”? I guess we will see that in the years to come. For sure, COVID accelerated these movements a lot. Now the question is, which countries will realize that and enter the new “market” the fastest.

The post How Remote Work Is Changing The World appeared first on Yumasoft.

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 ?

TypeScript types narrowing – what is that?

One of the goals of TypeScript is to make writing JavaScript code better and more secure by adding the typing system. However, we don’t want the typing system to be problematic and making us to use the dirty haxes like all the time casting our variables explicitly, do we? ?

First, we need to understand that TypeScript does a lot of stuff in order to ensure we work with the most specific type as possible. Basically, if the exact type of local variable can be determined, TS compiler tries to do that.

Imagine such a function:

In vanilla JS, such code would of course compile. But in our case, TypeScript sees a problem:

The compiler is right here. Our parameter is either string or number, so the length property may not be available if someone passes a number.

You might have already been in such situations. What did you do? Well, sometimes when the code is more complex, and you just know that the variable contains the requested property, it might be tempting to cast:

Of course, we will satisfy the compiler here. But does that make our code any more safe than the previous version? Not at all.

In our example, based on the code we have written, TypeScript is not able to determine the exact type of variable. We can help it by using type guards. We will talk about them in details in a separate article. However, for now it’s enough to know that the language has some built-in type guards – one of them is typeof. Let’s use it in our function:

That’s cool, TS compiler doesn’t complain anymore. But how does it work? Our code is still accessing variable.length directly, there’s no casting there.

Notice what your IDE tells you when you hover your mouse over the variable in the first if branch after checking if the type is string:

and also what it tells you when hovering over variable in the else block:

Wow! The IDE magically knows what’s the exact type of our locally scoped variable! ?

This magic is called types narrowing. TypeScript compiler does many things to ensure that the type of local variable you work with is of the most specific type possible. It is based on the complex analysis of the source code, especially the code surrounding the place in which the local variable is used.

in keyword in types narrowing

Let’s take a look at this code now:

Let’s say we have a variable which may either be Employee or Manager:

In that place, TypeScript can’t say whether person is Employee or Manager.

Maybe you’ve used the in keyword for determining types before. Types narrowing also works with in keyword:

As you can see, TypeScript analyzed the flow, and it noticed that in the first if block we check whether the person object contains the employees property. If it does, the compiler known it must be Manager, not Employee. Cool, isn’t it? ?

Narrowing and equality operator

Another interesting application of TypeScript types narrowing is using the equality operator:

Notice how TypeScript determines the type of variables based on the === operator. If both parameters are equal, they must be both strings.

TypeScript types narrowing – summary

Narrowing in TypeScript is a very power feature of the language. I just showed you some simple examples, so you can grasp the idea and notice how much TS compiler does to ensure your type is the correct one.

If you’re interested, you can read much more about this in TypeScript docs. It’s however worth knowing how TypeScript compiler works and how you should properly check for types in your code. Remember that using any or explicit casting should be your last resort ?

The post How Does TypeScript Types Narrowing Work? appeared first on Yumasoft.

Prototypes

You may consider not doing TDD with prototypes. By prototype, I mean an app that will most probably be thrown away or completely changed very soon. It may be created when you are experimenting with some technology/framework or are just asked to conduct research on something.

TDD gives you a high code/flow coverage, which may need to be changed in case of prototype projects. If you are in such situation, consider resigning from TDD at this stage.

Short living apps

Similarly to prototypes, short living solutions might be the ones where TDD is not the best fit. It applies to one-time-use apps or scripts which are supposed to do one thing well and quickly.

Short living apps are the ones where you may consider not using Test Driven Development. I’d even argue whether you need any kind of tests for such programs. Testing such apps or even scripts may be art for art’s sake. If something is supposed to realize a given task without fireworks (like reusability, maintenance etc.), I wouldn’t bother with testing it. It’s better to focus on solving your current, short-lived problem than on practicing the profound TDD idea ?

Unclear requirements

One of the reasons not to use TDD might be unclear requirements. The idea of writing tests in Test Driven Development is to define the expected outcomes for predefined incomes. As we said in the previous article, Test Driven Development can help spot the edge cases and make the business requirements more close to the code. However, if you don’t have these requirements defined, TDD might be a waste of time (at this stage). If the requirements actually arrive or are completely changed, your significant set of tests will need to be changed or even removed.

MVP

If you’re creating an MVP, with very short time and budget, TDD might not be worth the struggle. It’s probably better to resign from using TDD in that case. You should rather focus on your product and the business value it needs to deliver. TDD might slow down the delivery time, which, in case of MVPs, can be critical. It’s better to deliver the minimum viable product without TDD than to not deliver it with TDD ?

However, remember to add some tests, even post-factum. MVPs have a high chance of survival, so you’d want your final product to be tested and testable. You need to find a good balance here, not to make your solution completely untestable when it’s ready for production use.

Tests writing beginner

If you are a total beginner in writing tests in general, Test Driven Development might not be the best approach to start with. You may consider not to use TDD at the beginning of your testing journey.

To make Test Driven Development effective, you should be able to write tests quickly and efficiently. Starting to learn software testing with Test Driven Development may make you feel overwhelmed and discouraged. If you’re a beginner, I suggest to first write some unit tests, get familiar with that and then try to learn Test Driven Development.

It would be great if you can find some smaller and well-defined task to start with TDD. If you don’t have such tasks, try solving one of the programming katas (e.g. this one) with TDD.

When not to use TDD – summary

Like everything, TDD is not a gold standard for every possible case. It should be used as often as possible, but not always. Remember to always weight the gains and losses from using Test Driven Development in a given project or application at a given time.

What’s your experience with Test Driven Development? Can you list any more cases where it’s not worth using it? Share your thoughts in the comments below!

The post When Not To Use TDD? appeared first on Yumasoft.

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! ?

Visas

When traveling full-time, visas can be a real pain. When living in your home country, you don’t think about that aspect of life at all. However, digital nomads who want to stay longer in a foreign country must apply for an appropriate visa first. What’s problematic is the permitted length of stay. In most Southeast Asian countries, which are very popular among remote workers, foreigners can stay in the country for up to one month. After that time passes, you need to either exit the country or apply for another, often expensive visa extension.

Because of that, there’s a common practice within digital nomads called a visa run. It basically means to leave a particular country by bus or plane for a day or two (sometimes even for just several hours!), only to go back and get another visa stamp in your passport ? Some countries are even trying to introduce mechanisms preventing visa runs. All this makes digital nomads life complicated, stressful and costly.

Taxes

One of the most frustrating digital nomads problems is taxation. In most countries in the world, if you stay for longer than 6 months, you should be paying taxes in the country you’re staying in. However, because remote work is still a gray area in most of the world, the taxes often cannot be technically paid by a foreigner.

The issue is that most of the world’s countries still have not defined what a remote work really is and how the taxation and visa rules relate to it. In effect, often you are not able to legally obtain a visa that gives you a tax ID, which is needed for paying taxes ?

Even if you finally get a tax ID in the country you live in, there are issues with double taxation. Assuming you have your company registered in your home country and are still paying taxes there, you might be taxed twice – both by your home country and your new residence country. In such case, digital nomads must analyze the double taxation agreements between the two countries, which are often hard to understand. Establishing your double taxation rules sometimes requires consulting a local tax advisor, which adds up to the cost of your trip.

Apartments not suitable for remote work

For me, this is a very annoying point! If I were to choose one of the digital nomads problems I could magically solve, I would vote for apartments not adjusted for working. Sometimes even such a would-seem-irrelevant thing like a bad table or chair not suitable for working with a laptop can be a disaster for your stay. Especially if you book a flat for a longer period.

What I hate the most are these IKEA chairs, popular in the whole world ?:

I can’t even express how much I do hate this chair ? Maybe they look fancy, but try sitting on it and working with laptop for 8 hours… The back of this chair is very flexible/elastic, so it is impossible to sit straight on it. So I am publicly asking all apartments owners – please stop buying IKEA FANBYN (and similar) chairs! ?

Adding to that too low/too high tables, poor WiFi quality and not enough light, the apartment you book for a few months can become your remote work prison!

Internet

Digital nomads need constant Internet access. While in most cities it is not a problem, when you want to travel to a bit more remote areas it becomes painful. WiFi is often unreliable, and mobile networks also often can’t be counted on.

I remember joining our daily meeting with Yumasoft team in late 2019, when I was living in a remote part of Bali, Indonesia. Amed is a beautiful place, with rice fields and volcano views, but the Internet really sucks there ? On a video call, I couldn’t use my camera of course. Even with only voice, I remember me saying something and the guys in Poland hearing it after 20-30 seconds. It was fun, but also a bit of stress.

Time zones

Another challenge digital nomads face on a daily basis are time zones. Working from different continents than your colleagues requires you to adjust to the majority of the team’s timezone. Having my team based in Europe while living in Asia, I had to start working around noon and finish work around 8PM.

This becomes even more problematic if most of your team is based in the same place all the time. This has been my case for almost 3 years at Yumasoft. Fortunately, we are quite flexible with working hours, and we try to use asynchronous communication as much as we can. Nevertheless, if you want to become a digital nomad, be prepared that time zones will most probably not be your best friends ? Of course, remember to always check the timezone in the country you are going to travel to!

Making friends/socializing

Many digital nomads problems are related to social aspects of life. Working remotely, it might be hard to make new friends. If you are not an outgoing person or maybe an introvert (as many programmers are), you will not have the safe physical office space to expose you to some social interactions.

Getting trapped at your apartment may make you more isolated than you have ever been before. The solution is to sometimes go out to a café or a coworking space. You can always meet like-minded people there. However, for introverts, it may come at a price.

The same applies to the team you work at. If some of your teammates work at the office, you may feel “out of sync”. Some jokes and stories are always only told in the office, and you will not hear them. It might make you feel “out of the team” at some point.

That is why, at Yumasoft we try to organize remote work properly. It is very important that everyone feels part of the team. However, be prepared that it may not work ideally in every company you may work for.

Work-traveling balance

This point is similar to work-life balance, but what work takes from us in case of digital nomads is not life, but traveling ?

Imagine you are living on an exotic island in Thailand. The weather is great, there are some stunning beaches around you have not visited yet – you arrived just 3 days ago. However, you must finish this important task… Maybe you can go on Saturday? Not this time – you must visit the local immigration office for your visa extension.

That is what I mean by work-traveling balance. Being in exotic and interesting places makes you wanting to explore them, not work ? Going further – sometimes you cannot go to some place, because it is not suitable for remote work (poor Internet etc.). It makes you resign from visiting some cool places around, because you need to work. Even if they are at your fingertips. Unfortunately, being a digital nomad is not a constant holiday ?

Not being understood by others

After you start a digital nomad lifestyle, you will notice that no one really understands what you do. Your friends and family members will soon be introducing you as “the guy who travels”. Most of your family will have no idea what you actually do at work. They will say: “she does something on her laptop”.

Unfortunately, most people will also not understand your decision to leave home and constantly travel. This is not the lifestyle most people can and choose to have. Be prepared for not being understood by people who surrounded you until this moment. On the positive side, when leading a digital nomad lifestyle, you will quickly meet fellow nomads who will understand you very well ?

Medical insurance

Last but not least – medical insurance. When traveling the world, it can be one of the most costs-generating digital nomads problems. You may still be covered by a public healthcare in your home country, but in most of the countries in the world you are not covered for health problems at local hospitals. If something happens, you have to pay even for using local public healthcare.

That is why digital nomads must but a worldwide medical insurance. Most of the typical travel insurances will not work, because they are usually time-limited. It means that you cannot travel for few years on a travel insurance. You should buy a nomad medical insurance.

Prices for good medical insurance for digital nomads start from 500 USD per year. If you suffer from chronic diseases, it will be even more expensive. You should also read the insurance policy very carefully to be sure it will cover your medical expenses in every case. Especially now, during COVID-19 pandemic.

Digital nomads problems – summary

As you can see, nomadic lifestyle is not perfect – it has its drawbacks as any other lifestyle ? For me, after almost 3 years of working remotely and traveling, I can surely say that the benefits of being a digital nomad outweigh all of these problems. But it is important that you are prepared for them, so they do not surprise you when you get on the road.

Of course, it is always best to check it yourself! There are now many more companies like Yumasoft that allow their employees to work remotely. Just give it a try and see for yourself! ?

The post Most Annoying Digital Nomads Problems appeared first on Yumasoft.

Moving design into code

With test driven development, you create your tests before writing production code*.

Having that in mind, one of the benefits of using TDD is that you need to move your design requirements into code before you even write a single line of business logic.

It means that you need to spend time thinking about good names for your tests. I often create empty tests straightaway after staring to work on a task. Spending time to create well-named test methods can help you quickly spot missing parts in the design.

*By production code I mean the actual business logic except the tests’ code. This is only to differentiate here, but I personally consider my tests part of the production code in real life. Tests are as important as all the code.

Finding edge cases

Going further, if you create many empty tests with well-thought names, you will surely find many edge cases. Thanks to test driven development, you’ll verify the business requirements by your code without writing even a single line of it. Discovering edge cases and boundary conditions will let you clarify the requirements or even change/adjust them before any production code is written ?

Structuring your code beforehand

You’ll see that TDD forces you to think about the code you’re about to write beforehand. You’re going to think about production code to-be-written: how and where to add it, what methods, parameters and classes are needed. Thanks to that, you can quickly notice that maybe the place you’d normally place the new code in is not the best choice. Maybe it requires too much changing instead of modifying.

Such approach leads to taking and rethinking architectural and structural decisions before writing a single line of production code. In the end, it saves you a lot of time. Without TDD, you’d probably just add this new code where you thought it’s appropriate and struggle to refactor it later. And refactoring without tests is dangerous ?

Allowing to refactor

Test driven development is based on red-green-refactor cycle. As soon as your test is green, you can safely (for sure much more safely than without tests, especially if you combine TDD with mutation testing) refactor the code you’ve just written.

In the end, the quality of your code is much higher than it would be without tests. You don’t feel the fear of refactoring, which is a common blocker for improving code quality in legacy systems.

Making implementation very easy

When you move from red to green phases of TDD, it’s time for implementation. From my experience, writing production code that satisfies TDD-produced tests is very easy.

I find it much easier than writing code not covered by TDD-based tests. You exactly know what to do and which tests must pass. Thanks to that, your implementation is minimal – it should only make the test(s) green.

Creating current code documentation

Implementing a new feature with test driven development will leave you with a comprehensive set of tests. From my experience, I write few times more tests with TDD than in a “traditional” tests-after-code mode.

As a nice side effect, you’re building and growing the only possible, current documentation of your code – set of your tests. Only tests can tell you the truth about your code. It can’t be achieved with any other kind of documentation. Notice one more advantage – you’re creating documentation… without writing any documentation! ?

Current, well-named tests are very helpful not only for developers, but also for the so-called business people.

Spotting architectural problems

Last but not least, test driven development helps to solve application’s architectural problems. Tests should be relatively easy to write. If the test is hard to write before production code exists, it might mean that the architecture of your solution is wrong. There’s a problem somewhere that should be addressed.

That’s why it’s very important to start working with TDD as early as possible in your project. There might be some cases where TDD it not suitable (maybe I’ll write a separate article about it ?), but in quite mature and stable projects, it should be a gold standard. Altering the architecture is much easier early in the project.

The post 7 Reasons To Start Doing Test Driven Development appeared first on Yumasoft.