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
-
This is definitely one of the reasons I'm defensively OCD about understanding the domain before I start working. If I see excess complexity, I notate it as a risk by submitting tickets with documentation. It's tedious and a waste of time, but it eventually justifies a rewrite.
-
@SortOfTested I do that. Constantly. And it pisses me of that I still take the blame when shit explodes. Every time i have slipped i told them why, brought up risks early. Etc. Still my fault.
-
@SortOfTested to be honest this job is a humongous pain in the ass. They rolled this out too early and it shows. Our sprints are too short. There is no real time for planning. And the whole thing is a clusterfuck.
-
mr-user13525y@projektaquarius
Could you make a unit test and code it to pass the unit test?
After the unit test pass , you could say "Hey my unit test pass,it's working.Whatever happen next,it's your guy problem."
I use the tests to keep my sanity in check. -
"Sprints". Scrum and it's philosophies are the root problem. Shit software is achievable anytime with any methodology. Scrum just makes it much more attainable.
-
mr-user13525y@projektaquarius
The cursed UI component. I cannot help you there since there is no perfect way to write a test for UI.
Maybe add a screenshot in pull request so they know that it's working when you commit it. -
@mr-user possibly. I find that I just get accused of "it works on my machine" syndrome.
Ever work on a codebase that's so shitty, that if you do something in a generally accepted and expected way the entire product shits the bed? Cuz that's the situation I am in. Been working on the same fucking feature for like 4 sprints because it keeps being sent back because every time I adjust it to the shittiness that is currently in the baseline, someone changed something and it explodes again. And the worst part is that this is a well known and established problem. Basically every engineer, except the guy who wrote it of course, hates this system. Hates the baseline, and hates the platform. Yet I'm the one who is "losing trust" with the team, even though I get my shit up and running early all the time. They just break the foundation every time.
rant