The text-based environment in UNIX is incredibly versatile and powerful, programmers and system administrators who log into a UNIX server remotely will typically work exclusively in the console, working on a remote desktop (similar to TeamViewer in Windows) is just too inefficient.

But can a console really function as an everyday desktop? That is what this article will try to explore, and I think you will be pleasantly surprised at just how useful a text-based environment can be!

A miracle occurred this week. Everyone I have talked to about it, myself included, is shocked that it happened.

I did find that a disproportionally big amount of these bugs was reported by players using Linux to play. I started to investigate, and my findings did surprise me.

Asking about your attempted solution rather than your actual problem.

There might be a way of doing complex multi-participant tasks that is better than what's being done currently, but the incentives for each participant are not aligned.

Software Engineering is really frustrating because there’s basically never a “right” answer and so most decisions come down to “whatever the senior engineer wants.”

Software distributions are often volunteer-run and represent the interests of the users; in a sense they are a kind of union of users.

You have an incentive in modern companies to not be the problem person, but instead to ship new features today. Nobody gets promoted for maintenance or passing a security audit.

The title explains it all, you don't even have to read.

Take manual control of your Linux system’s DNS resolution and keep programs from interfering with and overwriting your resolv.conf file.

FOSS is what you make of it. You have the right to make the changes you need from the software yourself, and you are the only person that you can reliably expect to do it.

“Copyleft” or "Reciprocal"… a legal expert opinion.

The following is the 500-mile email story in the form it originally appeared, in a post to sage-members on Sun, 24 Nov 2002.

In this post, I argue that this particular Rubicon has long been crossed, and that we should take a dim view of buying yet more telecommunications infrastructure and services from potential geopolitical foes.
Instead, we should work very hard to regain some semblance of control over our current telecommunications infrastructure - something we have long lost.

Programming is hard, programming is not for everyone, and for the time being everyone might be able to do it, but most definitely most should not.

Ultimately, building software is a complex and deeply human activity. Everything is contextual and there are rarely easy answers. Most meaningful progress happens through consensus, compromise, luck, and lots of hard work.

In the end, a lot can be understood through the lens of values.

I was able to lower my heat pump's electricity needs by ~50% and half of the costs are also paid for by the mining earnings.

The definition of compiler has never assumed generating executable machine code.

Science is supposed to be self-correcting. To test whether science is indeed self-correcting, I tried reporting this misconduct via several mechanisms of scientific self-correction. The results have shown me that psychological science is largely defenseless against unreliable data.

After years of wrestling GnuPG with varying levels of enthusiasm, I came to the conclusion that it's just not worth it, and I'm giving up. At least on the concept of long term PGP keys.