How to write an effective bug report that actually gets resolved (and why everyone should)

Posted by mckayc on Oct 18, 2016 2:06 PM EDT
Lucidchart Blog; By McKay Christensen
Mail this story
Print this story

I want you to take a moment and make a mental note of all the software you use on your computer or phone. Which percentage of the software did you pay for? 50%? 20%? 0%?

Chances are if you’re anything like me, most of the software you use, you got for free. I use almost exclusively open source software. Just because I use free software, however, does not mean that the software did not come at a cost. Thousands of developer hours went into each piece of software I use.

Free or not, good software makes our lives better. That is why we use it. So what can we do to give back to the developers who are adding value to our lives? A thank you email perhaps? Donate via PayPal to the developers (even better)? Become a ravenous fan who tweets and instagrams incessantly about the awesome software?

I would argue that one of the best ways we can support the software we love is by showing an interest in the development of the software by submitting bug reports. So next time you are bugged by a bug (see what I did there?), consider taking a more proactive approach than complaining or throwing your computer out the window, and actually take the time to report the bug.

Full Story

  Nav
» Read more about: Story Type: Editorial, News Story, Security; Groups: Community, Developer, Linux

« Return to the newswire homepage

This topic does not have any threads posted yet!

You cannot post until you login.