Analysis of Uber code of conduct

I would like to share my thoughts on code of conduct of Uber. I wanted to find interesting code of ethics, ethics policy or code of conduct and, sincerely, I struggled for a bit. As these papers are usually official and are legal documents, most of them seemed a little bit boring for me. They also felt very similar to each other even among IT companies. The most interesting which I could find was Ubers' Business conduct guide from November 2019. Its online version can be found here: There are several points which I noticed right away in this document: Visual design - this documents clearly had quite some time spent on it by designers. I also feel that quite a lot of resources were spent on it from both legal and design departments. Separation on small parts - pages have more pictures and less text in them than in most other documents that I found. Each page is not overflowed with text, so it feels

Wikipage article review - Low-code and no-code programming

Today I would like to give my opinion about a wiki article written by my fellow students about no-code and low-code programming. The article can be found under this link: To start, I would like to briefly tell why I chose this article to give my assessment. Although I have been working in IT for some time, I have never heard about these concepts and their use. I even mistakenly thought that low-code programming had something to do with low level programming. So it was very interesting and educative for me to read about these topics. What I liked in a introduction part, is the fact that in this article probable Estonian names for these concepts were given. In my opinion it is a nice habit for native speakers to have local naming for words as an alternative to English terms, this is why it could actually be a good idea to actually post this article on Wikipedia, so that these terms could be populated before these co

Supporting solution which I discovered for myself lately

I would like to share about one supporting solution in Microsoft Windows, which I started to use recently. The solution itself is pretty simple and many know about it. On the other hand it turned out that actually there are also so many people who do not know about it and discovering it could greatly help them. It is called a copy clipboard. The idea is very simple - when one wants needs to copy a data (text, pictures) from one place to another they usually select the data which you want to copy then paste it. And the process is repeated several times until all data is copied. Taking use of clipboard solves this problem - you can select any amount data you want to copy and then paste it accordingly. This could be especially needed when you have only one monitor or use a laptop as in this case switching between apps might be too much and separating a screen vertically might not be very convenient. But this supporting solution also has one negative point - it stores everything and user h

Implementing IT solution with waterfall - my personal example

This time I would like to provide an example of one IT project and how choosing wrong project management type can make everything overcomplicated. The example which I am going to provide took place in production factory where I was responsible for logistics. The story was simple - factory had its own applications developed by its software developers long time ago for their needs. However, there were several problems - the application was written using outdated technologies and there was only one software developer left who could maintain those programs. Overall company decided they should not have their own software and switch to some standard ERP solution. As a factory had its project managers and widely followed waterfall approach, they decided to continue using that approach on this project as well. There was no need to make a lot of development per se, as the company decided to use one of standard ERP solutions, mostly some modifications which seemed simple enough. The idea was t

Thoughts on "How to become a hacker"

After reading an article "How to become a hacker" [1], I had some thinking and want to share some thoughts about it and bring up some points I totally or partly agree and disagree (please note that hacker here is not the same as security hacker). Generally I really liked an article to widen an understanding of software development culture. On the other hand I would not advice to look at this article as some sort of dogma or laws, which have to followed by every software developer. Here are some points I found interesting to discuss after reading an article: In "Learn how to program" it was a surprise for me that discussion about specific programming languages was so huge. Eventually this discussion led to a good conclusion, that a hacker should have a variety of programming languages in his disposal, which I totally agree. On the other hand I do not think this has to be some predefined set of languages - this could be specific for everyone. Also although the article

Management in IT - two different management types

Today I will write about managers in IT industry and I would like to provide two examples. I thought that I could write about some famous real manager, but it would require to investigate a lot of time in it and still I will be speculating, as I will make my suggestions based on others opinion (which is not always fair). I also felt that my knowledge about famous managers is too week to provide any good information. So when I was thinking how to provide an example of problems in management in IT and two different management styles, I came to an idea that I can provide a good example actually based on a movie. This way I will not mislead about a real person and anyone can actually see a movie and see the problems in IT management. The movie I will be talkin about is called "The intern". Two types of managers[1] So in this movie we have two managers: Jules Ostin - a young and successful start-up owner. She is a  leader as a manager and tries to develop a company and bring every

The difference between the professional and an craftsman in software development

There are a lot of things which designate a professional in software development and IT in general. But there is one quality which in my humble opinion is very significant and by my personal observation is very common among professionals (and not only in IT) and beginners/amateurs often lack this quality and it is a systematic approach.  Systematic approach in different fields: Bug-fixing - craftsman tries to fix the bug itself and they are usually limited in their approach and in the ways they solves the problem. Professional fixes the issue. They have more knowledge about the reasons why bug can appear. Tools - craftsman tries to use the tools he is good with. When talking about IT, they usually do not like using new languages or technologies. Professional on the other hand often does not have such limit. They are capable of switching tools, because they understand the importance of using the correct tool for a correct situation. Writing code - craftsman writes code for a task and th