Contents

On Friday, one achievement I had was learning a new technology that allows us
to keep UI elements and events separated from the software on the
server side, which should allow for more flexible UI code and
decreased chances of code becoming a swarm of angry hornets.  I've
been transparent about the initial increased development time while
learning the technology.

On Wed, Apr 4, 2012 at 9:32 AM, Bob Jones <[e-mail]> wrote:
> We are still very interested in achievements you’ve had from participating
> in our initiative.  When you have a chance, please reply to this
> email and describe what you have done.
>

Version data entries

14 entries across 14 versions & 4 rubygems

Version	Path
replyr-0.1.0	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.9	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.8	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.7	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.6	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.5	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.4	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.3	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.2	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
replyr-0.0.1	test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt
email_reply_parser-discourse-0.6	test/emails/email_was_showing_as_nothing_visible.txt
tr_email_reply_parser-0.6.0	test/emails/email_was_showing_as_nothing_visible.txt
lp_email_reply_parser-0.6.1	test/emails/email_was_showing_as_nothing_visible.txt
lp_email_reply_parser-0.6	test/emails/email_was_showing_as_nothing_visible.txt