OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs.

If you’ve ever argued with your team about the way your JSON responses should be formatted, JSON API can be your anti-bikeshedding tool.

By following shared conventions, you can increase productivity, take advantage of generalized tooling, and focus on what matters: your application.

Clients built around JSON API are able to take advantage of its features around efficiently caching responses, sometimes eliminating network requests entirely

Podcasts sind wie maßgeschneidertes Radio: Der Zuhörer stellt sich sein individuelles Programm zusammen. Das Angebot reicht vom dicken journalistischen Brett über Hörspiele bis zum netten Geplauder.

For a better understanding of the CompletionStage API, let's look at 20 examples of CompletableFuture in action, both synchronously and asynchronously.

we can figure out how to use our brains more effectively by building our own latticework of mental models.

This is a book about JavaScript, programming, and the wonders of the digital. You can read it online here

RIG is a scalable, open source gateway to your microservices. It solves the problem of connection state (which users are online currently, with which devices), which allows your microservices to be stateless. Pushing arbitrary messages to all connected front-ends of a specific user becomes as easy as publishing a message to a Kafka topic.

The key takeaway, for both physical and digital spaces is that we need to be disciplined and make deleting and organizing code a regular priority. Ignoring clutter only compounds it and makes a seemingly intractable problem even worse. Armed with a simple set of rules and making an effort is worth it. When you KonMari your code, you can transform frustration into joy.

SOAP and REST protocols have a couple of primary differences. Learn the benefits of REST over SOAP, as well as the (less common) benefits of SOAP over REST.

In other words, any authentication your application requires can be bypassed by a user with local privileges to the machine on which the data is stored. Therefore, it’s recommended not to store any sensitive information in local storage.

Binder: an awesome tool for hosting Jupyter notebooks

Sekundarstufe 1

Die neue Haptik eines alten Mediums: der Roman 'S.' von J. J. Abrams und Doug Dorst oder das 'Schiff des Theseus' als Spiel mit der Wirklichkeit

21 Settings to change in Windows 10 to to Reclaim Your Privacy (2017 Guide) - Fall Creator Update You’ve been told over and over that Windows 10 is the best thing since MS-DOS 5, and you’ve finally broken down and updated your PC from Windows 8. I have to admit that the interface and overall ... Read more

Charl Botha has a useful video on rewriting Git history with Magit. Botha gives three examples:

1. Changing the commit message on any old commit
2. Squashing two or more commits into one
3. Splitting a commit into two or more separate commits

There is a nice little utility well hidden in JDK bundles. jinfo is a command-line utility to harvest configuration information from a running Java process. The interesting part however, is that with the -flag option, the jinfo utility can dynamically adjust the value of certain Java VM flags for the specified Java process

One of the most important (and confusing) git features in my new job was rebasing. Looking back now, the worst part was not finding a clear beginner's guide. So for the past me, and any future devs like the past me, this intro is for you!

Although a lot has been written about Meltdown and Spectre since their announcement, I have not seen a good mid-level introduction to the vulnerabilities and mitigations. In this post I’m going to attempt to correct that by providing a gentle introduction to the hardware and software background required to understand the vulnerabilities, a discussion of the vulnerabilities themselves, as well as a discussion of the current mitigations.