There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 2 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 2 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 2 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: over 2 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: over 2 years ago

Admittedly, this is an issue with organization and can be solved with thorough cleanups, but I suspect that may disrupt the usual flow of non-PM people more. I am thinking of using a separate tool like craft.io or productboard.com to highlight strategies, roadmaps, cross-team initiatives, discoveries, etc. With a possible link to JIRA somehow. Has anyone ever tried this? Source: almost 2 years ago

Recently my friend at Productboard noticed an interesting bug in one of our services. For some reason our code responsible for calculating how many days our customers' features spend in certain states (Idea, Discovery, Delivery, etc) in some cases would give us wrong results. - Source: dev.to / about 2 years ago

ProductboardProductboard helps us capture user feedback from email, Slack, Zendesk, our public-facing product portal etc. And see what users need the most. We also use it for prioritizing product objectives, release planning, roadmapping…. Source: over 2 years ago

I use ProductBoard. It's fairly expensive but pretty great. I gather requirements into PB and use the inbuilt editor to flesh them out. When a story is ready I push a button and it ends up in Trello (but you can add your own integrations; there's one for github for example). The integrations aren't perfect but I love it. Used it in my last job and brought it in at my current job. https://productboard.com. - Source: Hacker News / almost 3 years ago