411 karma · joined September 13, 2010
email ian [at] testdriver.ai
Turn your phone into a remote control for the web. Works with:
- Youtube - Spotify Web - Hype Machine - Vimeo - Pandora - Rdio - SoundCloud - Grooveshark - Plex - TuneIn Radio - Google Play - Twitch.tv - Last.fm
--------------------
Photoshop download resources. 15,000 visits / month.
--------------------
Wake up call alarms personalized with Facebook, Twitter, Reddit, etc.
--------------------
Email me if interested: ian@meetjennings.com
The slice tool represents the direct transformation of raster image to website. We all know that this isn't possible anymore because of mobile, retina, etc.
But Photoshop and image editors still provide tremendous value to the web development process for mockups, image assets, colors, etc.
What this article is trying to say is that the process of turning a design into a website has become much more difficult. A PSD is no longer a final deliverable but the beginning of a conversation.
Now design needs to be functional. Instead of taking the static image you get from a PSD, you need to ask "What does this look like on mobile? What about huge resolutions? What if we don't have that content?"
The article suggests that this process will be improved by designing in the browser thanks to CSS3.
The truth is that the browser has just barely hit the minimum requirements to be able to make design decisions. Have you seen the Chrome color picker? It's alright for choosing a border color but final design work can not be done entirely in the browser just yet.
Some people were questioning if these emails were real ("who tells their professor they're slacking?"). I have always chosen to communicate in an open and honest way.
I'm particularly happy that I was able to dig up this email because it paints a great picture of our early hustle. We would find hackathon events any way we could and RSVP right away. Much to our surprise, not every hackathon has a place to stay overnight, so we often ended up crashing on our friend's couches. In one specific case I remember pushing 8 chairs together to form a bed.
At the first hackathon we released Hacker League at, our friend challenged us to sign up 10 events.
When I presented the company to this class I remember ending the presentation with "This is a real company, and we've run 13 events to date." The professor shouted that that was "a success" and that I should be very proud. Since then we've powered hundreds of events.
At the time it wasn't clear if we were developing an app for hackers, people who were interested in hackathons, organizers, or just anybody in tech. We weren't really sure what we were building, just that we wanted it for ourselves.
I think a key part of our success was determining a market and sticking with it (thanks professor). At some point we declared Hacker League as "a platform for hackathons" and although the site was used by everybody in attendance, the focus was on organizers. If the organizers used it, so would the attendees.
A huge benefit of the hackathon format that for every hackathon we attended, there were a few people in the audience who were either organizers or thinking about organizing an event. This helped the site go viral within the hackathon community.
You also might remember me from Mote.io, an app I launched a few months ago on HN. http://mote.io
I agree that there is thin line dividing the positive or negative sentiment towards schooling here.
In some ways school was incredibly valuable, I met my co-founders at Rutgers and this class specifically helped develop the company.
At the same time the classwork was getting in the way and I needed to push it aside to help get the company off the ground.
"Mote.io, Pandora 'The rolling stones'" or "Mote.io, play Hype Machine popular page."
Does this mean they don't give a shit about experience? No. It means they want to have a large reach without much maintenance. After that is accomplished, then they can worry about experience on a per device basis.
I don't believe it's correct to just dismiss this as garbage because the application is currently buggy. The entire idea of this approach is to improve the experience across all devices, but for now they are limited because they are still on the first step, implementation. Also note the slide that says "betting on the browser," meaning that Facebook is betting that issues between platforms will eventually fade away.
http://help.github.com/win-set-up-git/
Your site should try to provide a very linear guide for new users.