schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Take no risk with legacy.
Before touching working code, weigh it:
frequency of change × risk × cost of refactoring.
If the code never moves, reflection is a cheap way in.
A characterization test (Michael Feathers) freezes today's behavior, bugs included.
Refactoring working code just to make it pretty rarely pays off.
So don't refactor it. Reflect on it.
🚀 Clean Code & Design Patterns: Writing Code Other People (and Future You) Can Read
Clean code is about the reader, not cleverness. This post covers naming, guard clauses, pure functions, refactoring with a safety net, SOLID in plain English, and patterns like strategy, adapter, and wrappers, then builds a provider-agnostic summarizer.
The mark of great systems engineering: modules that are trivial to replace or delete. When you couple your orchestration logic tightly to a specific cloud vendor's proprietary SDK, you inherit all their pricing shifts and downtime.
Keep your core orchestration vendor-agnostic standard library Python.
Technical Debt: How CTOs Measure, Prioritise and Pay It Down
Technical debt explained for leaders: the four kinds of debt, how to measure its “interest”, a scoring model to prioritise it, how much capacity to fund, and how to talk about it with the board.
#EngineeringLeadership #TechnicalDebt #CTOStrategy #Refactoring
The mark of great systems engineering: modules that are trivial to replace or delete. When you couple your orchestration logic tightly to a specific cloud vendor's proprietary SDK, you inherit all their pricing shifts and downtime.
Keep your core orchestration vendor-agnostic standard library Python.