News for hackers. Stuff that matters.
Re:Data-Oriented Architecture (2020) by reificator on Sunday November 14, 2021 @08:37AM (#29217092)
My advice to anyone naming things and trying to evangelize them is to try to find any way the name could be made fun of, any alternate meanings that could be applied, and so on. And do that for the acronym as well.

The article here calls it Data-Oriented Architecture once, and then proceeds straight to DOA. Trying to convince people to switch something as fundamental as their software architecture is difficult enough without calling your idea "Dead On Arrival" from the first paragraph.

Re:Data-Oriented Architecture (2020) by jspash on Sunday November 14, 2021 @12:43PM (#29218849)
Agreed. I work with an internal system unfortunately called the Digital Asset Manager. So all day long we talk about adding things to the DAM database and editing the DAM record and so on. It never gets old - to my juvenile sensibilities.

However, the term does occasionally slip into external meetings and interactions with people. It's not a good reflection of the company for sure.

Re:Data-Oriented Architecture (2020) by throwuxiytayq on Sunday November 14, 2021 @02:10PM (#29219661)
Yes, it's a name that's both funny and memorable. I don't see much of a problem.
Re:Data-Oriented Architecture (2020) by marktangotango on Sunday November 14, 2021 @10:02AM (#29217537)
This is so true, I was once burned by an unfortunate mis-characterization of an acronym for a service I had created. It benefits us all to keep in mind that sales/marketing types prioritize different things than technical merit or clear naming!