KAS89

5y

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

Ranter

Comments

1

vane

11038

5y

I prefer composition over inheritance if that is the case. Code is more manageable and loosely coupled.
3

VaderNT

1659

5y

Very good question. Your tech lead's (and many others' similar) attempts to "enforce good code through code" is very much understandable. However, it cannot be effective as it rests on a wrong assumption: That you can "fix people". With technology in this case.

Technology, processes, scoldings, etc don't fix people. People fix themselves. If and only if they themselves think they need fixing.

In all other cases, the workaround it is.
2

Hazarth

8971

5y

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.
1

jesustricks

2690

5y

awful idea, what you said is better...
1

Devnergy

6250

5y

Hey OP, maybe they are doing it to downplay you. Maybe they are afraid of you and wants you not to climb to their ranks.

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service