Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
dotFuck326113dWhat system is this?
And what pricks. Writing some handy tool is a sign of laziness? Fuck them
tokumei2555113dI call laziness efficiency.
Fast-Nop15129113dWhat usually helps is when you get less done in the same time and shrug it off to management with "you wanted me to use that inefficient stuff".
BlackHades1113dCreating your own tool is laziness LMAO....
hash-table4288113dThat is why all Pharmacy reps are super model hot and all software reps seem to be following suit.
Amazing this is still how sales get made in 2019 really #metoo
I wrote a system for automating the thousands of annual disk RMAs our engineering team handles. Management is in love with it, because of the time it saves. They've told us many times that we need to move from JIRA to SNOW, and I've told them that it simply will not be possible without API access. "This is not a refusal to work. It's just not possible to involve the new system without programmatic access to it."
They say they'll look into it and then they never get back to me until a couple weeks later when they've completely forgotten everything I've said, and say, "why aren't you using the new system!?"
LynxMagnus1813113dWe switched from Assyst to Service Now a couple of years ago. It's an improvement on Assyst but it's so frustrating to use. UI is terrible.
vlatkozelka3028113dmaybe unpopular opinion, but personally all ticketing systems suck balls IMHO.
We have been less and less reliant on JIRA for the past few months, and just relying on git (gitlab) with properly named branches, and a good old whiteboard.
I've never seen my team work at such speed in 2 years, and the bug free sessions on our app have never been so many. I was looking at git activity today to fill in JIRA, and I was amazed by the increase in merge requests, and the quality of the reviews/code
Honestly, JIRA and such feel more suitable for communication between different departments*, rather than between the team members/managers.
It might be the case of not every toold/method is for everyone. Some teams need JIRA, and some teams might be hindered by it I guess.
* I don't just mean departments, I mean people that have no better way to communicate. Like the dev team of the company and the QA team that works for the customers for example.(yes one of our customers have their own QA)
I don't see the value of jira for development, but I think it's well-suited for tracking problems, like RMAs. That said, I agree that ticketing systems in general are terrible, and I have yet in my nineteen year career to find one I like.
hash-table4288112dWell, you could make it all so simple and use what we use Basecamp :) essentially just a task list. Isn't that all a ticketing system is anyways?
vlatkozelka3028112d@bahua exactly what I meant, but shorter :p
One of the managers once asked for info about something that's been done a year ago. My co-worker argued, with evidence from a year ago. The manager asked: "how the hell do you know what happened that dau in such details, even though we didn't have Jira back then". He answered:" Helloooo... we have git! What kind of developer even needs jira?"
stonestorm36111dAwful slow java script-based websites are growing nowadays.
With npm and such being so popular this seems to be the future of Web.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job