Software_engineering

I recently re-read my original post about Weave - the data-pipeline language I’ve been developing in my spare time. That post ended with the words “Weave is nearly fully implemented - and I’m nearly through the book! Another few weeks and I believe I’ll have Weave ready[…]” Oh the Hubris of my youth. In reality, it has taken me another seven months since those words were typed before I could consder Weave to be even remotely “ready” for “anything”. [Read More]

Ah, Null. Infamously referred to as the billion-dollar mistake. As software engineers, we likely spend a quarter of our careers managing Null. Checking for it. Returning it. Trying to figure out WTF returned Null somewhere down there that caused an invalid de-reference here… No getting around it. Development in languages with Null can be Iffy. I’m a Ruby dev in my day job and after writing some variant of if ! [Read More]

I’ve been writing software for Decker for about 4 years. During that time I’ve experimented a bit with what what works for having a display constantly in my line of sight. Rule 1: Make it Useful First People (including yours truly) will put up with bad UX if the program solves a need. But useless software never gets run. There are whole books to be written about how to write useful software, but one good technique is to start from a problem. [Read More]