Checklists - laser cutter, chisels, 3-in-1, and other lathes etc
43 views
Skip to first unread message
Oskar Pearson
Sep 19, 2012, 8:38:08 AM9/19/12
to london-h...@googlegroups.com
Hi All
I've created a 'checklist' project on github at https://github.com/oskarpearson/lhs-checklists for London Hackspace items, with the idea that the checklists can be laminated and stuck to expensive tools.
I've put together a draft example here: http://www.deckle.co.za/LHS-Laser-Cutter-Checklist.pdf
As you can see my first pass for the laser cutter is done (It's a bit buggy, and both the content and format needs work for clarity. Trying to use it for practical burning on the weekend was enlightening.) Feedback is welcome.
We can extend this idea to the chisels, the 3-in-1, and general lathe usage too if people think it's worthwhile. I'm happy to put together checklists for things if people can send me the relevant info (I don't know how to use a 3-in-1, for example), otherwise do the git thing.
I've been wanting to do this for a while - I was inspired by 'the checklist manifesto' - see http://news.ycombinator.com/item?id=1070547 for Hacker News coverage, and http://www.newyorker.com/reporting/2007/12/10/071210fa_fact_gawande?currentPage=all
Selective quote from the latter:
> Yet it’s far from obvious that something as simple as a checklist could be of much help in medical care. Sick people are phenomenally more various than airplanes.
> [...]
> In 2001, though, a critical-care specialist at Johns Hopkins Hospital named Peter Pronovost decided to give it a try. He didn’t attempt to make the checklist cover everything; he designed it to tackle just one problem, the one that nearly killed Anthony DeFilippo: line infections.
> .[..]
> Only two line infections occurred during the entire period. They calculated that, in this one hospital, the checklist had prevented forty-three infections and eight deaths, and saved two million dollars in costs.
> [...\
> The researchers found that simply having the doctors and nurses in the I.C.U. make their own checklists for what they thought should be done each day improved the consistency of care to the point that, within a few weeks, the average length of patient stay in intensive care dropped by half.
Oskar
I've created a 'checklist' project on github at https://github.com/oskarpearson/lhs-checklists for London Hackspace items, with the idea that the checklists can be laminated and stuck to expensive tools.
I've put together a draft example here: http://www.deckle.co.za/LHS-Laser-Cutter-Checklist.pdf
As you can see my first pass for the laser cutter is done (It's a bit buggy, and both the content and format needs work for clarity. Trying to use it for practical burning on the weekend was enlightening.) Feedback is welcome.
We can extend this idea to the chisels, the 3-in-1, and general lathe usage too if people think it's worthwhile. I'm happy to put together checklists for things if people can send me the relevant info (I don't know how to use a 3-in-1, for example), otherwise do the git thing.
I've been wanting to do this for a while - I was inspired by 'the checklist manifesto' - see http://news.ycombinator.com/item?id=1070547 for Hacker News coverage, and http://www.newyorker.com/reporting/2007/12/10/071210fa_fact_gawande?currentPage=all
Selective quote from the latter:
> Yet it’s far from obvious that something as simple as a checklist could be of much help in medical care. Sick people are phenomenally more various than airplanes.
> [...]
> In 2001, though, a critical-care specialist at Johns Hopkins Hospital named Peter Pronovost decided to give it a try. He didn’t attempt to make the checklist cover everything; he designed it to tackle just one problem, the one that nearly killed Anthony DeFilippo: line infections.
> .[..]
> Only two line infections occurred during the entire period. They calculated that, in this one hospital, the checklist had prevented forty-three infections and eight deaths, and saved two million dollars in costs.
> [...\
> The researchers found that simply having the doctors and nurses in the I.C.U. make their own checklists for what they thought should be done each day improved the consistency of care to the point that, within a few weeks, the average length of patient stay in intensive care dropped by half.
Oskar
Mark Steward
Sep 19, 2012, 9:08:34 AM9/19/12
to london-h...@googlegroups.com
Very nice! Should we fork this on the londonhackspace account?
Mark
Onder Vincent Koc
Sep 19, 2012, 10:32:35 AM9/19/12
to london-h...@googlegroups.com
Great work, fork it perhaps?... We should get this up on the wiki :)
Sent from my iPhone
Sent from my iPhone
Ian Henderson
Sep 19, 2012, 11:32:44 AM9/19/12
to london-h...@googlegroups.com
Great idea and +1 for the wiki
Ian
Ian
Önder Vincent Koç
Sep 19, 2012, 11:38:43 AM9/19/12
to london-h...@googlegroups.com
Just a link or a mention in relevant pages to the github raw output would be great :)
Oskar Pearson
Sep 19, 2012, 12:02:47 PM9/19/12
to london-h...@googlegroups.com
Hi Onder, All
> On 19 Sep 2012, at 14:08, Mark Steward <marks...@gmail.com> wrote:
>
>> Very nice! Should we fork this on the londonhackspace account?
>
As to why I didn't do it in the wiki, I thought I'd reply to all to give a proper explanation.
I've spent quite a lot of time trying to make sure that the formatting is useful for people 'at a glance' as they are trying to work on the tool/device.
The issue with putting the actual _content_ of the checklist into the wiki is that printing the wiki pages out leads to a dog's breakfast of a layout, and isn't really amenable to printing in a checklist format. Have a quick glance at the current material-settings printouts on the laser cutter if you need an example.
The fonts and word and line spacing were quite carefully chosen here in an effort to make it readable (See comments in the git repository for font references and similar - I've tried to stick with best practice).
I know there are ways to export wiki output to different formats, but it's always going to be more limited imho. If someone wants to figure out a set of printing stylesheets for the wiki, go ahead :)
A secondary advantage, imho, is that having a more 'curated approach' to the documents will lead to better checklists, rather than huge blocks of text without much structure / clarity. For example http://wiki.london.hackspace.org.uk/view/Equipment/LaserCutter is very very useful - but it's just not a checklist.
Having democratic editing is great, but unless someone owns/curates the content, it ends up like one of my 3am braindumps.
So, in essence I know it's "reinventing the wheel" vs the wiki, but what else is hackspace for? :)
Oskar
> On 19 Sep 2012, at 14:08, Mark Steward <marks...@gmail.com> wrote:
>
>> Very nice! Should we fork this on the londonhackspace account?
>
> Great work, fork it perhaps?... We should get this up on the wiki :)
Thanks! Fork and do as you will.
As to why I didn't do it in the wiki, I thought I'd reply to all to give a proper explanation.
I've spent quite a lot of time trying to make sure that the formatting is useful for people 'at a glance' as they are trying to work on the tool/device.
The issue with putting the actual _content_ of the checklist into the wiki is that printing the wiki pages out leads to a dog's breakfast of a layout, and isn't really amenable to printing in a checklist format. Have a quick glance at the current material-settings printouts on the laser cutter if you need an example.
The fonts and word and line spacing were quite carefully chosen here in an effort to make it readable (See comments in the git repository for font references and similar - I've tried to stick with best practice).
I know there are ways to export wiki output to different formats, but it's always going to be more limited imho. If someone wants to figure out a set of printing stylesheets for the wiki, go ahead :)
A secondary advantage, imho, is that having a more 'curated approach' to the documents will lead to better checklists, rather than huge blocks of text without much structure / clarity. For example http://wiki.london.hackspace.org.uk/view/Equipment/LaserCutter is very very useful - but it's just not a checklist.
Having democratic editing is great, but unless someone owns/curates the content, it ends up like one of my 3am braindumps.
So, in essence I know it's "reinventing the wheel" vs the wiki, but what else is hackspace for? :)
Oskar
Reply all
Reply to author
Forward
0 new messages