<?xml version="1.0" encoding="UTF-8"?>
<opml version="1.0">
  <head>
    <title>cmdln.net_2007-08-15</title>
    <expansionState>0,2,4,5,8,13,19,26,30,34,40,52,58,62,63,71</expansionState>
  </head>
  <body>
    <outline text="Intro" Offset="00:17">
      <outline text="A quick review of Stardust"/>
    </outline>
    <outline text="Word of the Week: cokebottle" Offset="03:38">
      <outline text="http://catb.org/jargon/html/C/cokebottle.html"/>
    </outline>
    <outline text="Inner Chapter: Knocking Rust Off" Offset="05:02">
      <outline text="First part of the discussion more general">
        <outline text="Just assuming simple reasons for time away from hacking"/>
        <outline text="Biggest challenging is getting an employer or project team to give you a chance"/>
      </outline>
      <outline text="Second part trying to address change in abilities">
        <outline text="Not even anything as drastic as dystonia"/>
        <outline text="Many friends and acquaintances with RSI"/>
        <outline text="Some with other motor problems, even one with visual processing issues"/>
        <outline text="Most or all have adjusted"/>
      </outline>
      <outline text="Getting a job, position may require compromise and/or sacrifice">
        <outline text="Take a more junior role, less pay, less responsibility"/>
        <outline text="Take a different functional role, like QA or CSR"/>
        <outline text="On open source may require working on less desirable aspects"/>
        <outline text="Commit documentation, do other house keeping"/>
        <outline text="When I joined B2e in the integration group"/>
      </outline>
      <outline text="Native talent is unmistakable">
        <outline text="Skill and experience are a plus"/>
        <outline text="At most may warrant a probationary period if talent is obvious"/>
        <outline text="Since skill, experience are earned, can be re-learned"/>
        <outline text="Unfortunately, many don't agree"/>
        <outline text="Skill, experience are at best a yard stick"/>
        <outline text="Cannot measure every aspect of being a good hacker"/>
      </outline>
      <outline text="Be careful to avoid being too aggressive">
        <outline text="Can be natural to overcompensate, maybe try to prove something"/>
        <outline text="Remember your principles, simplicity in particular"/>
        <outline text="For example, first project for my current employer"/>
      </outline>
      <outline text="Personal projects can help keep practice up">
        <outline text="Something that can be demonstrated would be best"/>
        <outline text="Open source would also be good for letting potential employer, coworkers review"/>
        <outline text="The more practical the project is, the more representative it will be of actual work product"/>
      </outline>
      <outline text="Find a mentor or helpful peer">
        <outline text="Don't be afraid to admit you need time, help"/>
        <outline text="A good mentor or team lead will realize the cost is worth the pay off"/>
        <outline text="Some may see the opportunity as a blessing"/>
        <outline text="Like a junior developer, some room for molding"/>
        <outline text="Unlike a junior resource, closer to self sufficient"/>
      </outline>
      <outline text="Dealing with changes in abilities">
        <outline text="Use an operating system with good accessibility support"/>
        <outline text="Take full advantage of accessibility"/>
        <outline text="Experiment with custom peripherals, alternate input, output schemes"/>
        <outline text="Speech recognition may be usable, though tougher to train for coding"/>
        <outline text="Know some RSI sufferers who use pedals as well as keyboard, mouse"/>
        <outline text="Know some, personally, who use hyper ergonomic peripherals"/>
        <outline text="Take advantage of automation"/>
        <outline text="Much code is repetitive, good IDEs offer automatic completion, templates for common constructions"/>
        <outline text="Time spent on tooling should be less pressured, should pay off for main line tasks"/>
        <outline text="If you can choose tasks, pick ones that work to your new strengths"/>
        <outline text="If open source hacking, find a project that has longer release cycles"/>
        <outline text="See if you can find a collaborator">
          <outline text="If your experience, skills are deeper, can pair program and mentor"/>
          <outline text="May be able to ease burden of building code"/>
          <outline text="Allow focus problem solving without getting bogged down by physical weakness"/>
          <outline text="At a minimum see if you can get someone to help customize tools"/>
          <outline text="Also may be easier on open source projects"/>
        </outline>
        <outline text="Be creative">
          <outline text="Just because you may not be able to work the way you used to, despite mean you can't still work"/>
          <outline text="Hack your own situation, be willing to experiment and not get discourage with things that fail"/>
          <outline text="Any one thing that makes it easy, possible to hack will be worth ten failed attempts"/>
        </outline>
      </outline>
    </outline>
    <outline text="Outro" Offset="28:29">
      <outline text="Contact me">
        <outline text="Email to feedback@thecommandline.net"/>
        <outline text="Web site at http://thecommandline.net/"/>
        <outline text="IM to command.line@skype"/>
        <outline text="Listener comment line is 360-252-7284"/>
        <outline text="del.icio.us tag is &quot;for:cmdln&quot;"/>
        <outline text="http://twitter.com/cmdln"/>
      </outline>
      <outline text="I'd like to thank libsyn.com for AAC hosting and Wouter de Bie for MP3 hosting"/>
      <outline text="These notes and the show audio and music are covered by a Creative Commons license">
        <outline text="http://creativecommons.org/licenses/by-nc-sa/3.0/us/"/>
        <outline text="Attribution, non-commercial, share alike"/>
      </outline>
    </outline>
  </body>
</opml>
