Day 11: Blog Agenda

In order to move into blogging about the true DITL of Dev, I have an agenda of topic transition into pure dev talk.

The rough agenda is as follows:

  • Days 1-10 have so far been mostly workout talk, with a slight amount of dev talk
  • Days 11-20 I will be transitioning into full dev talk. To do this, I will be removing the following topics:
    • Morning
    • Weigh in
    • Meal log
  • Days 21-30 will be mostly dev talk with some work out talk here and there

Work out

Soreness before: Minimal, legs/pecs

Activity: Shoulders and Back

Soreness after: Minimal additional soreness



Today I was able to understand more of how works. I am hoping tomorrow I will be able to get additional data from the request.

Part of the reason I have been working through this carefully is because I’m still struggling to find the purpose of So far, it seems like it is essentially a fancy redirect server. As soon as I figure out the master purpose of, I will believe I will be able to work past this much faster.

Rietta Inc

Today I was working on a fairly large amount of lines of conversion from a Sinatra project to a Rails project. I find I get overwhelmed when I get into too big of a hole, so I decided to chop in up into bite size chunks. The lines sorted cleanly in their own controllers, so I moved them into their respective controllers. This took me a decent sum of time because the functions were mixed together, but it will allow me to convert the code from Sinatra to Rails much faster in the future.

One of the things I like to do nightly is commit and push any changes. This prevents data loss on the work I do, in the case of a computer crash, fire, or any other issue. This also allows the company to have the work I accomplished even if I get hit by a bus, which reduced the bus factor of having the code on only my laptop.

To do this, I simply:

git add -A # add all new/modified files to be staged to commit
git commit -m "WIP: Commit message portraying completed work (will be edited later)"
git push # push to git server, which should always be off site

When I am ready to PR in, I rebase squash in order to push the WIP commit(s) together with the finished code and provide a final commit message.