The latest versions of Firefox, IE, and Opera support EV SSL, but still there is no sign of Safari … and this has been pointed out for quite some time. What in the world is Apple up to?
I have googled twice to be sure I wasn’t missing anything, currently I cannot find anything pointing to an Apple article stating it is being developed or status.
I have mentioned this to other people who seem to care less. My only point is that I enjoy having the choice of four browsers instead of one or two. I am hoping that with the introduction of more stable and safe browsers that friendly competition will ensue, and we the users will win out.
I always find it extremely difficult to come up with things to blog about. I have the privilege of working with some very intelligent people whom I genuinely enjoy talking with. A lot of times I point out how they should make a post about particular conversation. I have been told on more than one occasion that they are more of a verbal person than a writer. My nature is usually the same but I see that as a weakness of myself and I will be trying to rectify it as there is tremendous value in being able to communicate effectively in the written format as well. I will be using posts made by people I hold in high regard and give my own thoughts and spin on it.
The other thing I plan on doing, and have done in the past, is to blog about a particular tool and how I find it useful. As you may very well tell, I enjoy using vim and from time to time I blog about a certain command. I do know the help files document these items well and that there are probably countless other tutorials on the web, but this is mainly for myself and honing my skills as a blogger.
In doing so, I hope to encourage the few people who read my blog to do the same.
Jeff Atwood has a really good post titled Don’t Go Dark. I myself sometimes get caught up in things like this. With the exception of code reviews (which I really do enjoy), I have a tendency to clam up when posting my code out for public viewing for things such as open source projects.
Just last night I happened to post a python class I had been working on, it was (and is) nowhere close to being complete. But I did feel as though it had value in it and could be used by other people. I had hopes others would pick it up and improve upon it as well. I reflected on why I believe people would behave this way, and my only insight was to how I felt. My biggest hesitation was not being able to clarify any misunderstandings or to justify why I had written it the way I did and my name would be attached to the code as it stood.
I thought back to a blog post I read over a year ago, I can’t for the life of me remember who posted it. But one of the reason why was to give you a chance to defend yourself on how lousy the code might have been. It might be because of a bug or some user requirement, but since the code will always be there, it is best to document it with explanations on why you did things a certain way (or do not do things).
Performing code reviews, I feel, are extremely important in a developers life. If developers are using the agile principle of pair programming then code reviews are taken place on a daily basis. But all too often developers do not implement pair programming. I have witnessed teams, which even though they profess to use agile principles, are quick to cut out pair programming from their software development.
Maybe this should be a code kata, in that a developer should write up a snippet of code and send out for review amongst their peers.
As I was about to ‘publish’ this post, another similar fear hit me. As I put out my thoughts and opinions on this blog, I am sure that I will get something wrong. But I will always have a way to correct it and publish it out again … hey, that sounds awfully familiar to writing code doesn’t it?
