Dear JavaScript,
Jamie Kyle

You fail to mention/link the reddit posts that you reference. This is the web man, give us some links to verify your claims that those threads were just unproductive waste of time. Without giving the links you are wasting my time now to validate your claims.

But then I can believe to an extend what you are saying because, I criticised an open source project recently in rather harsh voice in the issues (all valid issues) myself. I admit it just stressed me out how badly this piece of software was written. Code style, comments, software patterns. I tried to read the code and to understand (like you suggest) what lead to this design decision. And then I see that the decision was stupid. Like as an software design decision. Made out of lack of grasp of good API design. Which is hard, I admit. I fail myself several times at defining a good, small API surface for my own projects. And what makes a good API is also up for heated discussions. General opinion is that Microsoft makes bad APIs. Which is not always the case (WinRT with a few exceptions never fixed until today). But they are consistent. They support their old, bad API for decades. Not so the open source world. The idea is since its open source, if the API breaks for you, then you can just compile the source to your liking if you want. But I can understand people complaining about.

Yet, “you get what you pay” for is still valid. We should be grateful for the time we all save since somebody else spent his time on something we would never be able to pull of our self and then giving it away for free. But there comes also responsibility with it. With more and more people using your pieces of code you can no longer reign as the sole Emperor over your source kingdom.

Happy people usually don’t give positive feedback. If there would be a “Praise” tab on GitHub next to the “Issues” tab maybe the tone would shift. And maintainers would also feel the positive feedback and not only the issues with their hard work.

And that brings me to another point I wondered. The company you work for only offers people the “like” option and this is basically the currency of the platform you develop. That is also literally the currency of the platform that ultimately ends up in your very own pockets each month. On the facebook platform people can “like” articles of beauty and reason as well as the ones spitting hate. Why facebook never introduced the “Don’t like” button is something you have to ask yourself. Your morals presented here are perverted by your own employer. How can you justify to work for them? Their whole business model is highly immoral and everybody has a price.

Every coder thinks his code is the best. Although my own code, written half a year ago already looks like shit to me now. But when I see bad code (ng, ng2) I just can’t help myself but rant. But I also greatly admire and praise good code.

Also Medium, why isn’t there an additional response box at the bottom of all responses? This site is a #UXmess. But I’ll save that for a very own rant story later :)

Like what you read? Give philk a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.