Who gets the credit?


On Twitter, there is a “Like” button. What is it for? if one clicks it, do they show appreciation for the content of what has been tweeted or for the action of having tweeted something?
I believe that it is there for the content and I click it to show I appreciate what has been written.

On Twitter there is also a “Retweet” button. What is it for?
I believe it is used to share tweets that one found interesting and they want to share it with their fellow followers. At least that is how I use it.

Now, what does it mean if you like a retweet? This is how I see it: you like the content that has been retweeted. Right? Good. That means that all attention will go to the re-tweeter and very little to the original? (that is assuming the re-tweeter has a lot more followers that the initial author, of course)
Then what about the initial author of the retweeted tweet? Do they not deserve appreciation for having shared a piece of interesting information? Then instead of “liking” the retweet, why not like the original? you click on the retweet anyway to read it. Or do you? And to quote a famous meme on the internet: “Do you mean to tell me…” that you do not read the content of the retweet? you just like and/or retweet after you only read the title? That is even worse than not crediting the author.


[inline] Styling in React – #ReactEurope


I will begin with 5 minute refresh on CSS.

The next 10-12 minutes will be about how and why to apply inline styles in React. I will share my ups and downs, and what I learned – like sometimes it really is necessary to put the styles inline.
I am dedicating part of the talk for the style attribute: what is is and how is/should it be used – focusing on the fact that it accepts a JavaScript object rather then a a CSS string; prefixes for different browsers are also included here.

The last past of the talk is about a more modern approach: styled components. I am sharing this part as a JS alternative to inline styling.

Bank Holiday vs. Holiday


A bank holiday is a colloquial term for a public holiday in the United Kingdom, some Commonwealth countries, Hong Kong and the Republic of Ireland.

– Wikipedia

A bank holiday is a day in which banks (and maybe other businesses) are closed. There are, however days that banks and businesses are closed that are not bank holidays: Christmas Day, Good Friday.

So people of the world if your country does not designate a special day for the banks to be off, then it is not a bank holiday!

So, why do us, the rest of the world refer to any holiday as “bank holiday”?

Short answer: Because we are ignorant.

Long answer: We are ignorant and we are too lazy to do our research. We just use words and expressions we hear around without knowing their meaning. We just assume we can figure it out from the context. Surprise: we can not! Why? because you can not possibly match the context 100%.

Should a developer care about the business?


Yesterday I was in a meeting with my team lead (backend dev), another backend dev, a business analyst and a designer. The designer kept asking questions about the admin panel of the app, about the technical limitations, what is out-of-the box and what not so that she can design a solution that will not be too creative for our limitations.

And after the team lead answered all her questions and the meeting is over, the other backend says (with an annoyed voice):

“Why should I, as a programmer, care about the business. Why do I need to know about all of this stuff. I know PHP and that’s it. How can we create high performance if I care about the business”

At the time it just seemed odd to hear that from a programmer (and a backend, no less), but I said nothing. I just paused. Now, a day later, after I processed the words I ask: How can you not care about the business? How can you provide the client with the best possible solution if you do not know and understand his business, the roles, the client types, the products, the categories – everything that is business related? How?

How to make a developer feel unwelcome


It’s December 15th 2017 and I am happily starting a new job that promises a lot.

I arrive at the office around 11am. They usually start at 10, but since here no one really comes in time…

As I said, I arrive around 11am and I go straight to the HR department (because HR is the only contact I have). There I am invited to sit at a desk until the IT guys will bring my laptop because they do not know what my project is going to be nor what team I am part of. I know I am frontend and I will work with Magento2. 2 minutes later the IT guy comes and says:

“Let’s go to the other floor. There’s where you’ll live”.

We arrive at my desk, I see a laptop (with a nasty scratch on the exterior of the lid). It looks kind of old to me, but I think maybe I should not complain from the first 30 minutes. The It guys helps me connect to the wi-fi and hands me and envelope saying: and this is the envelope. He sounded as if I knew what that envelope is. Again, I don’t ask about it, thinking i will figure it out, or maybe it is self explanatory. Then he leaves.


I am John and I solved a problem


I am John, I work for a company whose name I can not say and we have this client, but I am not allowed to mention their name, and we had this problem for which I cannot give specifics but I am here to tell you about how we implemented the solution.

Sounds familiar? Maybe, maybe not.

Well, for me this is the thing I hear at almost every conference I attend. Truth be told, I can understand that one can not give specifics, but one should also not start a topic meant to teach others unless you are willing to go into specifics.

I have the feeling that these “Johns” want to create the impression that they encountered a million problems and found at least one solution for each.

But how do I know that the problem was not created due to a faulty logic? How do we (the attendees) know if maybe the requirement was stated or understood in the wrong way. Usually that is where the problem stands. And it is best to ask all the questions before starting to work.

Anyhow, there are speakers for whom I would travel half the planet, but there are also others that have fancy job titles and do not have a clue of what’s going on in the dev world.

So, conference organizers: please, please I would rather see the same 3 speakers in all the conferences than having different poorly prepared speakers, just for the sake of not repeating.

And for the speakers: Please speak for the sake of sharing and making the community better not for the money. Remember why you became a programmer! If money is the first answer, you are doing it wrong.

Petr (or how to lose a great developer in under 3 months)


Once upon a time, in April this year, I was moving to a new company. It looked really good especially since they said that they have “Nordic (Danish) management”. All good until end on July when I had some well-deserved vacation.

In mid-July this new developer Petr Čaněk joined my project as developer. I knew nothing about him even though something was a bit off in the way he talked (choice of expressions, tone, attitude, frequency of words per minute, lack of article usage…), but hey! we are all unique and as long as the company decided to bring him in I was convinced that they made the best decision, so I welcomed him to the team, made sure that he had access everywhere he needed and then left for vacation.

After I came back, we had a meeting with the client and out project manager could not join but we (PM, team and client) had an agreement that I would be his stand-in (not only that one time but every time he would not be there). For some reason Petr felt the need to say – out loud – that this team had no project manager and because of that reason we are chaotic. I immediately responded that this statement is not true. We do have a project manager, but since he is not here, I am his stand-in, as agreed. I asked him if I could be of any help in this role, and when he said “no” I suggested we should continue the meeting. A few days later I receive a call from my line manager (in short: a person responsible with the relationship between me and the company) saying that Petr complained to him about me not doing my job – there were over 10 untouched tasks in my backlog. I cleared the problem (or at least  thought I did) as it was a misunderstanding that lead to so many tasks being created. My line manager also informed me that out PM would be changed (the reason was that the new PM already has the rest of this client’s projects).

After this things only went down.


Colour of the year 2018


If you haven’t decorated you house yet or at least the Christmas Tree I (or better: Pantone) give you colour of the year 2018: Ultra Violet!.

The consistent Petr (part 2)


In our project we have this Sentry integration that would let us know when something goes sideways (I am sure most devs know what I am talking about).

About a moth ago (all of devs and dev-ops) have missed one notification (we were all in a meeting an ignored the email) and live site was unusable.

Ever since I made a rule (for myself) to put the errors in a common Slack channel for all the devs to see. All good, no one was bugged.

A few days ago, Petr makes this announcement:

“Note – it seems that current errors from production are maybe false-positive and they are not affecting user. Sentry integration will be updated shortly.
Second note – even these errors may be false, we will still take a look into them.”

Today I see tow dozen errors in my email  and I notify the devs, that maybe something went wrong, as there are too many different ones. If they are nothing than only 5 mins of our lives were lost.

To my notification I get this from Petr:

Yes, the FE errors on production were mentioned on stand-up and also in #frontend channel. They can be false positive, due to complications with Sentry integration.

There was no mention of said errors in any of the stand-ups this week or past week.

The consistent Petr (part 1)


This morning, when I got into the office, I was surprised by my tester who said that none of the bugs I’ve put in for testing are fixed. Imagine my amazement when I checked the bug-branch I was working on and the testing-branch and they had very different code! So I go to Petr and:

Me: hey Petr, did you get any conflicts when merging the bug-branch into the testing-branch
Petr: Yes. But I fixed them. I kept the testing-branch code
Me: You should have kept the bug-branch code as it was the newest one (and I added it to fix some bugs reported on the testing-branch)
Petr: Yes, yes. That is the one I used.

Half of the day has passed since and we still have different versions of code even though the bug-branch was merged into the testing-branch…Petr is on it (fixing).