Writing code can be fun, but it can also be annoying. Especially when you feel like you’re doing the same thing over and over again. Fortunately, there is a tool that can save us this unnecessary effort and also make the code easier to read!
“Why is the banana crooked?” That’s a good question that comes up again and again. We want to avoid such ambiguities, recurring questions and assumptions in software projects at all costs. When we make a decision, we want it to be easy to understand later on. But how do we do that? How can we record decisions and what do we need to bear in mind?
If you want to communicate with other APIs, you can hardly avoid OAuth 2.0 when it comes to security. We explain the most important terms and show when and how OAuth should be used.
The API is ready, the monitoring is running. But who wants to spend all day looking at the diagrams generated and checking the status of the system? What do we need now? → An alerting system!
Sketchnotes – the combination of scribbles and text – are an effective tool for keeping content in mind during architecture sessions and conferences, for example.
By running our software through the so-called test pyramid, it is put through its paces. This is how different types of tests build on each other in software development.