95 karma · joined April 7, 2015
After a number of emails to sports memorabilia auction sites and a university historian, I was able to identify it. The Super 20 Club was a term for the members of the press/media who had attended the first 20 Super Bowls (amazingly, there's a Super 50 Club). They received sets of one decanter and six crystal old fashioned glasses. Interestingly, the recipients had their names engraved on the decanter, not a team name. One expert I contacted hypothesized that the previous owner of the decanter was a noteworthy (ie celebrity or friend of the team) season ticket holder, who had Giants season tickets for the first 20 years of Super Bowls. It was probably worth about 100 bucks to the right buyer, but sadly broke in an accident some months later.
I've also found a football autographed by the '82 Patriots, a Nighthawk X10 router, and some high-end kitchen appliances. I never spend more than 10-15 bucks per-item as a rule of thumb.
Your point makes sense when the full functionality of the phone is taken into account. I was viewing the argument as phone camera vs dedicated camera.
There's a whole other rabbit hole when you get into the discussion of whether the camera or the lens is the primary driver of good photography.
If a smartphone camera is a Toyota Corolla, a nice camera is a basic luxury sedan for Sunday drives. It does everything a little better, but it's a bit pricier for less use. That being said, it's really for people who just like to drive.
Right now I wear an Oris 65 daily and I have two Bulovas (Lunar Pilot & Accutron Spaceview) for different occasions/outfits.
Edit: Also the industry would affect things, I imagine
I'm also actively developing a social web game where players work together to build a story by submitting words and voting in a common word bank. One of my servers is down right now so I don't have a playable link, but the game (and domain) is Rauk.us and is connected to an associated Twitter account that shares completed "stories" (@Rauk_us). I'm aiming to have the game back up next week. Developed in Node.js with Socket.io for real-time gameplay.
I've also designed & developed multiple commercial releases in the digital space (i.e. Steam + Itch.io), but since those are past projects I'll leave them out.
Feels like a healthy enough balance.
In terms of self-education, I would recommend to play as many games as possible, and play them twice. The first, as a player: develop an emotional connection with the experience. The second, as a designer: look at everything under a magnifying glass and never stop asking "why did they do this the way they did?" Hope that helps, just my 2 cents.
With an interest in comic books and cartoons, I began practicing animation in the margin of my paperback books. Flip-books got me interested in Flash, and I spent some years learning basic frame-by-frame animation. Setting up menus and basic playback controls opened the doors to ActionScript, which got me started with choose-your-own-adventure animations. As I experimented with basic game mechanics, I started to play more games, and eventually turned to Java to learn "real" programming, where the concept of game loops and loading external images was introduced. After practicing on and off for years, Unity appeared and opened the doors to 3D game development (I was taking a computer graphics course in college around this time as well). I took some time to read up on level design, since I never really worked in 3D space prior to this. Since then, I've picked up bits and pieces of incorporating stronger media (textures, music, sfx) and polishing the user experience (more attention to the GUI and overlays). Most recently I've added analytics and other metrics to improve my understanding of how users behave. Funny enough after all that, now I'm designing tabletop games.
That's my journey, at least.
Comic books -> Cartoons -> Paper animation -> 2D Digital animation -> Scripting games -> Developing games -> Using external assets -> 3D games -> Level design -> Low-level concepts -> Polishing media use -> Polishing GUI -> Analytics -> Tabletop