Chapter 76. A Rose by Any Other Name Will End Up As a Cabbage

After a lifetime of playing with computers—starting with writing games in BASIC on the BBC computer and going on to such diverse elements as pascal, Mathematica, and using Labview to process hand-rolled databases made of raw text data files from experiments held together with sticky tape—Sam Gardiner stumbled into professional software development. He has been working in the software industry for six years.

Sam Gardiner
image with no caption

I OVERHEARD SOME PEOPLE DECIDING that they need more layers in their architecture. They were right, as it happens, but going about it a little backward. They were attempting to create a framework that would contain the business logic. Rather than solving some specific problems they started with the idea that they want a framework that wraps the database up and produces objects. And it should use object-relational mapping. And messages. And web services. And it should do all sorts of cool stuff.

Unfortunately, since they didn’t exactly know what cool stuff it would do, they didn’t know what to call it. So they held a little competition to suggest a name. And that is the point at which you must recognise that you have a problem: if you don’t know what a thing should be called, you cannot know what it is. If you don’t know what it is, you cannot sit down and write the code.

In this particular case, a quick browse ...

Get 97 Things Every Software Architect Should Know now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.