New Year’s Resolutions

6 commentsWritten on December 27th, 2009 by
Categories: About The Blog, Opinions

These are the technical commitments i’d like to make for 2010:

Keep improving Agatha

It hasn’t been long since i open-sourced it but i already consider it one of the best decisions i’ve made so far.  Most of it was written about 18 months ago, and it had been almost a year since any modifications were made to it before open-sourcing it.  Some new features have already been added to it, and there are some more cool new features coming up in the next 2 releases.  Hopefully, we (the people who work on it and the people who use it) can keep coming up with improvements.

I’d obviously like to see more people using it and increased acceptance in general, but that’s something that will take time and more effort, if it will ever happen that is.  If it doesn’t happen, then the people who did take a chance on it will at least get to benefit from the effort that will be put into it.

Get more involved with NHibernate again

My last commit for NHibernate dates back to August 19th.  Definitely not proud of that, but i certainly intend to get back to contributing actively.  While it’s not a very pleasant code-base to work with, i did find fixing issues for NH to be rather satisfying because you know you’re either helping a few people, or a hell of a lot of them depending on the impact of the bug.  I’d also love to clean up a lot of the query batching code because it is quite messy and repetitive.   If any of you tracks NHibernate’s development and you don’t see a commit from me for a while, feel free to bitch at me because of it :)

Increase acceptance of QuickNet

I’m starting to love QuickNet more and more.  In the first post i wrote about it i mentioned that i thought it was a revolutionary step in automated testing (at least for the .NET world) and i still stand by that statement.  I’d go as far as saying that if you don’t see the potential and the value of it, that i can’t help but question your willingness to improve the quality of your work in general.  I was actually very disappointed with the lack of feedback that i got on my last post about it, even though i specifically asked you to comment on it.  Obviously, i can’t expect everyone to leave comments, but there are quite a few of you who claim to be interested in automated testing and writing not only clean but also correct code so i was certainly surprised that a lot of those people didn’t respond to the questions i asked at the end of that post.  I’m pretty sure that once a big name blogger jumps on it, most of you will jump on the bandwagon as well.  Until that time comes, i’m going to continue writing about it and trying to get people interested in using it.  If you don’t look forward to those posts, you might want to unsubscribe from my feed right now :)

Keep blogging

It’s been a pretty successful year for this blog.  I plan to keep up the amount of effort i put into it, and i also want to continue building on some core principles that are pretty much the foundation of not only this blog, but also what i do and how i do it.  I want to keep learning.  I want to keep sharing knowledge and experience.  I want to keep offering my honest and open opinions, no matter how frank or blunt they may be at times or who they might rub the wrong way. I want to remain true to myself.  I will keep treating people the same, no matter how little or big their name is.  A good idea is a good idea and a bad idea is a bad idea and i will continue on treating them as such, no matter who or where it came from.  

My wish for you

I wish everyone the best for the following year, and i particularly wish for you to understand and be inspired by the following quote:

go farther, go further, go harder
is that not why we came?
and if not, then why bother?

Bonus points to whoever can name the author of that without googling it :)

  • http://benpittoors.wordpress.com den Ben

    I was actually very disappointed with the lack of feedback that i got on my last post about it, even though i specifically asked you to comment on it

    You posted it on Christmas eve… You expect feedback by the 27th? Don’t let Mrs. Carter grieve…

  • http://davybrion.com Davy Brion

    wasn’t exactly christmas eve if you check the timestamp ;)

    besides, the stats show that it certainly was viewed enough, no matter what time/date it was posted

  • Ex-reader

    I’d go as far as saying that if you don’t see the potential and the value of it, that i can’t help but question your willingness to improve the quality of your work in general. I was actually very disappointed with the lack of feedback that i got on my last post about it, even though i specifically asked you to comment on it.

    Wow. Just, wow. Over the last few months the amount of useful content on this blog has gone down and your ego seems to have no upper limit these days. Time to get over yourself (for you). Time to unsubscribe from this blog (for me).

    • http://davybrion.com Davy Brion

      the ego thing has always been like that, so i’m sorry it took you this long to figure that out

      as for having less useful content in the past few months… it depends on what you like i guess… the stats seem to disagree though

      anyways, like i said, the content will probably be similar (at least in topics) in the upcoming months, so yeah… unsubscribing was probably a smart move :)

  • http://www.bigmostacho.com/ Bruno Martinez

    I agree with ex-reader. It ‘rubs me the wrong way’ when improvement is seen as one dimensional. There are many ways to write better programs. Dictating a single path leads to hype, not advances.

  • http://davybrion.com Davy Brion

    @Bruno

    It’s not about one-dimensional improvement or dictating a single path. For example, I never said that people need to drop every kind of testing that they do and replace it with QuickNet tests or that QuickNet is a silver bullet that’s going to solve all of your problems. But it is definitely a very valuable _addition_ to your toolbox and your development process.

    Pretty much every principle or practice that most of us subscribe to is based on one of the following two goals:
    1) create working code with as few problems as possible
    2) keep it clean, maintainable and sustainable

    using QuickNet is an effective way to find as many bugs as you can… and i really don’t understand why more people don’t see it that way