andersnolsen

I believe the biggest problem is due to the design of bike lanes. They are often narrow and squeezed between car lanes and car parking. Due to this design bike lanes are also more often subject to being blocked by construction and forced to merge with car traffic. The visibility on bike lanes are way poorer than regular car lanes due to the above factors. In cities you also have to deal with the loading and unloading of goods. This means large, tall vehicles blocking the sight and often crates and people moving in your lane.

How often do you experience your whole lane blocked by the content of a whole appartement?

In Stockholm where I live snow, and ice make bike lanes hard to see and also makes them inaccessible.

I really agree that you shouldn't keep a speed where you can't control your vehicle, but so common design flaw puts an unreasonable amount of responsibility on the biker compared to heavier vehicles misusing the bike lane.

I'm a bit puzzled

Without any open content it's hard to validate if it's worth subscribing.

Did you check out the meteor package "spiderable"? It might need to mature a bit but it might do the trick

I'm sure you'll have no problem finding a job now. Great work!

Small thought - when you're moving an object, wouldn't it be logical to also allow for small step moves with the arrows?Now it will move the camera position.

Only one thing to do - test

The author couldn't be more wrong. Eating animals is always wrong. Would you eat your own dog? Or little brother? They are made of meat as well. I wouldn't eat my own dog and my little brother, well, if he was a gingerbread boy maybe.

I totally agree. Why emulate sketching when you have pen and paper? Why emulate browser behaviour when you can code? Sketch on paper, learn some HTML, javascript and use a framework.

I'm working with very simple HTML and Bootstrap. I also use JSON files with actual data and some simple jquery to populate and handle states. After a while you'll get a library of HTML snippets, javascript code and dummy content. You'll work quite fast. The result is much closer to the truth and you might actually be able to re-use some of the stuff you've created when you build the actual app.

I've been using Axure and Balsamico which are quite good tools, but I find myself getting stuck and wasting a lot of time on emulating behaviour which is quite easy to code.

I carry a contractors cliboard in my bag with a stash of regular- and graph-paper (I print them - http://konigi.com/tools/graph-paper), especially like the dotted versions. I shuffle the new sketches and ideas to the back and clean them out once in a while. I do a lot of sketching as well so it's easy to add a clean sheet on top of my latest sketch and re-draw, test various poses and expressions. I've earlier used regular sketchbooks, but I find the contractors cliboard better. Gives you a solid board to put on your lap while commuting, you can easily discard a paper and start fresh, and it let's you store. Also - single sheets of paper is always avaiable.

A great point with using paper is that anyone can draw on paper. Just take out the contractors board, give your co-worker a pen and you're creating something together.

When I'm on the go and have some good ideas lying around I might shuffle them in with the other paper just to develope them further when I get a slot. The good ones get photographed and stored, the not so good I try to give a second round of thought and fresh sketches. If that fails it's straight to the bin.

I also keep a simple notebook app in my mobile which I use just for ideas. Lately I've been testing Trello and also Hollyapp.com, task tracking for nerds. I like the markup syntax of Hollyapp. Very fast to write. I like splitting my ideas to managable chunks and todos since I in the moment of the idea often have a picture on how to accomplish it. I'm writing more and more Markdown for this

A lot of credit to Mårten Agner http://angner.se/ for the sketching techniques I use daily.

Thank you. Very inspiring!

Amazing game. You could easily charge 8-10$ for it. Maybe more with the right marketing.

I'm not sure about the cut-scene advice. Yes - I can see you loosing players but It's part of what makes this game feel very retro. Sure, you could tweak it a bit and do the cut scenes a bit shorter. Also you should add an option of skipping the cut-scenes alltogether. I did a replay of the first part and would happilly trade x-x-x with a single escape press.

Agree with the @reitzensteinm. You should have visual reaction to hit. I was kind of expecting it since you had a lot of other visual effects such as screen shake etc.

You've done an amazing job. Do you have a twitter account we could follow? app.net?

Not bad but it needs some more testing. After some up and down scrolling with home, end, page up and down it totally blew up in Chrome.

Excellent app! I've been playing around with it for an hour now and can really see myself using it.

Inline editing is the one feature i miss the most. Also the tree list is a bit hidden. If they were visible you could switch faster betweem them and setup the app as a lightweight project management tool or issue tracker. Just add your users, milestones etc as own trees and copy/paste between them. Also a syntax like: (someissuenumber) ... which renders issue number in front of the line would make it kick-ass.

Great job!

There are so many reasons for using jQuery. Myself, I'm using it for a ton of reasons: speed up development, create more compact and readable code for myself and coworkers, enjoy the huge range of plugins, theming... you name it. Support for IE-ancient is not on my list. Actually I would love to see it gone, die, disappear, vanish.

Even though jQuery handles most of my cross-browser issues I still have to test and worry, create workarounds and lots of additional code, consider it in my architecture, take care in the design and handle it in the application lifecycle.

I have been looking for and at able framework that DON’T support old browsers. Thank you for not supporting IE-ancient in your 2.+ releases, I will continue using you jQuery!