Joseph Hallenbeck

Anno Domini 2018

Sometime last Winter Nelson Elhage’s essays on using lab notebooks for software engineering made the rounds on Hacker News. One item in the early essay struck a cord with me: Computer scientists are taught to document the end results of their work, but aren’t, in general, taught to take notes as they go This seems to be current standard protocol for software versioned with git where care is taken to currate the repository history. Rather then record every wrong step and dead-end branch we are taught to prune and re-write the record by squashing our merge histories. A half-dozen commits...
Years ago I filed to incorporate a limited liability company. I did nothing with it since, but now find that I am at the juncture in my career when I should feel comfortable with taking on and managing client work beyond the stable income of my employer. This is the natural progression of a remote worker, and while I have no plans of leaving my day job, diversification in this age is absolutely necessary. Kynda Consulting will focus on serving the White Mountain area, by providing website development and hosting at the local level, and bringing economic development to the...
Continueing my book club notes on the the Pragmatic Programmer by Andrew Hunt and David Thomas. Chapter 3 The best way to store knowledge is in plain text, not binary blobs The drawback to plain text is that it comrpesses poorly, and may be expensive to process. This doesn’t seem particularly relevant with modern computers, but I suppose embeded systems still suffer this drawback. Plaintext helps insure against obsolescence and eases testing Shell beats GUI Get good at one editor until it’s like playing the piano Use source control (yeah we’re doing the obvious now) Embrace debugging as just another...
Recently, I’ve been running a book club to cover the contents of the Pragmatic Programmer by Andrew Hunt and David Thomas. One of those volumes that has been held up, forever, as a text that any good Software Engineer should have read. The text itself is rather sound, although starting to show it’s age in the era of software-on-the-browser. Probably not going to do much of an articulated look at the book. Rather, I think I will simply post my cliff notes as I, or we go through each chapter. Chapter 1 Take responsibility for actions, career advancement, project, and...