Our top 5 topics in august by the tech practice circle

Summertime = vacation time. And we also need a well-deserved vacation. Nevertheless, some subjects were surfed and shared by our developers. This time, topics from the following areas are included: Open source, Rocket science, Tailwind, Chrome DevTools features, and Quality Assurance.

Javascript is rocket science after all! Working on complex systems, with endless lines of javascript and websites with millions of users a day, can be pretty exciting. If something goes wrong and a service is down for a while, that’s bad and not the user experience we want to provide for our users. Fortunately, though, we don’t do rocket science. So it was surprising for us to learn that the James Webb Space Telescope uses Javascript to control the telescope. Read the details in the article from the verge. It made me kind of proud that being a javascript developer can be rocket science.

Use Tailwind Without Tailwind In the article, Helmuth highlights the benefits of using tailwind, or what you can learn by taking a closer look. Tailwind is not part of our preferred tech stack, but it’s great to have the opportunity to look over the edge. As you can imagine, the reaction and attitude regarding Tailwind have been somewhat divergent. That’s the great thing about being able to disagree.

Chrome Devtools Recorder Recording user flows is a totally exciting feature. Not only can you record and replay flows to debug your application, but you can also export them and share them with others to track the exact error. This improves bug descriptions immensely. You can also export them with the respectively installed plugins in formats of common testing and performance tools. The individual recorded steps can of course be manipulated and additional ones added.

“uncurled” by Daniel Stenberg Daniel Sternberg writes about his experiences from over 30 years in the open source world. The inventor of Curl and open source enthusiast of course makes his work freely available and invites collaboration by using GitBook. Recommended reading for all who are interested in open source that wants to get an insight into his attitude, projects, what he thinks about funding, and how the open source world has changed over time.

5 Effective Steps to Align Testing with DevOps Our Quality Assurance team is already top notch and I read many things that are already implemented at Mercedes-Benz.io. Nevertheless, the article gives some interesting impulses on how to set up your QA team and your processes.

I would also like to draw your attention to the articles published on our blog by our esteemed colleagues.

Ricardo Brilhante has written an excellent text about AGILITY: IS FAILING AN OPTION? I don’t want to foreshadow how he answers this but we have “The Failure & Innovation Award” in our company for a reason.

We also have another part of the ARTICLE WRITING series, this time with a part about: FEEDBACK AND HOW WE INTEGRATED IT WITH A DEVELOPER </STYLE> Have a read and learn how to deal with feedback while writing and how we support that at Mercedes-Benz.io.

A heartfelt thank you to all who encourage discussion and distribute wisdom by sharing these stories. Hang loose and stay curious! Photo by Robert Bye on Unsplash.


View job openings

How to avoid a TL;DR reaction

This article is about how we can better get our messages across to readers in written form, why this is becoming increasingly difficult, and what we can do to avoid getting a tl;dr response to our written articles. 

Why am I writing about this?

I want us, developers, to write informative and readable articles.

So that we bring our knowledge and experiences into the world because we are awesome at our job and others can learn from it. Therefore, we need to be aware of the reading behavior of our potential readers and actively engage in writing readable texts, which has its challenges, especially in the technical field.

Where does the problem come from?

We live in an era where time is scarce, or we, as rushed characters, have the impression that time is short.

There are different reasons for this, but read the article by our colleague Hidayat: “prosochē – reflecting on attention.” Hidayat has looked at this in detail. You can experience how difficult it is for him to focus. 

In any case, we want to know what is coming, especially when we read articles on the internet. Often, however, we are denied this insight in advance, which means we miss the chance to get excited about the topic. Then you turn off and don’t read the article or scan frantically over the article for helpful information and possibly miss important parts.

On the other hand, it is also up to the writers who enjoy writing gushing articles or cannot formulate their statements shortly and crisply.

tl;dr explained

tl;dr Too long; didn’t read means that a contribution, be it an article, post, or similar, has been put into too many words and is therefore potentially not readable.

There are two uses of the term:

  • One is as a reaction to someone else’s post to indicate excessive verbosity. In this context, tl;dr is often used as a rude reaction.
  • On the other hand, to display an article’s summary and indicate that the contribution is too long.

The origin of tl;dr

The phrase was probably born on Reddit as a reaction to excessive posts. Like so many other things, it found its way from there to the entire internet.

The first entry in the Urban Dictionary dates back to 2008 and offers a wide variety of readings and variants of the phrase.

What can we improve when writing articles?

For not provoking the unwanted tl;dr reaction towards our articles, here are a few suggestions for action:

  1. A text formulated in understandable language is the basic prerequisite.
  2. It is important to pick up the reader initially to inspire and prepare them for what is to come. Then the reader will work his way through a dryly written, complicated, or just totally long article.
  3. The content should be structured and divided into consumable and varied bites.
  4. The same applies to the first sentence of each paragraph, which should be written as a summary of the paragraph so that the reader quickly knows which paragraphs or sections are of interest and can take a shortcut to the part of the article that is important to him.
  5. In general, texts should be reduced until only the essentials are formulated in them to avoid repetition.
  6. If a topic gets too long, you should decide to split the article. A series of articles also has further advantages.


Write your articles in an exciting and structured way, pay attention to your audience and take them on an exciting journey. Then you will get good reactions to your articles, and they will be valuable for the readers.

I hope this article doesn’t provoke any tl;dr or even ts;drtd;drtl;dc reactions from you. Anyways, feel free to let it out.

Bonus for all those who have read this far

TLDR Wikipedia has excellent examples summarized, these are also quite humorous. 

Image via Unsplash by Thiébaud Faix

Header image via Unsplash by Anastasia Zhenina