Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I think there's a good way and a bad way to do this. I agree with the approach of "design and document your classes and functions so they have to be used correctly" but not with "My way is the only way"
What I try to do is lead by example (as in if I already seen or written a piece of code that seems to do a good job in any of our projects) so I have something to point to when I'm doing a code review and I can explain why I think that's a good approach for this case too.
In my company one of the tech leads created a “framework” for other devs to code on. His main goal is to restrict devs from doing whatever the hell they want and follow his platform. But that makes everything so complicated. If I need to find where it sets the connectionString, I’d have to go 7 levels deep in the code. Do you agree with this whole approach? If they wanted to standardize the dev process why can’t they document it and enforce it in code reviews. Restricting devs will lead to workarounds. They will find ways to do stuff by hacking the “framework”
question