Glenn Butcher

Home
About Us
foo
incexp
Journal Archive
onedrive
Photographs
Picture Albums
Slashdot Quotes
slideshow
Weather
Resume (.pdf, 17K)
Pictures

Transitory

Teaching

Research
Dissertation (.pdf, 446K)

News
CNN: Technology
CNN: Top Stories
COS Gazette: Headlines
COS Gazette: Metro
CSM
Honolulu Advertiser
Internet News
LWN
Newsforge
NPR News
NY Times
PCMag: Reviews
Slashdot
Space.com
The Hawaii Channel
Toms Hardware: Articles
Toms Hardware: News
Washington Post
Yahoo: Boeing
Yahoo: Missile Defense
Yahoo: Tech Tuesday
Yahoo: Top Stories

Software
HexDump
Home DNS
InOut Board
LOCOMGR
RRController
ttygcc
UBW IR Receiver
Walkabout
website
Gantt Chart
Trainsheet
Google Map Test

Railroading
LaBelle Long Caboose
NG TerraServers
Cumbres and Toltec Maps

Other Stuff
Gumbo Recipe
Links
Salsa Recipe
Weather Station
Website Tags

1/19/2005: New, Improved Website

Everything is moved from pcisys.net, except the motorcar types page. For that, I may make a .pdf, as it never has fit properly on the screen. That, or make some sort of navigable application that lets you step through the makes and models.

I've been using this website software for a little over a year now, and it really has made website-ing bearable. It's easy to write pages like this and post them, knowing that the formatting will be consistent and a link will end up in the navigation without extra effort. I've got an installation set up on a server at work, where I post test event summaries and make pages on other stuff that might be useful across the organization. We're geographically dispersed across two timezones, so communicating is always a challenge. I'd like to see more of what we do in email move to web-based media; email is so onerous to manage when you get a lot of it, especially big-uns. Seems every other email I get at work has a 1-5MB attachment consisting mostly of these huge organizational shields; the content is less than 10% of the file size.

I'm also working on a state-machine process app, geared toward "trouble report" style applications. Really, any app where people collaborate on an information-based solution could make use of it. The process is described in a XML state machine definition, and the tool takes new instances and drives them through the machine, doing state transitions when specific criteria are met. We have bunches of these sort of processes at work, so this sort of tool could be quite useful. Just gotta find the right audience; our chief engineer is trying to stand up a "responsible engineer" process to drive solutions to incident reports, and she seems to be interested. In the imaginative vein in which I named my website app "website", I'm calling my process tool "process."


Posting disabled, for now...