At my workplace, we like to follow an Agile development methodology called Scrum. Turns out there is a bit of an issue… most issue trackers don’t allow us to organize tickets the way we need to. We’ve been using Trac for a long time (before we started using Scrum), and it’s one of the few tools that pretty much everyone likes. I’ve looked at other issue trackers (Bugzilla, Jira, Scarab, Roundup, etc), but they’re either costly, too heavyweight, or just plain don’t do what we need them to.
Just caught wind of this article. Turns out the need for software developers to optimize can give away information. Take a look at how this article shows you how to determine the right cookie based on a timing attack. Great stuff, and once again, shows the real need to understand a problem before you go coding up solutions.
Did you see it? Yeah, that was the world growing just a little bit dimmer, as one of the most amazing people in the world passed away after a long struggle with cancer.
So, in a previous post I said I’d likely chose git as my dvcs of choice. Well, it’s been almost 2 months and I find that while I’m very happy with the speed of git, it’s command line is more than I care to understand at the moment. I can get by with just a handful of commands, and on projects that are using git, I’ll do exactly that.