Have you heard that story “One day …”? That’s my feeling when I’m hearing these terms in an IT environment.
We may have a majestic monolith. Be proud, own it, it might work, especially for 2016, but what about tomorrow? How do you scale in an economy of scale?
I don’t even try to enlist those terms or to explain them, let aside providing links to Wikipedia, because there is no use. People that know them may learn them the hard way, getting to that point where previous solutions didn’t scale anymore. It may be either the performance of running…
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”? …
Ovi Crisan
Cloud Architect + DevOps + Microservices
