Uncategorized
I wrote an API
Just as Gary and Wayne talked about not building an API, I did it.
The API returns a random graffiti image from a database I have: http://publicartfound.herokuapp.com/get_graffiti
The API return a JSON object containing a URL to a graffiti image. It looks like this:
{
data: ""https://s3.amazonaws.com/lkbg-aws-box/10790544143_0b07aab385_o.jpg""
}
Although this isnt keep score correctly, the quiz game is cycling random images.
Rule: Dont start coding at 12:30am
Incomplete prototype is live here: http://publicartfound.herokuapp.com
Code is here: https://github.com/rememberlenny/publicartfound
I talked with Nick today and decided to build out a graffiti game. This is a tool for encouraging people to build out the community’s content for the New Public Arts Foundation projects.
Im creating a system to encourage people to help identify the artists of the graffiti images I have. This is traditionally a tedious process that I dont want to do. I am creating a competitive platform for people who like graffiti to partake.
The game operates on a basic mechanic. Reward correct annotations, reward speed, and punish incorrect answers.
The mechanics of the game determine “correct” answers based on community’s majority.
Technically, I am leaning on existing code. I am using the Firebase service to store all my data. Im using poor jQuery and HTML for my single page web application magic. Basically, its spaghetti code. I don’t care.
I started with a basic To Do MVC project. I grabbed some Leaderboard code. And Im putting it all on a page.
Next, Ill add a randomized graffiti image. Ill also add the proper point system. Lastly, I create a chatroom, so people can talk shit.
Basic To do MVC thing:
The leaderboard code:
The basic framework + working leaderboard:
I made this when I was 14
Cookies for follows
We are encouraged to build platforms rather than software. We are encouraged to do things that wont scale.
The platform concept is great, but where do you start with that?