>>44202Bro I did my internship at a corporate company and the people there are fucking cattle. One department was still using Java 8, so I assumed that the C# department would be less of a nightmare with the latest version of .NET. I was fucking wrong. They had the best toolbox on the market, but they still built everything like 2012 enterprise slop. Ofc design patterns and class hierarchies are good, OOP is not the issue, its the culture. These retards never ask "do I actually have the problem this pattern solves?" They paste these fucking patterns everywhere because some senior told them to. Also I’m not joking, I once had to explain to a .NET senior what a fucking pointer is. This is the guy deciding the architecture btw.
<Fyi, I was a .NET backend intern, so here is a real example. One endpoint to get a user by id. That’s ONE query. Sounds easy, right? How could you possibly fuck that up? I opened the codebase and found IUserService, UserService, IUserRepository, UserRepository, UserDto, UserViewModel and UserMapper. Seven fucking files for a single SELECT. And the repository sat on top of Entity Framework, which already gives you DbSet as a repository and DbContext as a unit of work. These fucking retards built a repository on top of a repository.
>muhhh what if we switch databases somedayMan just shut the fuck up. Who has ever switched databases on a real project? And if you do, you’re rewriting half the app anyway..
<I swear, work at a corporate company long enough and you start despising Java and C#, which is a real fucking shame because they’re good languages. These nigger slaves have bastardized OOP so badly that devs would rather write fucking javascript than deal with another 15 layers of abstract factory bullshit.