Skip to main content

Lukashenko takes Minsk off High Tech Map

A few years ago I have created a company in Belarussian High Tech Park.  I found the city’s technology scene vibrant and the favorable tax structure created for the High Tech Park a nice pro business reform.  I have recommended Minsk as a viable location for an Eastern European software team.  Since August 9th 2020 my recommendation is changing: Mr. Lukashenko’s regime has kidnapped people off the streets, turned off the internet for several days and started putting people in jail for political reasons.  It is now risky to create or keep your R&D office in Minsk and I would not recommend it. 

AP Photo - Belarus Arrests

In my blog I try to keep focus on technology and keep politics out of it.  Regardless of my beliefs on Mr. Lukashenko’s government, I am going to keep this post strictly to risks that the current regime has posed to anyone doing business with Belarus since the troublesome election on August 9th.  I sincerely hope that companies which are affected by the police brutality now get their personnel out of Belarus as soon as possible.  I recommend that all other tech companies start moving their personnel out of Belarus into neighboring states before their leadership, engineers, or anyone else is taken in by the police for expressing dissenting views.

High Tech Personnel Arrests

Belarus police recently has put in jail 4 employees of PandaDoc on charges of theft that the company itself has denied.  I am not a Belorussian attorney, but the political nature of these arrests is obvious.  How does the state arrest an employee on charges of theft, when the employer and the auditors are denying any such theft?  It’s obvious that the charges are an intimidation tactic, due to the fact that the founder of the company spoke out against the brutal police crackdown by the current regime.  The regime has chosen to retaliate for expressing political dissent by attempting to damage their business.

Internet Turned Off

After the election the regime has chosen to turn off the internet for several days.  The reason is obvious: the internet is one medium that Mr. Lukashenko has a tough time controlling.  They decided to shut down large portions of communication and in some places just kill the connectivity altogether.

When the regime has decided to use this tactic it disrupts people trying to get business done.  Can you imagine if you have an engineering team in Minsk who is getting ready for an important release on August 10th or prepping a customer demo on Monday only to find out that they are not able to deliver their project because the current President is threatened by what the people of Belarus can post or see on the web?!  From a business perspective its unacceptable!  

There are many humanitarian issues in Belarus right now: beatings, torture, vote falsification and political prisoners. There are plenty of resources covering the humanitarian catastrophe which is happening in the middle of Europe, so I am keeping my message only to the technical and business issues.

To our colleagues in Belarus: please stay safe and please look for a way to get out.  Thankfully your business is mostly dependent on your skills and not on heavy machinery.  Most of you can move with nothing but one laptop.  You can serve your customers more reliably in Latvia, Poland or anywhere else where the government relies on the voice of reason rather than brutality.

There is hope that possibly the regime will change in Belarus and the people will get the government that listens instead of beats them up.  I hope that the current government coms to its senses before they completely destroy Belarus.



Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!

SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…