.NET and the death of potential

Much has been said about the failings of OOP, and how to navigate those failings. This is a think piece about closed-source and its impact on human beings.

4 years ago, I entered the workforce as an “as-junior-as-it-gets” junior software engineer. Having just taught myself to program, I approached my new team’s Angular/.NET stack with immense curiosity and drive to learn.

Closed ecosystems are carefully curated black holes

Microsoft, Oracle, Google, AWS, Apple all thrive on lock-in. Picking on Microsoft, if you’re developing a Windows application, you’re in for pain if you’re not using Microsoft’s IDE to write Microsoft’s language for Microsoft’s OS.

Closed ecosystems are serial killers of autonomy

This black hole of problem-solving discourages creative problem-solving, discourages autonomy, and keeps you complicit in whatever direction the Microsofts want to pull you in.

In Closing

Why settle for something we have no control over? Why settle for something we didn’t choose, but fell in to? Because it’s easy. It’s not easy keeping up with a constantly changing industry. It’s not easy to work full-time and manage life outside of work in the first place, let alone throwing in the monumental expectations of the previous section. It’s easy to surrender to the status quo and defer judgment to the Microsofts of the world.

Advocating for quality, user experience, and thoughtful design in code and in products!