Blogmarks
- A wealth of knowledge on kanban – From the Lean and Kanban blog comes a very long, but information rich, presentation on the kanban principles, differentiation from scrum, and a lot of good practical examples.
- ongoing · Test-Driven Heresy – I'm normally a "you must absolutely write your tests first" guy, but I can see the argument that on a new project/component you may be more efficient scratching around and then writing tests. But whatever you do, by god, write tests before the code goes into production.
- Boeing and Dreamliner Troubles – Print – Portfolio.com – An interesting tale: a lean practitioner had shepherded the 777 through Boeing. But management changes and a focus on cost cutting drove him out and it sounds like the 787 is in trouble. Even more interesting, the practitioner left Boeing for Ford, and his lean changes there allowed them to forgo bailout funds. Since McDonnel-Douglas was my hometime aerospace company I feel bad that they "infected" Boeing…
- Adding value in the new news ecosystem « BuzzMachine – "So I imagine a news organization creating a kind of anti-wiki – a dynamic, collaborative Snopes: a list of what we don’t know so we can see what is unconfirmed and so these things can be confirmed – so journalists can add journalism." That rings true with a description of journalism I heard at Georgia Tech's Computational Journalism conference: "Journalism is the science of verification…"
Pywatch: Run tests when your code changes
Saturday | June 20, 2009 | 11:08 am
I’m happy to announce that pywatch is ready for use, I think.
What does it do? It’s both a Python module and a command line client that allow you to run arbitrary shell commands whenever changes occur in a list of specified files.
Here’s an example:
pywatch --help Usage: pywatch [options] "command" file1 file2 ...Options: -h, --help show this help message and exit -v, --verbose Output timestamp when commands are run. chris@pinko:~/Code/pywatch$ pywatch -v ./bin/test src/pywatch/watcher.py src/pywatch/tests.py
Running commands at 2009-06-20 12:00:13.226711 Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. Ran 4 tests with 0 failures and 0 errors in 2.003 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
Running commands at 2009-06-20 12:00:34.422557 Test-module import failures:
Module: pywatch.tests
Traceback (most recent call last): File "/home/chris/Code/pywatch/src/pywatch/tests.py", line 1, in
import makethistestblowup ImportError: No module named makethistestblowup Test-modules with import problems: pywatch.tests Total: 0 tests, 0 failures, 0 errors in 0.000 seconds.
Running commands at 2009-06-20 12:00:44.600708 Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. Ran 4 tests with 0 failures and 0 errors in 2.006 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
So far I’ve been using it to automatically run tests on personal projects, including pywatch and baseboards.
You could use it to run other arbitrary commands whenever you change a file, but running tests was the particular itch I was trying to scratch.
It’s available at GitHub and PyPI
Permalink | Comments (0) | Categories: Programming, Projects, Python, Pywatch
Blogmarks
- Simulate Office Presence with Skype and VNC | Smarterware – Ok, there's something really cool about having your telecommuting coworker "in" the office via a always-on VNC session and Skype video chat.
- The Capitalist Manifesto: Greed Is Good (to a point) – A relatively thoughtful article on the recent economic implosion.
django-baseboard updated to 0.3
Saturday | June 13, 2009 | 11:41 am
I’m happy to announce that django-baseboard has been updated to 0.3
Here’s what’s new:
- Better error handling and reporting for the management commands/cron jobs
- Projects are no longer required to have an RSS feed foreign key (bugfix from 0.2)
- Project.project_url returns the Basecamp project’s homepage URL (because Project.basecamp_url can be any valid URL within a project entered by a user)
- baseboard.helpers.update_summaries takes and honors a network timeout argument (defaults to 20 seconds)
- Projects now have RSSFeed foreign keys — suitable for displaying a Trac change log or a project blog, etc.
If you were following along on GitHub then you’ve already got the last three changes. If you were using the official PyPi relese then I, ahem, forgot to upload version 0.2.
But now there’s 0.3 which is a whole tenth better than 0.2, and a whopping two-tenths better than 0.1.
Permalink | Comments (0) | Categories: BasecampReporting, Management, Projects, Python, Technology
Blogmarks
- Remote logging with Python logging and Django – I don't know why, but we've yet to find something at work that's begging to have additional logging in our Django apps. But if we did, this would be a great way to do it. We log our (few) 500 errors out to the apache error_log and use an app to grep that and notify us of problems.
Disclaimer: I work at The Atlanta Journal-Constitution. The opinions expressed here are my own, and do not reflect those of the AJC, Cox Newspapers, Cox Enterprises nor any other party.
