“To those who argue programming is an essential skill we should be teaching our children, right up there with reading, writing, and arithmetic: can you explain to me how Michael Bloomberg would be better at his day to day job of leading the largest city in the USA if he woke up one morning as a crack Java coder? It is obvious to me how being a skilled reader, a skilled writer, and at least high school level math are fundamental to performing the job of a politician. Or at any job, for that matter. But understanding variables and functions, pointers and recursion? I can’t see it.” via codinghorror.com
Please don’t learn to code
What’s happening
“It’s been about a month since the last update to Bugify. I’d like to have an update out every 2 to 3 weeks while the app is still reasonably young, but that didn’t happen this month sorry. The biggest thing I’ve been working on lately is the new permissions system – which is not a simple addition. The last thing I wanted was a bulky permissions system that slows the app down, so it’s a lot of work trying to get it right.” via blog.bugify.com
Bugify-related posts have a new home
I have setup a blog just for Bugify updates at blog.bugify.com. If you’re a Bugify customer, please add the blog to your feed reader to keep up-to-date with Bugify changes.
Related issues in Bugify
One feature that’s not immediately obvious in Bugify is “Related Issues” (or “Issue Linking”). Sometimes you get a ticket that’s related to, or depends on another ticket. We didn’t like the way some issue trackers handle this with explicit “depends on”-type linking, and wanted a system that felt natural, simple, and required less effort.
To link an issue to another in Bugify, you simply need to reference the ticket in a comment, or in the issue description. For example, you could write “We need to get #123 finished first”. This would do two things: first, you would be able to click on the “#123″ and go straight to that ticket, and second, Bugify would asynchronously scan the ticket for links to other tickets. When it finds a link from #456 to #123, it creates a “link” from both #456 to #123, and from #123 to #456 (reciprocal linking). You’ll see the related issues on the side bar, and if something’s not right, it’s a single click to remove the link (every time you update an issue, it will scan for links, so you’ll need to remove the reference to the other ticket if you don’t want the link added back in again). And, of course you can also access the list of related issues through the API.