Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
AlmondSauce13163286dSounds like "I've just graduated / just gone on a course / just watched a YouTube video about abstraction, and now I need to make sure everything has a million layers and is fully abstracted beyond the point it makes sense" syndrome.
Catchy, I know.
Worse is the "management has told me to write this in 50 layers, 48 of which make no sense" syndrome.
The worst thing about it is these people generally feel enlightened, and come out with crap like "I used to think like you, I really did, but this way is so much better because it allows me to deal with these 10 hypothetical scenarios that are unlikely to happen much more easily."
No excuse for typos though. There's a reason IDEs these days often have spellcheck for variable names. I fail code reviews over that sort of thing - seems picky, but it's trivial to correct at the time and can easily cause a whole bunch of confusion in future.
rutee0718697286d@AlmondSauce The common brag is to make things extensible and yet every time you add a small change, it breaks. He made some configurations that are either ignored or you have to copy/paste everywhere several times for it to work. I don't know what kind of bootcamp teaches people how to code like this.
It was a lot of stress when I did code reviews because there are so many little things that people can't do right. It makes you think, "Do I really have to point this out?"
AlmondSauce13163286d@rutee07 Oh, that's just "can't code" syndrome in that case. Unfortunately if it goes on for too long, it's terminal. No known cure...
Yeah, sometimes I feel like that in reviews too. In my case it's usually more embarrassing for the author than me, so it tends to get stamped out after a while.
ReverendLovejoy2754286dFor each action you need one class for the controller, one class for the service action, one class for the input DTO, one class for the persisted model, one class for the model mapper, one class for the model validator, one repository class for persistence, one class for the result and one class to hold an error object.
Oh, I almost forgot, you need interfaces for everything.