I use my rad-scripts node module to quickly set up management and automation of my active projects.  I now have a couple private node modules:

  • mah-haus is my node module that mass-manages all my repos – it’s great; with one command I can completely sync my entire dev station when I start/finish a session
  • atci is for my AbetterTrader project and gives me all the dev tools I need to build, publish, and run continuous integration

Thanks node.js, I love my new automated life.  Should I publish these modules even though they have no real public use?  Nah, why pollute the npm-isphere?  But I will put this post here so I can use it for the module home pages.  😉  Carry on!

I’m experimenting with Sprintless Agile as a methodology for my personal projects.  It’s agile without managers and deadlines.  It removes the artificial constraints of arbitrary deadlines from software projects.  Because I just spend the free time I have on my projects, there is no need for deadline tracking.  The need for task estimation is therefore eliminated, leaving priority as the only criterion to be freely applied to all tasks equally.  Without the “get it out the door” pressure, crunch time is lost, but releases are more continuous than planned, and life runs more smoothly.  The hope is that projects will be able to focus on the important goals instead of throwaway demo work.  The fear is that too much time will be spent obsessing over unimportant tasks.  Therefore, the top priority becomes to continuously prioritize.

Why would [git push] fail to push annotated tags as well?  That just results in another disruptive layer of potential synchronization issues.  They finally added sane behavior, but you have to turn it on with:

git config --global push.followTags true

Or, use rad-scripts!  Which has [git-sync], and, as of today, always uses –follow-tags.  I’m loving my Node.js lifestyle.  😛