That's all fine and such, but the thread started from the assumption the OP coworker actually have a task to accomplish. Not doing said task isn't "a feature not implemented yet".
An important issue here is that a product can be released
"here"? In which sense? The OP is teaching his coworkers regular expressions as tools
. To be used to generate the product to be delivered. It's on those tools the OP claimed "less code is less bugs" - to which I objected.
Now whether those unimplemented features become "bugs" or not really depends on the documentation and marketing.
Really? That's all? Djees, I wish I had know that years ago. All those time I've been working from specifications and customer wishes - and now you're telling me they don't matter? If I just don't document what I haven't implemented (or haven't implemented correctly), my delivered product doesn't have bugs! Can I keep the test suite, even if it fails?
So, I guess with the following commands you could remove all the bugs in Perl at once:
$ git clone ssh://perl5.git.perl.org/gitroot/perl
$ git rm pod/*
$ echo "Perl is bugfree" > README
$ git commit -m "Removed all bugs from Perl" -a
$ git push origin blead
Quick, put in a grant proposal for the perl5 maintenance fund before Nick and Dave do it the hard way!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||