jhaitsma

One often-overlooked aspect is that for business purposes, the first priority is to have something that gets the job done. Release early and often, then iterate towards perfection - but only for what your customer wants.

This generally means that its not great, but it works. If time permits, it is great to tidy / refactor bad code, but this is not always possible. Reminds me of an item posted a couple of weeks ago - "confessions of a terrible programmer"

That is exactly the point, however last year I had an existing .NET build that I wanted to port over to linux - it was developed with VS2005 / .NET 2, so should have been fairly trivial to port.

The issues I ran into were many (eg windows forms, data access being not or only partly implemented) so I just gave up and ran the original .NET in a windows virtual machine, rather than mangle it to work with gtk#.

So in principle it is an ideal idea that in practice has many issues due to MS driving .NET development and MONO having to play catch-up and then attempt to mangle the windows-specific code to be cross-platform. YMMV.

Really depends on the day - if I have a lot of interruptions, my "flow" consequently gets shot, and the work I do goes downhill considerably.

However, when I have it going on, I can stay focussed for 2-3 hours at a stretch without needing a break, but generally then my eyes start pointing in different directions. After a short brak / walk outside I can generally pick up where I left off and be good for another couple of hours before I run out of steam...

Funny thing is that if you have the alternative (ie clock-wise rotation) then the left leg is on the floor.

Anyone know more about this interpretation flipping? It's kinda weird, and makes me wonder if people that have lost the use of one eye ever have this kind of thing happen in real life.