stusmith1977

Wouldn't it have been more sensible to do the launch from somewhere nearer the edge of the earth?

I tried pinterest a while back (so apologies if it's changed since)... I remember the sign-up process was awful. Part of the sign up process forces you to follow a certain number of other people. I just wanted a blank page to start adding to. If I'm signing up to something "social" with my name attached, I don't want to be forced to publicly follow other people/groups that I haven't fully checked out.

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).

What was always worse was that the choices never came with any explanation. I remember a while back trying some flavour of Linux or other, and during installation it asked (paraphrased):

"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.

And on desktop too. Page up / page down keys don't work unless you focus the page. There is a scrollbar within a scrollbar.

In situations like this, you can report the bug to Microsoft Connect:

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've found the "24 Days of Hackage" series incredibly useful - each day is a brief introduction to a useful Haskell library, many of which show off features of Haskell that aren't available in 'standard' languages. Even better, each one comes with working example source on GitHub, so you've got a starting point if you do want to experiment.

http://ocharles.org.uk/blog/

(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.)

http://en.wikipedia.org/wiki/United_Kingdom_insolvency_law#U...

and

http://en.wikipedia.org/wiki/Trading_while_insolvent

I can't remember how tight I made it... but I would think you need a couple spare: one for the number of iterations, and another for the screen stride. But yes, spilling registers like SP and LR is a useful trick if you need it.

Reminds me fondly of the time I was writing assembler for the ARM2/3... it had such a nice instruction set that made hand-writing assembler pleasant.

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

  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.

Surely open-source handset OSes are just as vulnerable to patent attacks? If Firefox OS were to take off, it would immediately become a target for exactly the same sort of lawsuit.

The article compares to other first world countries, where I seriously doubt there is a problem with (under-)reporting infant deaths.

It's not just kids who are reassured by cosmetic changes. MRIs used to be called NMRs. People freaked out because of the word 'nuclear'.

The problem there is the word "allotment". How can you allocate in advance how many sick days to give? If you allot (say) four days sick each year, and an employee is sick three times, surely the rational choice towards the end of the year is to "use up" that allotment?

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.

Does "verbatim" mode approach what you need? Google won't attempt to guess what words it thought you meant in that mode.

Judges flaunt the law, surely? I mean, if you're wearing a huge wig and robes, you've got to be flaunting something.

The press could mention it, that would be a start. BBC news for instance barely mentioned the proposed blocking. The only stories to hit the front page (and then, right at the bottom in the Tech section) were the links to Huawei and the spat between the minister and the reporter. The actual proposed block has barely been mentioned. Apparently a baby being born warrants continuous headline coverage; loss of civil liberties gets a footnote.

And in fact, writing scads of dumb code is often the sign of a poor developer. It often follows from the "never turn back" mentality, that leads them to follow an initial poor choice of solution through to the bitter end.

Steam Cloud Sync can be a bit flaky at times, which is annoying when you play something like Civ V on multiple machines.

I'm going to add step 5b - save what SQL you executed (against what server, and for what reason), ideally in source control, as an audit trail.

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.

Lego Education does a spare parts catalog - but not sure if you can buy from it as a private individual. I used to use something similar when I was a kid - I couldn't afford (say) a complete new pneumatic set, so I just bought a pneumatics parts pack from a mail-order catalog and used those bits with my generic technic stuff.

(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).

I'd add one more thing to this article: don't throw these projects away, even if they seem failed/doomed/incomplete. Store them somewhere. Back them up. Whatever. You might need them.

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.

The UK did use legislation to gradually switch to the metric system, with certain exceptions.

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.

The selling point would be that you might only need one car instead of two - which would make 25k more attractive than 2x20k. The use of a self-drive car isn't that it drives you to the office, it's that it drives itself back home for your partner to use.

Agreed. As I understand it, these automatics kick in when there's a certainty of a crash ahead if no action is taken. In those circumstances, it's better to avoid the certain crash and take a risk on a uncertain shunt from behind.

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?

I vaguely remember there was some discussion of this in 'Metamagical Themas' by Douglas Hofstader. It's been a while since if I read it, but if I remember correctly he drew some parallels between law and provability in maths - basically, you can either have a system of law which cannot cover everything you want to make laws about, or you have a system of law which does, but which has some undecidable laws. Feel free to correct if I've misremembered.

Hearos ( http://www.hearos.com/ ) do a really nice range... I find their foamy ones amazing, comfortable and blocking even quite load noises.

Bingo. So many genetic/evolutionary algorithms assume you need a large population with crossover to avoid these supposed 'local minima'.

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).

I've got a Lenovo G770. Not particularly pretty but seems solid and has a nice big 17" screen for a decent price. I dual-boot Windows and Ubuntu without problems.

It's a shame the website had a white background, and the video had a black background. The borderless, chromeless video could have looked awesome if it had the same background color as the webpage itself - it would have merged in nicely.

Instead the video stood out as a black box - it looked a little incongrous just 'stuck there' in the middle of the page.

It's a chicken-and-egg situation, agreed, It just seems really strange to me that they spent so much effort pushing and developing the software side, without putting any effort into the hardware, when the two clearly have to go hand-in-hand.

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.