I have a folder for my projects on root and within those projects I have my GitHub repos all contained within their own directory named the same as the project.

If I am learning something, I have a folder for the topic I am learning, and a logseq file with all of my notes. Then I have folders for my book references, one for video or audio references, and then a folder for my practice projects.

If a random reddit post is correct and he was 84 years old, I can only hope to have the same drive and mental ability at that age. RIP.

My job is working with a ton of servers over ssh. Bash is the most convenient balance between features and not needing to do any setup.

I learned python by finding something I wanted to make, then referencing the documentation to learn things I didn't already know.

If I had trouble with finding it in the docs or understanding, I would just YouTube it/ duckduckgo it until I found a video that made sense.

I just did that over an over again and now about 30% of my day job is writing python.

I can never put my finger on why I don't stick with GIMP. I install it on every machine I own, and occasionally use it to open a file and export to another file format.

From time to time, I tell myself I will finally sit down and just only use GIMP. Finally learn the tool. Envitably I find myself googling to find every tool, and then I will come across something simple, like making a red rectangle, and I end up having to google how to do it, and then get frustrated that I can't just draw a box and quit.

There are probably legit reasons for the decisions, but if it kills my workflow, I can't afford to use it.

All my homies hate Packt.

Seriously though, I bought one bundle of Packt books and they were some of the most poorly written books I have ever worked through. Not to mention as I got better at the subject, I frequently had to relearn things I "learned" from those books. If it was even correct, it was frequently a bad way of doing something.

I think Linux phones would be super cool. And I dream one day it will become a properly usable reality. But what I really want is a properly supported, powerful ARM based laptop. Something approaching apple M series performance with the same kind of battery life. If Ubuntu can nail that, or another distro like asahi Linux, I will be happy with that and using graphene OS.

I didn't own this console when it was released, but I remember being totally enamored with it. I thought everything about it was just so cool. The boot screen, the console shape and look, the games on it. It was just so cool. I have since purchased one as an adult and it is one of my favorite consoles of all time. There is a timeline where this came out and competed against the ps1 and not the PS2 and we live in a world where Sega is in Sony's place.

My job is contributing to the building of an open source project full of shared tools and resources for businesses in my industry to share. I am part of a team of skilled developers and citizen developers across my industry that work to create shared FOSS tools to make all of us more efficient at our work.

So about 60 hours per week.

This might be the strongest argument I have seen. Thank you!

I usually grab a 3-4 year old Thinkpad every year or so for anywhere from free to 300 bucks. I pick them up from old corporate liquidation lots. Usually grab one that is a little dirty or beat up and then just clean it up and install my own SSD and upgrade ram from my stockpile.

I like some of the others on that list, but with how cheaply and easily I can get a Thinkpad, I just can't be bothered to spend more. I use my laptop mainly for code, and I do a lot of low-level programming so performance is usually way more than enough. The programs I write are extremely small and very efficient. Any processor from the last 20+ years will run what I am usually working on.

When I want to spend big bucks on a computer, I put that money towards my desktop where I do more gaming and some digital artwork.

I know a handful of languages and I think of them as tools. For example, a flathead screwdriver will work on a phillips screw head (In most cases with some outliers), but a phillips screwdriver might just be better for the job. Same with a wrench and a socket with a ratchet, etc.

When it comes to programming or scripting I approach it in the same way. If I am at work, and I need to automate something quick and dirty, no end user will need to use it, and it is just adjusting data or spitting data back at me, I am probably going to write it in Python.

Or, if I need to make something that an end user is going to interact with, I am probably going to spin up a web server and use the MERN stack to create that.

If I am working at home on a TUI for my favorite application, I am going to use Rust or Python

And if I working on a project that requires me to work with embedded systems, I am probably going to reach for C, maybe C++ depending on the support, and I have in a couple of instances needed to use Assembly.

All this to say, I think that if I had to use Python for all of these, I would be in trouble. Same as if I had to use C++ to accomplish all of the above. Could it be done? Sure. Do I want to do that? Not at all.