I've never been a fan of coffee, but I liked drinking it, but more out of habit than desire, and always at work (rarely at home). Years ago I started to notice terrible headaches on the weekends, and only after a long time did I manage to understand that coffee withdrawal was the cause. For me the conclusion was obvious: I will no longer take something that affects my body at this level. I have the same problem with Coke/Pepsi, I stopped taking it too.

Fun fact: on the same day I noticed and stopped taking it coffee, 5 days later I had terrible muscle pain in my lower back (I could hardly sleep). 2 days later I had no more pain. I researched later and saw that this type of pain could also be caused as an effect of caffeine withdrawal.

I mainly use Vivaldi because it has the best vertical tabs experience among the browsers.

I like Vlad: https://www.linkedin.com/in/vladmihalcea

This reminds me of something I did in one of the previous companies where I worked.

Like anyone else, when I joined the company, I had various questions: how to access certain systems, how to handle permissions, how to debug specific services, etc.

I compiled all these questions and answers as notes in a Git repository that my teammates could access. I wrote the notes using QOwnNotes, utilizing its Git integration. So, when someone had a question for which I already had the answer, I could simply share my notes, or create/update a node and share it.

The names of the notes were straightforward and easy to follow, such as:

- aws.md

- azure.md

- kubernetes.md

- staging.md

- production.md

- useful-commands.md (jq, sed, base64, etc)

My teammates used this resource frequently. As I was preparing to leave the company, I suggested them to fork my notes repository. I later heard that they continued to use it for many months afterward.

Very good article.

After read about the poor scenario where the Linux accessibility tools is today (https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-d...), I was wondering: if maybe the developers start to use these accessibility tools to improve their speed reading (and productivity as well), this could also helps to prioritize the accessibility features and bug fixes in Gnome, KDE, Qt, etc.

Sugarcane, I believe.

Yes sugar cane is much cheaper and efficient. But you need very warm climate to grow it. Brazil has that and uses sugar cane for the most part. The USA does not so it uses what grows well in its interior , which is corn.

Vertical tabs is really great.

But there were already extensions for that, which is a better approach than Firefox developing a feature only a small subset of people will use1.

For years every Firefox discussion I saw would have some person saying "why are they wasting their time on X? I won't use it til they have vertical tabs" with scores of upvotes.

This perfectly encapsulates the Mozilla position. Every possible move makes people complain.

Hard disagree. The extensions were terrible, at least for what I want, and probably can't integrate with the UI in the same way.

I totally support that. I know that this can create bad habits, but not everyone wants to become a great piano player; some of us just want to have some fun playing.

Same reason. I can add to this list Readme.com and Notion.

I have the exactly same issue using it with Aider.