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.
This post marks the third one I’ve written this year about versioning problems in open source software development, although they apply to anyone who develops shared software components:
In this post I’m...
I’ve given multiple talks and written posts about distributed tracing, a still relatively novel concept in the field of application performance monitoring (APM,) and how distributed tracing gives us observability into the dynamic run-time behavior of networked applications. I’ve also previously written about OpenTelemetry, “OTel” for short, an emerging industry-wide standard that combines distributed tracing with traditional metrics-based application performance monitoring into a single consumable standard that all APM vendors will eventually support.
In this blog post we’ll explore OpenTelemetry tracing in .NET 6.
The last time I wrote about the .NET Foundation was in the context of the “Project Maturity Ladder” proposal in late 2019 - a well-intentioned, but ultimately not really appropriate measure aimed at trying to increase the adoption of best practices among member projects.
The .NET Foundation has its heart in the right place - widening the range of “acceptable” OSS beyond what is produced in Redmond. I want that too. Everyone does, most of all the developers who aren’t able to use that OSS today because of the historical conservatism of the .NET ecosystem as a whole when it comes to OSS.
The current proposal puts the .NET Foundation as a centralized certification authority for the entire .NET ecosystem. That’s heavy-handed and will ultimately undermine the .NET ecosystem’s ability to become “bigger than Microsoft.”
The key takeaways from that saga, which is still recent in the minds of many maintainers who are participating in this week’s public outrage against the Foundation:
I issued a warning at the time that going down this road of treating member projects like they’ve automatically agreed to whatever the Foundation leadership decides to do by the virtue of joining it will lead to misalignment between the two groups of stakeholders. In other words, agreements have to be constantly renewed among the members - otherwise there will be less cooperation, less trust, and a lot more public pushback.
Two years later and it’s clear that the .NET Foundation did not learn these lessons.
I’m going to address this in three parts:
Three weeks to the day my wife and I welcomed our daughter to the world and ascended to parenthood.
When I first laid eyes on her, instantly recognizing my own features in her minutes-old face, I had one feeling course through my veins: a deep, uplifting, and eternal sense of responsibility. A lifelong commitment made automatically without the utterance of a word.
And it was then I understood what so many other parents, in their own way, had tried to communicate to me about parenthood: it’s a higher calling and you’ll understand what that means once you’re in it. In my unspoken promise to her I realized purpose.
I didn’t worry much about the unknowns while she was in the womb since there’s little, if anything, I could do about those. Instead I turned my attention to things I could control: preparing our home, our routines, our finances, and so on. But one nagging thought that straddled the can / can’t control divide tugged at my conscience: “what sort of world will your daughter inherit and how will you prepare her for it?”
It’s a Thursday, which means: .NET open source drama.
In my last post I went into detail on maintaining API, binary, and wire compatibility for open source projects and why that’s a nececssary ingredient for building professional-grade open source, the type that can be successfully morphed into a sustainable project should the authors pursue that outcome.
In this post I want to cover a subtle issue that you will inevitably run into as soon as you start having to worry about breaking changes for your users: semantic versioning (SemVer) and how strictly you should follow it.
My opinion, with which technical purists will likely find fault, is that strict SemVer is hilariously impractical and projects that follow it blindly actually subvert their own goal of building trust in their project. Read on.
We launched Sdkbin, our NuGet meets App Store marketplace for .NET developers on September 30th 2020, but with an important limitation: that Petabridge would be the only publisher on the marketplace until we had a chance to eat our own dogfood and work out functionality / user experience / business process issues with our customers first.
On Tuesday, January 5th 2021 my grandfather, James Chester Roush, passed away in his retirement community in San Diego, California, peacefully in his sleep. He was 96 years old. He was a World War II veteran, serving as a navigator-bombardier for the US Army Air Corps on a B-26 Martin Marauder stationed out of Sardinia and later, Dijon France.
I’ve written before about how to start contributing to OSS and I wrote for the Petabridge blog about “How to Use Github Professionally” - both of those posts were aimed at helping developers who had experience working in private software organizations bring their experience and passion into open source software and more specifically, how to use Github as a platform to do that effectively.
