Re:Behaviours to avoid in a software architecture role
by spookthesunset on Tuesday February 02, 2021 @03:17PM
(#26006035)
I hate with a passion services that have cute clever names. It makes it impossible guess what they do. It makes it easy to overload the service with things that don’t belong.... if the service was named “OrderService”, if somebody wanted to add a “spell check” endpoint people would start asking questions if that service was the right place. But since the service was named “CaptainCrunch”, who knows if spell check belongs...
Same goes for team names too... clever team names are obfuscation.
Re:Behaviours to avoid in a software architecture role
by Geminidog on Tuesday February 02, 2021 @03:27PM
(#26006174)
Agreed, the post you replied to had a sort of different point though. I took two semesters of naming things as part of my PhD in software architecture. Do you know anyone with such a PhD? Do you know of any course in any university that teaches people how to name stuff? Did you need to take such courses to arrive at your philosophy on naming things?
Re:Behaviours to avoid in a software architecture role
by GoblinSlayer on Wednesday February 03, 2021 @03:36AM
(#26011759)
Mathematics does calculations, not decisions.
Re:Behaviours to avoid in a software architecture role
by Geminidog on Wednesday February 03, 2021 @12:08PM
(#26015880)
The post was sarcasm that flew over your head. You can’t even get a PhD in software architecture because the entire field is a sham title created by industry. There is no theory or science behind “software architecture”
Either way you are wrong about math. All decisions can be mathematically modeled. It’s called a conditional expression, and you use it to model/calculate decisions when you program.
Re:Behaviours to avoid in a software architecture role
by GoblinSlayer on Thursday February 04, 2021 @04:07AM
(#26023912)
Different conditional expressions make different choice in the same situation, then you need to choose what conditional expression should be in the program.
Re:Behaviours to avoid in a software architecture role
by Geminidog on Thursday February 04, 2021 @08:17AM
(#26025060)
Different numbers produce different results in the same arithmetic expression.
Here's the concept of conditional expressions explained via a mathematical text: https://math.libretexts.org/Bookshelves/Mathematical_Logic_a....
When I went to Standford to get my PhD is Software Architecture I was required to take at least 2 semesters of classes on the theory of naming things in software. The biggest point the class made was proving mathematically how one should never name anything after a plant, Greek/Roman god, gemstone, animal or molecular structure.