architecture22

Check out the latest posts

How *deeply* broken can software get?

I tend to "spend" a lot of keystrokes on various aspects of technical debt and/or poor engineering practices. The list seems endless: component coupling, shallow modeling, leaky boundaries, inconsistent conventions, not-sufficiently-expressive design, incapacitated development agility, unnecessary layers of indirection, overzealous pattern usage, lava flow effect - naming...

Lava Flow Anti-pattern

What can we say about the characteristics of lava flow (no metaphors YET, I refer to RL lava)? * it's practically impossible to stop/revert lava flow, it can either continue in the current "channel" or get routed in a new one(s) * if there's...

You’ve successfully subscribed to No Kill Switch
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.