You're viewing a single thread.
You see, that's why you divide all the smaller distinct batches of logic into their own functions and then give the wrapper function a name like blahBlahOrchestrator or blahBlahManager waves hands mysteriously
I prefer to have a blahBlahManagerFactory, with an incredibly brittle undocumented XML configuration file. /s
I find that it makes everyone's work day simpler, because they simply cannot do their jobs. /s
If you don't have your config in .txt files with incredibly confusing implicit syntax, you're doing it wrong.
That's a bit too constraining for my taste. What if I want to orchestrate something like blahBlah, but in a flexible way? Something like an AbstractBlahBlahableFactoryBuilder?
Lordy. That's even worse than I was willing to take it. You win. Shudder Lol.
I wrote a bunch of
ifstatements to work out how to handle various types of errors, and called it ErrorClassifier. Can I add "AI engineer" to my resume now?Only if you name it
ErrorClassifierGPT
blahBlahBlahDoesAllTheThings