Software. Startups. Outer Space.
Aaron Stannard is the Founder of Petabridge and Sdkbin, building open source tools for .NET developers to build concurrent and distributed applications.
When talking to members of our team about their projects and taking on more responsibility for their outcomes I will regularly recommend the following:
“You should hate your own work product and still ship it anyway.”
This advice is as applicable for shipping software as it is for sending sales emails, graphic design, sweeping floors, or writing this very blog post. But why give it in the first place?
I recently waded into the waters of an intentionally obtuse piece of engagement bait on .NET Twitter, mostly because I thought it was funny:
An ASP.NET GitHub thread entitled “Epic: Eventing Framework in .NET 9” ignited an inferno of criticism for the usual reasons: Microsoft big-footing its own .NET OSS ecosystem, etc, etc…
A few years ago I would have cared about that, but this is simply in Microsoft’s nature - as I’ve written about here before. No amount of public venting of nerd rage or OSS community spirit is going to reach the top of the ivory tower over there. Only changes to Azure spend can make that happen.
If you want to play in the .NET ecosystem as an OSS project, a tool maker, etc - this is the price of admission. If Microsoft entering your space is enough to make you quit or enough to kill your business then you were never creative, determined, or passionate enough to succeed in the first place.
Microsoft claims they’re working on this framework mostly just to improve Azure WebJobs and therefore this isn’t really a threat to MassTransit, Wolverine, MediatR, et al but I don’t believe that. Why make it an epic within ASP.NET, by far the most popular framework in the ecosystem, if you don’t intend to have third parties actually use it?
That aside, it’s not the reaction of the OSS producers or Microsoft on that thread I found interesting - it was the reaction of .NET OSS consumers that caught me by surprise.
Many .NET developers were vocally cheering on the destruction of these popular third party frameworks, as though having multiple, well-maintained tools was an inconvenience that needed solving.
Who are the .NET developers demanding that .NET destroy its own ecosystem and return to .NET to the uncompetitive, intellectual ghetto of yesteryear?
Towards the end of 2023 I had some rare downtime and decided to use it to develop a new skill I’ve wanted to learn: leveraging .NET’s impressive Roslyn Compiler Platform to help Akka.NET users be more productive at compile-time.
That interest propelled me to release Akka.Analyzers, a new set of Roslyn Analyzers + Code Fix Providers that we’ve incorporated directly into the core Akka NuGet package as a transitive dependency going forward, so all Akka.NET users and all packages built on top of Akka.NET will benefit directly from our efforts there in perpetuity.
In this blog post I want to discuss one tricky and important obstacle that was not explained very well in any of the literature I found online: how to actually format the Roslyn-enabled NuGet package correctly. This is non-obvious.
One of the concepts that’s commonplace on software development Twitter / Reddit et al is the notion that management is ultimately responsible for everything that’s done by their employees - i.e. the captain is responsible for the behavior of the crew.
And in a sense this is true - from...
In light of the recent drama with the Moq project’s decision to try to solicit donations through the use of SponsorLink, I’ve decided to share some updates on Sdkbin - our NuGet marketplace for .NET developers that we launched in October, 2020.
The last update I shared on Sdkbin was February 2021 - Sdkbin has continued to be a major driver of revenue growth for us with our Phobos product and handles about 33% of our total revenue.
However, as I shared on Twitter yesterday - we are embarking on a project to rewrite Sdkbin in order to fulfill our mission of becoming the marketplace for OSS developers to build businesses around their technology.
There are some software development best practices out there that are universally and unambiguously true outside of any specific business context - “use source control” is a great example. These are rare.
The lion’s share of software industry “best practices” - SOLID principles, “Clean Code,” DRY, and so on -...
In the aftermath of the 2022 midterm elections in the United States many conservative leaders, disappointed with the election results, blamed their poor showing on mail-in voting laws in key states:
“We will never win elections in states like Pennsylvania, Nevada, or Michigan so long as there’s mass mail-in...
Read More
One of my favorite regularly occurring Twitter arguments is over what should be a simple and uncontroversial question: have you ever had to migrate to a different database in a production application before?
I wrote about our adventures migrating databases for MarkedUp analytics here thus I answer this question accordingly. But the group of developers who fascinate me are the ones who answer along the lines of “no and YAGNI - You Ain’t Gonna Need It.”
The reason for the “controversy” around this question is the “YAGNI” - the attitude that you should never need to migrate databases unless you’re incompetent, I guess.
Ten years ago on August 10th, 2012 I wrote “Today I am Leaving Microsoft and Starting my Own Company” and cap-stoned my final day of working for someone else. Since then, I founded two companies:
I’ve learned a lot over ten years and I’m learning more every year, but I thought I’d take this milestone as an opportunity to reflect on the journey so far.