Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

tirwhan (6235)

tirwhan
  (email not shown publicly)

Journal of tirwhan (6235)

Saturday December 31, 2005
05:48 AM

New Years Revolution

[ #28185 ]
In no particular order and hoping for a 50%+ success rate, I resolve to:
  • Write a wiki.
  • Cook for a dinner party.
  • Finally stop staring at and actually do something with Perl 6 and Parrot.
  • Be less paranoid about things that aren't worth it, be more paranoid about things that are.
  • Do one bit of creative writing every day (that includes coding, but only the kind of coding where I'm not redoing something I've done before or mindlessly using someone elses interface).
  • Spend more time with friends.
  • Find a new flat in Berlin. Make it habitable to the point where other people can enjoy spending more than ten minutes there.
  • Procrastinate less. Start with the simplest thing first and then just keep going.
  • Contribute some genuinely useful modules to CPAN. My only contribution to date ( POSIX::SchedYield) seemed useful enough to upload, but is hardly the stuff that'll make someones day.
  • Learn how to conciliate "Release early, release often" with being a control freak.
  • Give back more to perlmonks than I get from it (I suspect this is going to be the hardest, that site is just so damn helpful).
  • Lose weight, at least 5 kgs. I'm not really fat, but my gut shows I like the beer and it has to go. The belly, that is, the beer will continue to flow :-).
  • Transcend from test-first to test-driven development.
  • Start a revolution. Somewhere.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Maybe this will help you towards your release early and often issues.

    I've found that the optimum point to release "early" is when you feel the API design is correct. It doesn't have to be "done done" or even bug free.

    But it has to not change underneath people.

    My short talk on the subject [perl.org]

    • Thanks, that is a very good and interesting article and advice. This makes perfect sense except for possibly one thing.

      The hardest part about designing software to me is the API. It seems to come naturally to some people but even they don't get it right the first time all the time, and usually an API can be improved beyond the authors design.

      Given that, it seems it is best to put an unfinished API out there so that people can kick it around, complain about misfeatures and unintuitive behaviour and gener

      • Well, the key to the CPAN thing is that it's all time based.

        For a month you can change it heavily, for up to 6 you can tweak it, at 1 year too bad.

        It makes absolutely no difference if you say "experimental" or whatever, people ignore that a lot of the time if it's there and works and has for a year.

        So the problems come when you upload something, get it sorta working but still not happy, then get distracted by life or other projects for 9+ months.

        By the time you come back, too bad. You have users now. They'l