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
-
netikras35222151dWhat's the point of reading commit history apart from looking for code history [eg how that line looked before] and/or blame?
-
dissolvedgirl1065150d@netikras because their code is insanely weird and hard to understand, since they don't seem to like following conventional programming paradigms and patterns, so I figured the commit history might be less demanding on my brain, but it really isn't. I just scanned through it tbh.
And now they're still making changes on source code after sending me a zipped version of source code, because they don't want to give me read access to their repos so that I can clone it and pull whenever they've made changes. It's supposed to be in code freeze. Told my directors I will not be held responsible for any changes that are missing after I import this to our source control.
These people are quite unprofessional, but I admire their tenacity to deliver a working product and dedication to the software nonetheless. You can see the passion in the way they wrote code, but oh man it's bad.
Related Rants
Haven't even touched the code yet (besides reading the cringe commit history) and I'm already burned out
rant
spaghetti