CIO Principle: Cut It Once

Ovi Crisan
Mar 6, 2019 · 1 min read
Image for post
Image for post

IT in general and software development in particular has a few healthy principles, like KISS, DRY, YAGNI or SOLID. People understand immediately these acronyms, which distill a lot of experiences and good practices.

I’m proposing a new one: CIO principle — “Cut It Once”. Does it need more explanations?

Software development borrowed some terms from other well established industries, like construction (“architecture”, “blueprint”, “build”, etc.), so why not tailoring? For instance, “custom”, “alter”, and why not “cut”? It’s just another way to say “think before you act” or “plan it better”, because usually once something is cut it can’t be put back.

The focus here is on “once”, not necessarily on “cut”, meaning that you can analyze, measure or design as much as you want / need to, but when you act do it decisively.

And who is in a better position to measure and cut than CIO?

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store