Food in SF

Feeding a growing programmer


I am lucky, in some ways, that I can’t find affordable housing here in San Francisco. Currently I am sleeping at a hostel and spending every waking moment at MakerSquare. Literally from about 7am until I walk back, usually after 1 am, I am at MakerSquare. With 2 exceptions, lunch and dinner. This brings me back to why I am lucky…ish, I get to eat out every single night, and I can’t feel guilty about it because I am still spending less money than if I rented a 1 bedroom apt, with a roommate.

on the other hand I share a room with 7 other people ☹

As for programming, I last left you with a thrilling tale of sql database integration. Well we finished that in a few days. Now we are beginning with a group project, I will be working with Jon and Gideon. Our job is to build a web app rock paper scissors game, including a database. So far we have the game logic pretty well figured out, that was pretty simple. Now we are working on building the models for the database.

something like this I hope

As another part of this project, we are building cookies, but in Sinatra they are called sessions. This will allow a person to login and navigate multiple pages without being signed out. The final portion of this project is to construct Transaction scripts that allow our User input to communicate with our server without a breaking error.

Something like this?

In general the basic form this program, and from what I understand most programs, is as follows. User Interface, in this case we are using erb, html, and css with help from foundation to make things pretty quickly. We are using Sinatra to build our server an host the site pages on our own machines so that we can access it through a browser.

Then we have the transaction scripts, these are basically pass fail tests that we write, to test the user input and order to confirm that the input is correct for the program, otherwise we throw an error. Then we have the game logic, which is really simple, and the models for the database which we are storing as classes in Ruby.

We then built an orm in ruby, which acts as a filter and translator for our database. We pass information through our classes and activate the orm to either pull information from the database, or push information to the database. In this case we are useing a postgresql database.

Sometimes I am amazed that I understand what I am saying.

Inn essence we have a frontend, a buffer between the front end and the main logic of the program, then a buffer between the main logic and the database, and finally a database.

Which, as you can see above brings me back to food. In case you couldn’t tell by the title, I am hungry, time to see if the thai food restaurant around the corner is as good as I hear.

Email me when Jered McCullough publishes or recommends stories