Tag Archives: python

Weekly linkage

From my 2005 trip to California.Just a few:

Weekly linkage

This week’s internet cruising:

  • A Beginner’s Guide to Website Feedback – If I can wrap up and launch this damn character sheet app, stuff in this post will be handy for when it betas, especially the surveying. I suspect the LARPing audience will be sufficiently… opinionated to speak on it.
  • Six Useful CSS3 Tools – Some of these are pretty slick, if you're moving into CSS3 development.
  • Sharpening the blade, part MCMXVII: Nine Amazing Hours. – This is incredibly cool, and I plan to use it for a bit and see if it helps me focus.
  • Amazing Examples of Paper Art – I almost hate to link to this, in case Greg gets ideas for elaborate projects.
  • Python Business Rules Engine – Lott raises a good point about handling complex business rules, in that it's (often) cleaner and simpler to go ahead and incorporate complex business rules into the app itself rather than writing a parser to allow external entry. In my case, I have such a small user base on the side that would have been entering these rules that it's just as fine for me to do a small code release for any games added with these validation rules in them.
  • YouTube – Turkish male belly dancer "diva" – Major glitter warning, here. Major. This may be the first male bellydancer I've ever seen who wasn't mocking dancing, and he's very good. I don't like the music or the dissolve and swirling transitions, though. Or the glitter. That's a lot of glitter.
  • Amazon S3 and CloudFront with WordPress and DreamHost | .larre – This is quite a cool plugin. Not the quickest to set up with CloudFront, minifying, and combining, but worth the effort, even just for the hell of it.
  • Girl quits her job on dry erase board, emails entire office – This is apparently fake, but a cute read anyway. I’d advise against airing dirty laundry like that, though.

Tools, Consumption, and Sin-Eaters

These are on my desk at work.  I haven't eaten any yet.In working on my Character Sheet Manager for Geist characters, I’m finally building something that I’ve wanted for a couple of years now in projects at work — an Exception logger. Just a piece of middleware that grabs exceptions and logs them somewhere. In my case that’s Redmine, which has an API for manipulating issues. It’s not a perfect API, alas, because I can’t add notes to issues; I have to update the description of the original item. Django makes this very, very easy to build. I have an app in my project just for this Redmine connectivity, and I can keep its code and tests separate and independent.

I’m never sure how robust to build out something like this. It’s going to prove handy to me in the case of this app and others I’ll be building out, but there’s no way I’m going to try to implement every nook and cranny of Redmine’s API — I don’t need it. If I release it, though, other people could want the things I don’t need. What’s the right balance in releasing a tool?

As always when working on an app, it’s a struggle not to over-engineer things. This Character Sheet Manager project consists of two apps (ignoring the Redmine integration): the Game Manager and the Sheet Manager. The Game Manager is (right now) just a data app — it’s for me (and Greg) to put in Merits, Skills, various powers, etc. The Sheet Manager will be the consumer of said data.

But character creation logic — knowing how many skills someone gets, knowing how many specialties — is really per-game knowledge. But it’s the same for all White Wolf games of this version. …But what if I want to support something like Scion, where the rules differ a bit?

But… I don’t want to support them right now, and might not ever. Is this also a case of You Ain’t Gonna Need It? Right now, I kinda just want to get it out the door and in use as an evolving prototype. I don’t mind refactoring and rewriting some, but I don’t want to shoot my foot completely off, either.

In related news, there’s apparently been grumbling in global-level out of character Geist mailing lists about the existing character sheet. I should hurry.

Quasi-daily linkage