Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
asgs701476d"Not a Bug"
Cairo276dRecategorize as feature.
volttide45076dIt just did!
Obi-WanSpock65175dStory of my life
Just a f*****g screenshot with title bug and no more information.
You sir/mam, have a bug in your brain. Get it fixed before you go into the app to perform testing
PublicByte90375dI want your opinion on this one.
Back in the days when mailing lists were used instead of today's direct solutions (e.g. GitHub issues), people cared about writing detailed issues, including what they think the problem is related to, where the potential flaw is and so on and so forth.
In my opinion, people still have the need to write everything as formal and detailed as possible when writing an email. The saddest part of all of this is when I noticed this behavior on myself.
I often edit issue descriptions, because I missed smth, didn't get to the point across, or accidentally submitted the issue without a description at all.
In contrast, when I'm writing an email, I carefully check if everything is there, don't make any harsh decisions, and verify every detail I've written in the email as I'd have to write a follow-up email explaining that I forgot to mention smth.