The other day, I was watching Ted Ed’s collection of YouTube videos on riddles and came across this interesting logic puzzle described as “Einstein’s Riddle”. Einstein probably didn’t make up the riddle, but the problem itself is kind of interesting for a few reasons. You can either watch the video or keep reading for a retelling of the problem below.
Let’s take a look at a problem. We have a webapp to track build times for a continuous integration (CI) server. The main page has an HTML table with dozens of rows (one row for each build) and each row has an entry for the creation time of the build and the length of time it took for the build to be deployed, tested, or whatever else you’re doing with your CI server.
For most rows in your table, the duration can be populated with information from the server. The server sends back a creation time, and if the build is finished, a finishing time. Both the creation time and finishing time are specified in a milliseconds version of Unix time. The duration is easy enough to calculate. Firstly, in Angular we would opt to use the
ng-repeat directive to display the data in a table:
I spent the better half of today debugging one of my current projects, an Android app designed to help users do things on their phone faster. Vague, I know.
The issue at hand was a
java.lang.IllegalStateException resulting from a fragment not being attached to its activity. Reproducing the bug was easy. Launch the app, search for a YouTube video, back out of the app, and search for another YouTube video. The app crashes. An easy ‘solution’ was to check
fragment.isAdded() in the
onVideosRetrieved callback. Of course, the real problem is that the fragment still wasn’t attached to an activity.
This week on Hacker News, a game called 2048 rose to the top of the front page. Subsequently, productivity at software companies everywhere dropped tremendously.
The game itself is quite simple. Use the arrow keys and get the numbered tiles to combine over and over again until you get a ‘2048’ tile.
The game is partially (read: very) luck-based. When the board is getting tight, a single wrong number, or a number popping up in the wrong place, can mess you up for the rest of the game.
So I spent the last couple days tweaking my Octopress themes and relearning how to do things since not blogging for a while and getting a new MBP. Navigating the Octopress file hierarchy isn’t easy, but hopefully this post will help you (and be a useful reference for myself).
Originally posted June 23rd, 2013
I was at a grocery store a couple weeks back, and over the PA system, I heard the lyrics “we are, we are we are, we are we are”, and for some reason, I thought it was catchy. It sounded like Kesha, so I had a starting point for searching (and I was too embarrassed to use Soundhound/Shazam in public to recognize the song).
This post was inspired by a fellow software engineering student at UW. If you want even more detail than I’m providing here, check it out.
Last updated December 29th, 2013
Here’s a quick list of the courses I’ve taken (the full curriculum can be found here):
So after only a few months of using WordPress, I decided to switch to Octopress. I decided to make that obligatory post that every new Octopress user writes. It’s some sort of rite of passage, I think.