walls.corpus

By Nathan L. Walls

  • Arriving + Departing/Manhattan
  • Gilded Stream/Accord, New York
  • Substation/Washington, D.C.
  • Hondros Exhibit/Fayetteville

Tool Sharpening: Oct. 21, 2014

For some background on what’s going on here, see the first tool sharpening post

Environment + Process tweaks

  • Updated TextExpander shortcuts for phrases I typically drop into work chat windows
  • Added a number of TextExpander shortcuts for creating future Tool Sharpening posts, largely around standardizing snippets for podcasts for consistency
  • Upgraded my Mac to Yosemite (Mac OS X 10.10)
  • Upgraded home projects to Ruby 2.1.3

Project work

I made a little bit of head way with Issue #32 of my Pomodori project. Being honest, I’m not putting the kind of time or attention to this that I would like.

Skill improvements

Bash

This past week, I was preparing a software release. While we have a good deal of automation around this sort of work, there are some cases where the progression to release gets into a condition we haven’t automated for yet. In one of these cases, I needed to remove git tags we placed on the repositories for the release and further steps in our automated process.

Before, I’d likely just suffer through doing this three or four times, because it’s just at the edge of being worth writing a script. However, my coworker Steve Gambino reminded me that Bash is perfectly capable of solving this issue. It’s also a tool I could stand to get more familiar with for situations such as this.

for i in $( ls -1 ); do cd $i; git tag -d R36.0.2-20141016; git push origin :refs/tags/R36.0.2-20141016; cd ..; done

I ended up using variations on this for loop multiple times and I didn’t have any of the dollar auction costs of, “well, this will be the last time I do this, so it’s not worth writing a script.”

tmux

This past week, I had couple of tmux panes that I wanted to capture the buffer for and paste into BBEdit for separate examination. Rather than tediously scroll and copy and scroll and copy, I searched for a better way. As it happens, thoughtbot developer Chris Toomey had some additions to .tmux.conf that are very helpful for this sort of situation. Perfect.

Screencasts, podcasts and presentations

Photography: New York (2014)

Robin and I took a vacation to New York, covering New York City for a weekend and upstate in Accord in the Catskills at the tail-end of September. It was absolutely gorgeous and I have four growing sets to show the trip:

Some of the images, notably some of the foliage pieces like the one above, will be for sale. Drop me a line if you’re interested in purchasing a print.

Tool Sharpening: Oct. 11, 2014

For some background on what’s going on here, see the first tool sharpening post

So, it’s been a little while since my previous entry. I’d like to thank a 10-day out-of-state and substantially offline vacation for that. I have been posting photographs from the vacation, over on Flickr.

Anyhow, before I left, during and after vacation, I have been able to do some technical self-improvement.

Environment + Process tweaks

  • Added two more smart folders in Mail.app
    • One shows me all mail that I don’t have filters for that’s new within the last 48 hours
    • The other shows me items still in my inbox that are older than two weeks, which I want to serve as a sort of “drop dead” period. If I’m not getting to it by that point, I’m not likely to get to it at all. Archive and move on.
  • Improved my incoming email filtering so fewer automated messages hit my inbox

Project work

There’s been little progress on account of the vacation work, however, I did start on implementing the service object for adding a pomodoro in my Pomodori project.

Skill improvements

  • Learned about Control-R to search through previous commands. I’d been using history | grep <cmd> for years, like a chump
    • This works, but Control-R is more efficient a lot of the time for

Articles read

These next two pieces are vitally important not because they relate to the technical craft of our industry, but the rather awful state our collective social craft is in within this industry. While we’re great at technically building social spaces and connections online, we’re really crappy at understanding how those same tools can be severely abused and mitigating that abuse. These two pieces are two of the saddest and troubling I’ve read. I highly encourage you to read them and reflect on them.

Screencasts, podcasts and presentations

Tool Sharpening: Sept. 15, 2014

For some background on what’s going on here, see the first tool sharpening post

For this and following editions of my tool sharpening series, I’ve set-up five different sections below. I’ll explain them briefly:

  • Environment + Process tweaks will be for anything like my tweaks to BBEdit, vim, tmux profiles, helper scripts and similar changes
  • Project work will cover personal project work I do, since my primary motivation for that work is to learn
  • Skill improvements
    • Work with code kata, koans, exercism.io or similar
    • Typing practice
    • Other deliberate skill practice work
  • Articles read will be for links of interest I come across from Twitter or mailing lists
  • Screencasts, podcasts and presentations will enumerate audio and video media that I’ve reviewed. Expect this to be Ruby Rogues and Ruby Tapas heavy.

Environment + Process tweaks

I have a Getting Things Done-style Weekly Review that just hasn’t been working for me for a little while. Many weeks, I simply look at the weekly review in OmniFocus and mark it complete. It’s important to me, abstractly. But the way I’ve structured it clearly isn’t important to me in the concrete terms of actually doing it.

To that end, I’m hoping to move some of the big scary bits out of the Weekly Review and into a work day Daily Review I have been far more consistent with. Those pieces are to:

  • Process email from the last 48 hours for further action or file it
  • Review anything I added to OmniFocus in the last day
    • I have a perspective set-up for just this purpose
  • Review anything I added to the OmniFocus Inbox so it has a context, a project and a next action

Project work

I’ve been stuck recently on my Pomodori gem project. Namely, I was getting to the point where I felt like I was working too hard to make the command line interface work with Behavior Driven Development. So, I idled on the project for a few months.

Thankfully, the work project I’ve been working on has helped me identify where I could close some of the gaps between what I want to do and how to do it intelligently, so I’ve started back on that project, hoping to get the first version wrapped up before too much longer.

  • Worked on Issue 28 of my in-progress Pomodori gem
  • Put Issue 28 on hold and began work on Issue 30. Once Issue 30 is done, I can come back to Issue 28.
  • After review, opened up a new milestone and several smaller issues and closed Issue 30

Skill improvements

Avoiding module and class namespace collisions

So, the most interesting thing I learned this past week was about the purpose and use of the :: ahead of a namespace in Ruby. At work, my team and I are working on a automation our release preparation, which covers everything from triggering software packaging to building tasks and sending notification emails. For an audit trail piece, we want to log several of the steps to our team chat. And, instead of writing everything to target a third party object directly, I wanted to wrap it in an object that was part of our application’s domain.

So far, so good.

However, I soon saw an unexpected error, along the lines of ReleaseAutomation::Flowdock::Flow not defined when what I was trying to do was instantiate Flowdock::Flow within ReleaseAutomation::Flowdock. It took a little bit to find the right search terms, but I found a Ruby Best Practices post covering modules and namespaces. In that post, I found I needed to invoke Flowdock::Flow as ::Flowdock::Flow to tell Ruby to go to the top of the namespace tree vs. trying to match Flowdock as an abbreviated namespace in my project domain.

Articles read

Screencasts, podcasts and presentations


Looking back, I’m pretty happy with what I was able to learn this week.

Tool Sharpening: Sept. 7, 2014

For some background on what’s going on here, see the first tool sharpening post

The time since my last entry was primarily spent reading blog posts and watching screencasts vs. writing code at home. I’m totally OK with that.

← Previous