27 karma · joined December 1, 2010
I’m a web developer doing frontend (Javascript, Coffeescript) and backend (Ruby, Rails, node.js, PHP) work with 7 years of experience and graduated as “Mediengestalter” and Game Designer (Games Academy).
Portfolio: http://www.dievolution.com/projects
mail: thomas@dievolution.com
One thing: keep the dark color scheme, but don't put dark grey links on black background (like one commenter already mentioned here), and increase the line height by a few pixels, makes it a lot easier to read.
The technique has one major advantage over GTD and other systems (and I tried them all...), it is damn simple. You don't even need a tool, just a kitchen timer is enough for the start. The only thing I don't like to do in the standard 25 minutes pomodoro mode is programming. You need the tunnel, and a deep tunnel experience can't be achieved if you are interrupted every 25 minutes. My tip: Try 25 minutes first for two weeks, if you can't get into the tunnel, try 50 minutes, if that doesn't work either, try 1 hour 10 minutes. I found this to be the maximum time I can work fully concentrated. And of course, don't even think about checking your mails, reading HN or watching youtube while in a pomodoro.
Of course, I am a bit biased, because I am currently building a browsergame on HTML5 techniques (canvas and local storage at the moment, but of course audio and video will also be a part) at http://www.breederisland.com. It is really amazing how fast the new javascript engines in the browsers are, if you don't use an internet explorer, of course ;)
[1] http://www.videosinhtml5.com/videos-about-html5/google-io-20...
Btw, outside US, it seems like it is the other way round. I develop rails apps and have trouble finding work at the moment.
Oh, and not to be mistaken, it is totally OK to have these people pay for things that make them smile, Disneyland also takes an entrance fee.
There are so many advantages to go framework, I can't tell everyone: - frameworks are (mostly) under development, so you can benefit from trends and improvements in web development
- frameworks are well tested
- frameworks are more secure. Do you have all holes for XSS etc. closed? Are you sure?
- frameworks have almost always a community behind it, so you benefit from other users knowledge and plugins
- frameworks have plugins. You don't have to write anything from scratch, like DB connections, authorization or file uploads
- frameworks have documentation. Unless you are the sole developer of your app, you really want to have good docs.
Do frameworks have disadvantages? Sure, but I don't think it outweighs the advantages.
I don't include IE6 anymore in my web pages. If it works, ok, if not, well... too bad. In the last year, no customer ever really wanted to have an IE6 site.
The Problem with a site like this from Microsoft is, it is not the normal household PC which is still running IE6. There might be a few, but that number should be close to zero. It is the big companies, who are not switching to a newer version, because they have special software programmed for IE6 with funny activeX elements and big domain stuff behind so they can't simply flip the switch, and if it works, why should they upgrade? They don't want to throw a whole bunch of money at this problem. Thats sad, but you can't do anything about it...
That said, I don't think it will replace mouse and keyboard, because the way we interact with our computer is based on the periphery, the mouse and keyboard. Without mouse buttons, we can't click on something that good (there are possibilities for clicking with a gesture, but it sucks, at least at the moment). We can't type text with gestures, perhaps we have to dance letters? :) So in order to use motion based computer interaction on a daily basis, we need to invent some new interface link between the computer and our body. The Kinect is a very first but also a very good step in the right direction, because it is here, it is open, and it is not too expensive to use it. And it is a lot of fun to play with :)
Generally, it is really hard to get people to send you feedback, especially if your project/startup/tool is intended for not tech-savvy users. There will be some users giving you feedback all the time (powerusers/early adopters) and you should stay in contact even if you don't have something new at the moment
What I found to be useful is displaying a "1 minute of your time to improve the product"-form on the (in this case) applications home page, where every user will go. It is important to add a "no, I don't want to do this"-option, because you don't want to nag your users with a always displaying form-link. Don't do popups, too, they are irritating. Just a small but visible link with a do or don't option and if the user don't want to do it, don't force them again. On my last project, I got almost 20% of the user base to fill out the form this way, which I think is a really strong base for analysing and improving your application/startup/tool.
I chose maps because it has a good api and it is something everyone can interact with. You don't have to learn a new technique, just click, drag and pinch or scroll. It is an unlimited source of interactive backgrounds for the game.
Sorry! If you want to try TRZZL, use http://trzzl.co while the DNS Update is still running.
If you like your job at the startup, you did exactly the right thing, there is nothing better than doing the job you like and even get paid for it.
So my advice is: First, work a weekend with bare ruby, there are lots of good and extensive resources on the web. Second, if you enjoyed working with ruby, try another weekend learning basic MVC Rails. Good resource is rails for zombies (http://railsforzombies.org/), where the basics are well shown, and you can work through this on one weekend. Third, try converting one of your small projects to rails. There will be a lot of hiccups and frustration, but once the first project is done, you will simply love ruby.
I hope this helped you a bit, although I have not directly answered your questions (mostly because the given answers are the ones I would write, too).