A lot of things to say have been piling up lately and not much to say them, but let's try and remedy that by commencing with the saying of the oldest in a chronological order and then try saying the others as soon as technically possible.
On Wednesday I borked my computer into a irredeemable mess of turd. The more I tried fixing it the less stuff was working. It is out of these fatal conditions that my decision arose. I would change the flavour of penguins that run the intricate little gearsin my difference machine. And thus I downloaded Kubuntu.
Right away I noticed that a basically working installation of Kubuntu only took me about an hour as opposed to two or so days with Gentoo. The next thing I noticed was how quickly the very same installation rose and grew to something more my taste with packages downloading quickly and all that. Lovely.
Setting up my ATI X1600 for a dual screen setup as I had before didn't take as long as it did the last time, only about two hours of tinkering ... possibly because I had saved the configuration files, yes quite possibly, but they didn't work right away, still. The next thing to do was configuring my sound to work a little bit better and here's where the only very major drawback of linux rears its ugly head. There is no simple way of configuring your sound for 5.1 and proper dmixing. Right now I can only have either dmixing or 5.1, oh well, we'll get her configured.
The qualm I do have with kubuntu is that for some suspiciously odd reason the Opera browser cannot be installed in a simple manner and some other important things aren't in repositories. Also why in the world don't mp3s and other multimedia work right out of the box. This is supposed to be a newbie distro right? Why then so many intricate steps to get the most basic thing of a desktop computer working? Why!
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️