Refactoring for Information Hiding - Ionide Case Study - Run Project
Information Hiding is a critical, but tricky principle to master. This post continues a worked example of Information Hiding based on my Ionide test explorer contributions.
Refactoring
Refactoring for Information Hiding - Ionide Case Study - Getting Acquainted
Information Hiding is a critical, but tricky principle to get familiar with. My work on the Ionide Test Explorer presented some good examples of refactoring to limit scope (Information Hiding). I’ll try to recreate them as worked examples.
Continuous Integration and Refactoring: How to constructively develop against a single branch
Continuous Integration (CI) is a hot buzzword. I’ve had a general sense of it for a while, but Refactoring chapter two brought its place into sharp focus, mainly through Preparatory Refactoring.
Safe Refactoring with Scientist
Agile and DevOps have pushed faster and more frequent releases. Techniques like integration test, feature flags, canary tests, and monitors evolved to maintain service reliability without slowing that pace. But some code paths are so critical that they cannot fail even once. This is where Scientist comes in.