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
-
@melezorus34 yeah it's just like
Not my job to do that, that's the job of the person who writes the tickets.
Just frustrating. I usually end up doing this anyway, I just don't like it -
Tickets/stories should not be changed after they've been commited to the sprint (if you work agile/scrum) but instead a different ticket with a feature change should be raised instead. It's up to the developer/tl/scrum master to push back on changes that are added after the work has started otherwise what's the point of working with tickets, we could just code and use chats to request features added.
-
@vBitza yeah, we operate in "sprints" but our clients (who are more or less monopolous in the industry we wrote our apps for) have a huge shifting goal post problem and or managers are too worried about losing their business to insist on a solid spec (or any spec doc at all, it seems).
Business has been great for about 20 years straight, but our clients get pissy with us about stuff not being exactly what they want even though they don't tell us what they want, and that manifests in tickets being added to spirits and good, correctly solved tickets being rejected (when they should write new ones)
Not to mention the way we act like we're writing COTS software but we let the big client write the speed, which makes it distinctly bespoke -
Regex is almost always the wrong tool for the job unless your all out if other tools ;)
Joke aside, regex is a bad option for any validation unless you have a strict, written down description of the allowed format.
If that’s missing the regex will be to strict or to lax and will keep supplying new tickets indefinitely.
Got a ticket saying we need our website's record creation wizard to have better validation. No worries, just some regex, right?
Sure, regex for name entry (with the usual white person assumptions about names), and fixing the fact that it's in-page popup doesn't close on save. Or save draft. Or delete.
And also you need to apply the name regex for the fields on this page to all the previous names that the user lists.
And there's that one issue where the address history message always shows no matter what.
Oh and make sure that if they choose to ignore those validation issues then the validation message is in the notes for the record.
And fix the thing where it saves as draft instead of as a normal record.
And and and and and...
Can we just talk about making it 1 problem per ticket? This sort of shit makes me look bad when it takes me a week to fix 1 ticket, when I'm usually a few-a-day kinda person
rant