Trying to code to W3C standards
Doing new things, and why that’s good for YUI.
A little while ago I tweeted that it was my 6 year anniversary on the YUI project. Although, it’s been a great ride it’s time that I move on to do other things.
Over the last 6 years I have dedicated every ounce of my being to this project. I’ve worked on holidays, vacations, even paternity leave. I simply can’t keep that pace up forever, despite the popular opinion that “Dav’s a robot”, sadly I am not.
I truly believe that this is the best move for the project as a whole, it needs to grow on its own without me for a while. I also need to get out from under it and do other things that will allow me to “get my mojo back”, so to speak.
Starting at the end of this month, I’ll be taking a little time offline. I’ll be turning off Twitter, Github notifications, mailing lists, etc and focusing on my family and my personal life (not to mention that my Mustang needs some quality time too). I’ll be “out of developer mode” completely for about two months. I need this, my family needs this and I think the YUI project needs this too.
I’m confident that this will enable them to “Do what Dav would think is best”, but to do it without me. Hopefully this will bring the team and the community closer together to complete the tasks that need to get done and I fully support and encourage that.
This means that at a higher level I will still be involved with YUI and its quest to always work on the server as it does in the browser, I just won’t be the one doing it and I won’t be involved in the “day-to-day” operations of the team.
My new role at Yahoo is a natural progression for me, it will put me in a better place to help, not only Yahoo, but Node.js and indirectly YUI. I hope that you all see this as I do, this is an excellent opportunity for the YUI team, Yahoo, Node.js and myself and I can’t wait to bring all of the Node.js work that we have at Yahoo into the public eye where it really belongs.
Delivering to management a last-minute request
Image by Ieylush
When Google added animated image search
Code coverage is not just for tests
I’ve been meaning to write this up for a while and since I have had this conversation with a few developers over the last week I figured it was time to do just that.
The official definition of “Code Coverage” is:
Code coverage is a measure used in software testing. It describes the degree to which the source code of a program has been tested.
While this is a good thing, there is another important use for code coverage that many people don’t realize.
Dependency analysis is another very important aspect of your development. For example, you may be writing a small widget that requires the use of Lo-Dash. You finish it up, write all your tests and have 100% test coverage (yes, you really should aim for that). Now, you should turn the tables on your code. Instead of instrumenting your widget’s code with a code coverage tool, wrap Lo-Dash and run your tests again.
This report will detail what parts of the external libraries you are actually using to get your 100% test coverage. You may be surprised by how little of the library you are actually using to get the job done. You may also be surprised at some of the things that actually happens under the hood of said library when you do something as simple as looping over an array/object.
The point here is that code coverage isn’t just for tests, it can help you isolate your dependencies and help you streamline your code. And even better, it can help you understand your dependencies better. You never know, you may be relying on them a little too much.
For the record, my favorite code coverage tool would be Istanbul. I highly recommend that you check it out.
Just needing to post something here until I find exactly what I want to start posting.