Why I use Linux

I’m not sure whether I wrote an article like this before. Either way, the Why I use Linux Project is a nice opportunity to write (again?) about this topic. History First of all, some history. I was introduced to “the other operating system” in grade 11 by a close friend of mine. At the time, I didn’t know a thing about computers. I just graduated middle school (“Realschule” in Germany) and started high school (“Gymnasium” in Germany) and made new friends.

How to improve your open source code (4) - API Design

This post was written during my trip through Iceland and published much latern than it was written. What is a nice and gold API. How is “nice” defined when it comes to library interfaces? That’s a question I want to discuss in this post and also, how you can create a nice API in your open source library without studying a topic like software architecture or similar.

Blueprint of a distributed social network on IPFS - and its problems

#matrix , #ipfs , #scuttlebutt and now #mastodon - We’re living in awesome times! centralization < decentralization/federation < distribution! #lovefortech (me, April 10, 2017, on mastodon) The idea With the rise of protocols like the matrix protocol, activitypub and others, decentralized social community platforms like matrix, mastodon and others gained power and were made real. I consider these platforms, especially mastodon and matrix, to be great steps into the future and am using both enthusiastically.

The development of a music taste

It is funny how a music taste changes over time. When I started listening to music extensively, which was about 10 years ago (at the time, the nickname “musicmatze” came up, btw), I mostly listened to German rap and HipHop. I did not listen to “known” artists at the time. Some names I can remember are Pidvalid, Syntheciser, End and Alligatoah (yeah kids, take that - I listened to Alligatoah before it was cool).

Why we need distributed issue tracking

This post was written during my trip through Iceland and published much latern than it was written. When writing my last entry, I argued that we need decentralized issue tracking. Here’s why. Why these things must be decentralized Issue tracking, bug tracking and of course pull request tracking (which could all be named “issue tracking”, btw) must, in my opinion, be decentralized. That’s not only because I think offline-first should be the way to go, even today in our always-connected and always-on(line) world.

How to improve your open source code (3) - Modularization

This post was written during my trip through Iceland. It is part of a series on how to improve ones open-source code. Topics (will) contain programming style, habits, project planning, management and everything that relates to these topics. Suggestions welcome. Please note that this is totally biased and might not represent the ideas of the broad community. When it comes to hobby projects in the open source world, one often works alone on the codebase.

CI first vs. Review first

This post was written during my trip through Iceland and published much latern than it was written. Almost all toolchains out there do a CI-first approach. There are clearly benefits for that, but maybe that’s not what one wants with their self-hosted solution for their OSS Projects? Here I try to summarize some thoughts. CI first CI first is convenient, of course. Take github and Travis as an example.

All we need for a self-hosting distributed open source programming toolchain

This post was written during my trip through Iceland and published much latern than it was written. From my last article on whether to move away from github with imag , you saw that I’m heavily thinking about this subject. In this post I want to summarize what I think we need for a completely self-hosted open source programming toolchain. Issue tracking Do we actually need this? For example, does the kernel do these things?

How to improve your open source code (2) - Function naming and size

This post was written during my trip through Iceland. It is part of a series on how to improve ones open-source code. Topics (will) contain programming style, habits, project planning, management and everything that relates to these topics. Suggestions welcome. Please note that this is totally biased and might not represent the ideas of the broad community. We’re slowly working ourselves up from if statements in the last episode of this article series to functions in this article.

Why I think about closing contributions to imag

This post was published on both my personal website and imag-pim.org. I’m thinking of closing contributions to imag since about two months. Here I want to explain why I think about this step and why I am tending into the direction of a “yes, let’s do that”. github is awesome First of all: github is awesome. It gives you absolutely great tools to build a repository and finally also an open source community around your codebase.