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
-
@DEVil666 - man, are you me? I worked on a small team and we basically ended up having to delay every project 6 months+ just to have super level abstraction and "clean code" - when ultimately it wasn't used by the end client anyway. sheesh what a waste
-
@DEVil666 - to me clean code is secondary. it sounds weird almost for me to see myself typing that, but if customers / clients are dying for a feature, just implement it in the simplest and fastest way possible, even if you have not 100% perfect practices. they'll be way happier and you will too when you can clean it up on your own time. especially for one off features, clean code really only helps for a feature that may grow to higher complexity. that's what I've learned from taking the hard road one too many times
Writing a feature critical for production in 2 hours of solid focus during the morning.
6 hours later it's still not in the build because:
* tech lead wants the code to move to a partial class instead of an extension method, delaying the UX review. No guidelines for this ever existed.
* after seeing the result, the UX team wants some element to be dynamic. A line. A friggin horizontal line.
* after adding the dynamic shiny frigggggin line, I try to test the feature with the server. It is still not deployed because the server guy went home. "The PR was not merged so I assumed we'll add it tomorrow".
Another day at the meat grinder.
rant
pr-hell
screw-you-master
agile-is-fragile