Ranter
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
Comments
-
hejx465yTough love.. Discuss problem A, how would you solve it, or go about it. Ignore problem X, that is not your problem.. And helping them deeper in the hole doesn't help anyone..
Also tell them, before writing a single line of code, they should have a clear understanding of the solution they want, if it seams too complicated, it probably is.. And by doing this, you never end up with problem X..
Yes, I've had this issue,, way too many times 🤦♂️ -
@AndreKlang I'll try, it is not my responsibility since they're just a classmate, but I'll try to make them think hard about what solution they want
What to do if someone asks for your help with problem X, but then you figure out they originally tried to fix problem A and recursively came up with bad solutions until they got at X at which point the entire codebase overlaps responsibilities, implementations leak, concrete instances are created in controllers ignoring DI and you just can't say ANYTHING nice about it?
Also does not follow a methodology and just does whatever, thinks singletonning a database context is a good option because stuff isn't saved, says they will 'refactor later' even though it should have been done last week and just doesn't seem to get it?
I've told them that what they're doing is plain wrong and they're making it harder for themselves than it needs to be, but they just seem to not get it, even though at this point basic stuff like that shouldn't be an issue.
Posted this in rant since it became kind of a rant instead of a question
rant