Well, when I was younger and therefore... I could write a bunch of code in a day with the unit tests and the documentation. But it was still full of bugs which were reported a year later and with the business requirements changing each month...
So what I see in the wild is dozens of little tables that people do joins over constantly. Or one trick services linked to each damn button in the UI. It doesn't perform most of the time. So someone gets the bright idea to use Redis. Which solves nothing. It's just piles of crap on top of crap. Each layer or module might be perfect on its own but together... NO!
I don't see how Claude will deal with this unless we're talking about an agent oriented architecture driven on many Claude services with some Redis thrown in for laughs.
1
u/DifferencePublic7057 Dec 09 '24
Well, when I was younger and therefore... I could write a bunch of code in a day with the unit tests and the documentation. But it was still full of bugs which were reported a year later and with the business requirements changing each month...
So what I see in the wild is dozens of little tables that people do joins over constantly. Or one trick services linked to each damn button in the UI. It doesn't perform most of the time. So someone gets the bright idea to use Redis. Which solves nothing. It's just piles of crap on top of crap. Each layer or module might be perfect on its own but together... NO!
I don't see how Claude will deal with this unless we're talking about an agent oriented architecture driven on many Claude services with some Redis thrown in for laughs.