throwawaylala1
Joined 4 years ago
Joined 4 years ago
Wouldn't it be nice if we could start over and apply all the lessons we've learned over the generations? The world would be a much better place!
Or would it?
We'd end up with yet another mess. It'll be a different mess but it'll be a mess nonetheless. Or worse - we'll end up with two big messes instead of one big mess!
This such a complete and utter lie and I'm surprised people in 2022 still believe it.
You do know what's happening when you run Docker on your Macbook, right? Right?
Your frontend team needs an API call that retrieves only friend requests with user names/avatars because the current API call is too heavy.
Normally they'd go to the back-end team and ask them to add an endpoint or modify an existing endpoint to give them the exact data they need. The problem with that is global API surface area becomes more complicated. Complexity is bad because more mistakes are made.
With this model your front-end team can implement the endpoint themselves in the BFF and model the response data exactly as they need it.
They also don't need to deal with that one zealot on the back-end team that gives everyone a hard time about tiny irrelevant issues.
Not really. When you turn off recommendations, the app icons are hidden but the space for recommendations stays there! Yes, just a big ol' block of whitespace with a prompt to turn recommendations back on. It takes up like 30%+ of the start menu.
It's a dark pattern.
> event sourced architecture
You must be joking. Please tell me you're joking.
Keep building strawmen, I'll be building software.
What kind of function documentation are you reading inline lol? Does it have like 30 function arguments?
In what way would the JavaDoc @param/@return/etc annotations actually help? What Godoc has is more than suitable for the vast majority of cases.
so there's that