tcopeland

"What writer? We're talking about a sitcom!"

https://youtu.be/EQnaRtNMGMI?t=108

Martin Crevald has a book on the USMC reading list (https://grc-usmcu.libguides.com/usmc-reading-list/intermedia...) "The Changing Face of War: Combat from the Marne to Iraq". Interesting that he uses that battle as one of the fenceposts.

Another scenario is when an acquisition occurs for the data a company has collected and so the codebases are quietly retired. In that situation there's still some value in paying down some technical debt - security updates on libraries and whatnot - but there's a point at which the decommissioning effort becomes the primary driver.

Maybe Mary Rose Cook live coding a game as a conference presentation:

https://vimeo.com/105955605

FWIW "The Box" is on the current CNO reading list:

https://www.navy.mil/ah_online/cno-readingprogram/hvo.html

That's the truth. I had a thing come up the other day where a client wasn't including a content type header and thus the body was being interpreted as application/x-www-form-urlencoded. Rack middleware to the rescue on that one.

"Nudge" is on the Center for Homeland Defense and Security reading list:

https://www.chds.us/c/hsbooks

> I'd definitely include "Kill your dependencies" as a bullet point

Or at least your monkeypatches!

I was always disappointed by rails:update - look at all these crazy changes, I can't do all this stuff! - until I figured out I was using it the wrong way. A good way to use it is to run it in a different branch and then scroll through the diff, picking out items that you want to update. This lets you pick and choose and do even that incrementally, so you can do some easy ones first (like removing unnecessary MIME type registrations) and then move on to more complicated ones.

Longer writeup is at https://thomasleecopeland.com/2015/08/06/running-rails-updat... - it's 3+ years old now, but, hey.

That looks great, and my local library has a copy, thanks for the pointer!

Here's a direct link to the PDF:

http://www.benning.army.mil/armor/316thCav/ASA/content/pdf/A...

Interesting, that's on the Army Advanced Situational Awareness reading list (http://www.benning.army.mil/armor/316thCav/ASA/ReadingList.h...).

In the "things learned from Ruby" section:

  Focus on strong object oriented programming

What I've learned from Ruby is to favor functional programming concepts - minimize side effects, isolate state mutation, etc. Ruby is definitely OO, but when my Ruby code is more functional it's less buggy, easier to understand and move around, and generally less convoluted.

Yes, although many changes are performance optimizations and other under-the-covers sorts of things. Here are the changes for 2.5 which if tradition holds will be out on Christmas:

https://www.ruby-lang.org/en/news/2017/10/10/ruby-2-5-0-prev...

> I'm planning a full rewrite of the interpreter for Ruby 2.0 [...] It will use a bytecode engine.

And so it did! https://en.wikipedia.org/wiki/YARV

In the morning, usually setting things up for whatever operations are scheduled for the 0800-1200. In the evening, squaring things away from whatever we did that day and maybe prepping for night helo ops.

That an interesting watch rotation to stand. At first I dreaded that one because you get less sleep. But the upside is that 0400-0800 is a quiet time aboard a ship, and 1600-2000 things are usually winding down as well.

And if you're standing that watch that means you're not standing port and starboard (i.e. 4 hours on 4 hours off) so, could be worse!

Yup but coverband doesn't do code coverage during tests (like simplecov); it does code coverage in production by sampling requests and profiling them.

Seconded; this was a good one. It was on the 2014 U.S. Navy reading list.