Our top 5 topics in November by the tech practice circle

This month, the developers had stimulating conversations on MS Teams, sharing their opinions.

Sticky Scroll

Many of our frontend developers at MB.io use Visual Studio Code. The VS Code team has released a new setting that helps you keep track of your file. Sticky Scroll, this feature shows the class/function you are currently working on at the top of the editor. Just enable it in the settings: “editor.stickyScroll.enabled”. Watch the short video and let it explain the behavior.

The Microsoft Edge Dev Tools extension for VS Code

The title of this article was so catchy that it spoke directly to me: “The Microsoft Edge Dev Tools extension for VS Code is so awesome that I’m ditching Chrome for web development”. What do you think? Will you try the visual studio code extension?

State of frontend 2022

Over the past two years, the IT industry has been undergoing major changes, especially in the area of frontend development. In this report, 3703 frontend professionals from 125 countries and 19 frontend experts were surveyed to get an accurate overview of current trends and the future of frontend. The goal is to provide insights on topics such as technologies, practices, and working conditions. This survey is a good starting point to discuss the insights in the team, to read trends for ourselves and to find out what we want to focus on in the future.

100 Seconds of Code

Curiosity and the will to learn something new every day is in the genes of us as developers. Especially easy to consume are the contents of this playlist: 100 Seconds of Code. Watch one of the clips every day and you will have 133 days of fresh input. The basics and commands for tools, technology or frameworks are covered.

Practical Accessibility a online video course

A self-paced, get-right-down-to-it online video course for web designers and developers who want to start creating more accessible websites and applications today. The course is by Sara Soueidan an inclusive design engineer, author, speaker, and trainer. Because accessibility is important to us at Mercedes-Benz.io, one of our A11y gurus in our company will definitely be watching the course.


Experimenting and trying out innovative new tools and services is vital in the life of a developer. This git links collection gives you the opportunity to browse what’s out there and especially which is free to use for developers. From major cloud providers, to source code repos, web hosting, analytics, to game development, you name it. What will you try next?

Thanks to all who share their knowledge in our company in this way and use our communities to exchange ideas. Stay curious!


View job openings

Photo by Tim Stief on Unsplash

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