Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "loop of doom"
Computers fear my devaura. Everytime I get called to fix something it magically starts working when I enter the room. 5 Minutes after I leave it broke again.
Repeat like while(true)3
Linux doesn't like my Asus laptop
For fuck's sake stop asking me to login again when I put in the correct password, cannot even sign in as a guest jeez
Never. Partitioning. Again.9
Windows Update prompted me to install the 1809 update for Windows 10 recently.
I left the machine for a while and came back to find it frozen at a completely blank screen.
It eventually restarted...and got stuck in a continual loop where the Windows logo would flash for a second and then instantly restart again.
The restart occurred so early in the boot process that I couldn’t even get it into recovery mode or do anything with it to fix it.
So I had no choice but to reinstall Windows from scratch and reinstall and restore all my software and files. Took about 7 hours.
We often give access to a product owner from the customer on our Jira to keep up a good communication and everyone stays up to date as everything is on the board and not hidden in emails or paper notes on the desk of the guy that is on vacation.
So far, so good
Our customers really like this as they can comment on tickets and they are integrated in the workflow because they can push into the backlog and can review finished tasks.
It is just getting better for everyone so where is the rant?
One project is just a dump of shitty mixed content tickets. But how? They look really neat. There are tickets like "fixes from meeting 20th of may" which are initially well structured with approximately 4 subtle changes to the UI and some explanation and screenshots.
PM says: Good ticket. There you go ticket, into the customer review loop of doom.
20 comments and 13 status changes later. Point 43 from comment 17 is referenced in comment 20 to keep on hold as a third party needs to give feedback, point 7 is still not solved correctly as dev 2 was not aware that it was already discussed and changed in the ticket "Call from 25th of may" where in addition the resolution of points 5-12 were requested with an additional excel file to import.
By now we have the 8th of august and literally 17 of these kind of tickets.
I guess we need to improve the workflow and request a new product owner. But this far I just table flip everytime I get one of these tickets assigned.2
One of our departments works only on Thinclients and one of my colleagues made an loop. You can think what happened.7