📢 Breaking news! We are rebranding 🚀
~ Software Resilience is dead! Long live Software Antifragility! ~
Dear Subscribers,
🎉 Exciting News! 🎉
Coming October softwareresilience.substack.com will be served from www.softwareantifragility.com.
I created this Substack circa 2017 to serve as a notepad for my PhD on Open Source and Software Resilience.
I failed to follow up on that so I thought I could retrospectively share with you the learnings of the journey. And I did, for a while; 23 posts worth of a journey to be precise.
Lately I have been pondering on the future of this newsletter. I kept feeling that the name and content didn’t align. Instead of sharing content about Software Resilience I was mainly sharing lessons from my field work as an engineering leader 🙃.
I thought of starting a new Substack. But I didn’t want to let this one go and start from scratch. So I started thinking of ways to turn evolve this newsletter to something new; a topic worth investigating and field testing at the same time.
While I was struggling with these thoughts, “universe stepped in” 🤣. I received an offer to sell www.softwareresilience.com. It was the sign I was looking for.
So… Software Resilience is dead; long live Software Antifragility 🚀
From October onwards, this Substack will be served from www.softwareantifragility.com.
What you can expect after the rebranding:
New research related to software antifragility.
Opinion pieces on how software engineering roles, processes, tools, frameworks, etc, can impact the antifragility of a software.
Empirical insights of software antifragility in the Software as a Service industry.
Software Antifragility in the code spectrum: Closed Source - Inner Source - Open Source.
and the occasional engineering leadership / misc posts 😁.
NOTE: I will preserve the old posts as an archive, but the focus will (hopefully) change!
Unless I fail again!
Thank you for being part of the journey.
Talk to you soon 🫡,
Apostolos
P.S: What is Antifragility?
