253 karma · joined March 22, 2010
The sign-up process was so in-your-face and demanding I gave up and never came back.
(I'm male, if that makes any difference or relevance).
"Use Nautilus or Thunar?"
I imagine the story behind this is that half the Linux devs preferred the first, and half preferred the second, and so instead of the distribution having the balls to choose one, they forced they choice onto the user.
For the average user however, the choice read as:
"Open Mystery Box 'A', or Mystery Box 'B'? Warning: opening the wrong box will mean that many of the things you try to do simply won't work!"
Choice here is very bad: it makes the user feel powerless, yet simultaneously assigns blame to the user in the event that things go wrong.
1. Submit bug report. 2. Wait six months. 3. MS tech will post a comment, "this will be fixed in the next release". 4. Wait two more years. 5. Bug report will be closed as "won't fix".
(I'm a Haskell beginner, currently experimenting with using Scotty, Persistent and Esqueleto to make a web API - and these articles have been so useful to me - I'm finally getting my head around monad transformers, using them to extend the standard Scotty one. Proud moment for me.)
It had a "barrel shifter" that gave you free shifts of powers of two, so you could calculate screen byte offsets quickly:
// offset = x + y * 320
ADD R0, R1, R2, LSL #8
ADD R0, R0, R2, LSL #5
// = 2 cycles
It also had bulk loads and stores that made reading/writing RAM cheaper. The trick there was to spill as many registers as you possibly could, so that you could transfer as many words as possible per bulk load/store. LDMIA R10!, {R0-R9}
STMIA R11!, {R0-R9}
// Transfers 40 bytes from memory pointed to by R10 to memory pointed to by R11,
// And updates both pointers to the new addresses,
// And only takes (3+10)*2 = 26 cycles to do the lot.
Happy days...Without an allotment, employees will generally take a sick day when they're actually sick. Sometimes you'll notice someone who seems to take a lot of sick days. In that case you want to have a friendly chat with them - it's almost never the case that they're just taking free days, rather it's almost always situations like: they're not happy for some reason, they need flex working, they can't afford to repair a car and the commute is worse, they're suffering stress, etc etc. In other words, things it is useful to know about so you can help them (and hence help the company).
Sick day allotments are a way of ineffective managers avoiding confrontations with people: they just end up punishing everyone.
Otherwise, I end up having this conversation (which actually happened):
Him: <Big Client> is having troubles! Features X, Y, and Z aren't working! Me: Hmm, has anything changed? It was all OK on Friday. Him: No, nothing's changed. Me: Really? Him: Well I ran a bunch of scripts on Saturday while I was visiting them. Me: OK, so what exactly did you run? Him: Just a bunch of scripts.
(Another great resource is the ideas magazines they used to print - not sure if they still do - with loads of pictures of creations, but with minimal or no instructions).
Back when I was a teenager, I wanted to write an art package for an obscure computer (Acorn Archimedes). I wrote the first version in BASIC, then decided to re-do it in assembler. The assembler I first used couldn't cope with the size of the project in the end, so I wrote my own assembler; at that point I discovered C, so wrote it in that. Unfortunately the C compiler I used was so full of bugs I decided to port LCC to produce ARM assembler, but then I needed a linker, so I wrote that as well. Got it all working lovely to the point where it could compile itself.
At university I figured Intel PCs were more useful than my obscure computer so... I forgot about it. Lost it.
And to this day, I can't help but wish I still had it... I had written, and lost, a complete C development system, faster than any of the other compilers/linkers I tried, small footprint (it had to fit in a machine with 4Mb RAM), and ARM chips are now everywhere. Damnit!
So please... save your work.
http://en.wikipedia.org/wiki/Metrication_in_the_United_Kingd...
One major way in which metrication is being introduced properly is via schools - nowadays schools generally only teach the metric system, and the generation below me genuinely do weigh themselves in kilos, and measure themselves in meters.
On a similar note, in the UK, where most people have manual gearboxes, the advice for an emergency stop used to be to jump on the clutch and the brake, to prevent stalling. Nowadays you're taught just to stamp on the brake: in an emergency, who cares if you stall? Pushing the clutch can lead to the car "surging" if going downhill, so why risk it?
Very often, the most efficient evolutionary search algorithm involves a population of one (or two, depending how you count them): generate a mutation, compare it to the current best. If it's worse, throw it away; if it's better or the same, keep it and throw the original away. Rinse and repeat.
Search for "neutral networks" for more information about research into determining the "shape" of the fitness landscape. (Unfortunately, Google throws in plenty of search results about neural networks and network neutrality).
Instead the video stood out as a black box - it looked a little incongrous just 'stuck there' in the middle of the page.
Microsoft had the software stack ready - imagine if they had released (via partners) high-dpi laptops and screens shortly afterwards? That actually might have made a Windows machine a compelling and desirable product, instead of just an expensive way to run a browser.