[Sean McGrath:Work[not(Flow)] : The Pythonic Method, Trac, and Capturing Chaos (AKA The Real World Work Flow)

by M. David Peterson

I was first introduced to Trac by Bruce D'Arcus in December of 2004. At that point in history one could easily claim that setting up Trac was very much NOT Pythonic**.

On the other hand, using Trac for the first time was my initial introduction to the "Pythonic method" (if there is such a thing), in this case, the Pythonic approach to managing software development.

Firstly, what is Trac?

Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission; to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.

Okay, so while the focus is primarily on software development, in my own experience, Trac can easily be used for managing MUCH more than just software development. In fact, I would definitely go as far as suggesting that in many ways Trac implements (again, if there is such a thing) the Pythonic method to workflow management, and as such, can be applied to any type of project, software and non-software related alike.

Just to clear things up, what does it mean to be Pythonic?


2006-09-27 05:44:47
the more powerful tools get the more starters turn into finishers,
if only those tools didn't induce new ideas... :-)

Just make sure a team has a healthy communicating team of both

2006-09-27 10:06:10
Hey stelt,

>> if only those tools didn't induce new ideas... :-) <<

Amen to that! If it wasn't for those pesky ideas always poppin' up, I could probably get some actual work done each day ;)