[Geek-post] Why I choose open source

I’m currently using an awful lot of software and getting to the stage where I’m having to develop my own.  For this reason I thought I’d keep a little track of what I’m using and why. I’m in the process of moving all of my computers across to Ubuntu for a number of reasons.  Really the tipping point came one day when Windows 7 (the uncrashable) blue screened on me one too many times.  Now I’m perfectly happy with my gaming machine to use Windows and crash occasionally.  This is because by and large (despite Wine trying hard) you can really only game in Windows, and that’s largely due to it being the largest market.  This combined with the fact that the machine barely ever has the sides on means that a crash or two is unavoidable.  However, this my work PC, the PC that has its core programs, talks to the internet and that’s it.

So, what with my work requiring a lot of linux, I had the thing set up with virtual linux machines anyway I’d just never much had the time or inclination to go the whole hog and convert. At the end of last week I decided to convert my work machine to a dual boot machine.  After struggling to get Fedora to set its installation up on a pen-stick (I liked the idea of being supported by RedHat), Ubuntu (renowned for its user friendliness and compatibility) it was.

After a seamless installation I jumped straight into it, and wasnt disappointed.  In fact I was playing with it for 2 days before I even realized that I’d set up the boot loader wrong and it wouldn’t actually boot Windows at all.

Whilst this is a relatively minor problem and could be easily fixed, I’m now actually struggling to think of a reason why I’d want to.  From Ubuntu I can see all of my windows files and access them, so there’s no problem there. And I find myself actually in a much better position than I was in.  Everything that I used to do, I can do quicker and cheaper than in Windows and often much prettier.

This really feeds into my socialist belief that, for something to really progress it requires co-operation; and as time has gone by and all of the less complicated discoveries have been uncovered that only leaves the complexities.  And I believe that software should be much like science in that the whole community should work toward making the best, most complete solution for everyone.  Furthermore I believe that if something goes wrong, then anyone (with admittedly some level of knowledge in the matter) should be able to find out what is going wrong and attempt a solution.

People shouldn’t be discriminated against, or just kept in the dark for no reason.  How many times has Windows crashed on you and its then asked if you’d like to submit an error report.  When clicking yes you get a little animation implying something might be happening and that’s it.  The Apple website has a submission area where you enter any faults, problems or even suggestions.  To that you only get a “Continue” button.  I didnt even get a confirmation email for all my iPhone woes.

So, now I find myself using open source for almost everything.  And the more I use it, the more I like it, the more I investigate and the more I understand about how software actually works.

At the end of the day, I like control.  I like to be in control of my devices. And it’s for exactly this reason I have an Android phone (and not some Apple controlled fenced garden), a Linux operating system, Open Office (for the few times I require office applications these days), Firefox web browsing, Thunderbird email, etc, etc

I appreciate that paid software has a place in this world.  Millions of people use it everyday without even thinking.  Something Microsoft has gotten very rich off (not bad when they didnt really write any of it themselves). But when it goes wrong, you’re stuck and you have to wait for a patch.

I love Corel Draw, I grew up with it as my drawing program of choice.  But the new version is £750! Whereas, yesterday I downloaded Inkscape from the Ubuntu software centre for free and in 4 minutes I was drawing like I’d used it as if it was the new Corel update and I’d been using it for years. And I’m sure many people feel the same with Photoshop and GIMP, but unless you are a professional design photographer I doubt you use 10% of photoshop.

For that matter I doubt anyone uses more than 10% of Word. Microsoft know this. Their response to continue making money, is to change all of the menus and change the document format so that nothing’s compatible anymore. Is that really in the interest of the user?


This page previously appeared on morganbye.net[^1][^2]

[^1:] http://morganbye.net/2010/07/geek-post-why-i-choose-open-source) [^2:] http://morganbye.net/uncategorized/2010/07/geek-post-why-i-choose-open-source

Older post

Lecturing eh?

HTC Desire headphone jack fix

This morning on the way to work I got down to the road, plugged in my earphones to my phone and hit play on Spotify. Only for some horrible, tinny, quiet music to come out. It seemed that the phone just simply would not recognise that anything had …

How do you define successful engineering leadership?

The Philosophy

Many view technical leadership as being the “smartest architect in the room.” I see it as the opposite. My job is to build a room where I don’t have to be the smartest person because the systems, culture, and communication are so robust that the team can out-innovate me.

The Strategy

  • Alignment: Does every engineer understand how their sprint task impacts the company’s bottom line?
  • Velocity vs. Stability: We aren’t just “shipping fast”; we are building a predictable, repeatable engine that doesn’t collapse under its own weight at the next order of magnitude.
  • The Human Growth Curve: Success is when the engineering team’s capability evolves faster than the product’s complexity. If the team feels stagnant, the tech stack will soon follow.

What is your approach to scaling technical organizations?

The Philosophy

Scaling isn’t just “hiring more people” - that’s often how you slow down. Scaling is about moving from Individual Heroics to Organizational Systems.

The Strategy

  • The 3-Continent Perspective: Having managed global teams, I focus on “High-Signal Communication.” As you grow, the cost of a meeting triples. I implement “Asynchronous-First” cultures that protect deep-work time while ensuring no one is blocked by a timezone.

  • Modular Autonomy: I advocate for breaking down monolithic teams into autonomous units with clear ownership. This reduces the “communication tax” and allows us to scale the headcount without scaling the bureaucracy.

  • Automation as Infrastructure: At petabyte scale, manual intervention is a failure. I treat the developer experience (CI/CD, observability, self-service infra) as a first-class product to keep the “path to production” frictionless.

How do you balance high-growth velocity with technical stability?

The Philosophy

Technical debt isn’t a “bad thing” to be avoided; it’s a set of historical decisions that no longer serve you. Like any loan, leverage can accelerate growth when investments payoff. But if velocity and returns are slowing you need a payment plan before the interest kills you.

The Strategy

  • The ROI Filter: I don’t refactor for the sake of “clean code.” I don’t refactor a micro-service with no users. I refactor when the pain on that debt - measured in bugs, downtime, or developer frustration - starts to exceed the cost of the fix.

  • Zero-Downtime Culture: Especially at scale, stability is a feature. I implement “Guardrail Engineering” where the system is designed to fail gracefully, ensuring that a Series B growth spike becomes a success story rather than a post-mortem.

  • The 70/20/10 Rule: I typically aim to dedicate 70% of resources to new features, 20% to infrastructure/debt, and 10% to R&D. This ensures we never stop innovating, but we never stop fortifying either.