Refactoring away the blues

As a developer, one of my greatest tools is the ability to refactor away and redesign an API after it was initially written. Making it more fundamentally easier to understand and use. But there is also another side of the coin that we don't touch upon quite often. Making it more flexible.

Hosting a VM, OpenGL and SSH

Last few weeks, on and off I've been having a play with window creation and (hopefully) context creation for OpenGL in D. Now this isn't the first time that I've done this. I've had a go at porting GLFW to D, I also ported OOGL to D and later on create DOOGLE based off of it.

Google a designer, for the next generation?

About a week ago, Google launched and showed everyone attending their conference a new design technique using a 'material' for mobile application UI's. Along with it, came a web design editor. This comming from Google, these things could be expected but is it really worth a blog post from me? Of course it is. Some of the things they are bringing up is in some ways more impressive than Apple's guidelines for apps on iOS.

The dog eye for the careful programmer

Dogs, a programmers best friend or just mans? Think about it, a programmer is just a human being. Sure they may know something that most others don't (programming), but that doesn't change the fact.
Now as the phrase suggests, "dogs are mans best friend". Means that we work best and along side a dog at our side. Now this originally meant wolves. But we have since breed them into a whole bunch of breeds with each being specialised for their different tasks. This may be herding or just companionship.

Future is bright, I think?

I'm coming up to a major part of my life. Not anything like marriage however. My BCCE301 industry project.
Where by I will be working with industry to do a project in some form. Now my plan is to start to a company where by making a web service utilising D.
Ignoring the major issue of money in doing so, what other challengers will I have in doing this?

My mantra, learning from the pain

As those who know me, I'm a huge proponent of flexibility within programming. But flexibility is just one aspect when programming. What about features and code cleanliness?
Well I have my little mantra which helps with all of that.

Frustrations: Testing networked code

I hate testing network related code. Mostly because there is far too many moving parts in it.
For example you can't really unittest the actual socket itself. Because what happens if something wonky happens with the network stack? Or a process dies suddenly. How do you handle that? You can't really.