This also applies to professional growth. People often have a hard time receiving negative feedback because they experience it as an attack on their identity/ego rather than as an opportunity to learn.
The ability to take feedback constructively is probably one of the most important traits to hire for.
I met a senior NHS physician who built a very useful and simple mobile information service to improve access to certain services. My understanding was that he funded it himself with help from sponsors and had to do it entirely outside the NHS system.
It probably cost 1/10th of what it would have cost if it had been done through the NHS.
Not to mention that NHS computers are still running IE6 and heavily locked down, making it a poor development environment. Tim Kelsey can encourage NHS staff to code, but the infrastructure to do anything meaningful with that inside the system isn't there.
You can certainly be fully anonymous with bitcoin but care must be taken... Mainly, you need to isolate your change to an identity wallet - a wallet used for specific purpose under a dedicated pseudonym. Identity of the pseudonym is protected by plausible deniability - "I bought those coins on MTGOX, but I sold some of them to some guy for cash on the street corner, that purchase wasn't me"
The more hops through a wallet (which can be created dozens of times), adds more plausible deniability and separation to any purchase.
The purpose of this type of interview question is, per my argument, to get an idea of cultural fit and estimation skills. Like any measure it picks up some signal and a lot of noise, e.g. bullshitting skills. The trick is to combine measures such that the noise largely cancels out while preserving the signal.
If this were the only type of interview question used the points you brought up would be a legitimate concern. Given that it was, in my case, married in a much greater proportion with concrete questions I maintain that it generated unique, useful information.
Traders generally have, prior to entering a trade, the opportunity to think through everything thoroughly and ask for help on the bumps. There are also times when the cost of the time for analysis is so great that a gut, if rough, call is needed, e.g. holding hard drive manufacturer equity as news of Bangkok flooding breaks. Being able to ball-park figures, after issuing a disclaimer about the uncertainty of one's estimates, is also a generally useful analytic skill.
It should also be noted that part of recognising the priority of things to be analysed is the degree by which they deviate from expectations - generating many of those expectations is a form of intuitive estimation.
But, as I said, it's mostly to estimate whether this is a person we'd like to spend 10-16 hours a day near. Constant righteous indignation would probably get annoying as fast as serial bullshitting.
free and open-source software provides teaching opportunities that do not exist with proprietary software, since the background functions of free and open-source software, including its characteristics and programming, can be revealed to students. In these respects, free and open-source software is better suited to arousing interest in computer programming and information technology than proprietary software, where its use is all that can be taught.
The other points from the report:
1. When purchasing new software, free and open-source software and proprietary software are to be considered on an equal footing, with the object of always selecting the most favourable purchase.
2. Every endeavour shall be made to choose software based on open standards, regardless of whether the software in question is standard or bespoke (custom-designed). Generally, software which is free for anyone to use is also typified by open standards.
3. Public bodies shall endeavour to avoid any undue dependence on particular software manufacturers or service providers. The utilisation of free and open-source software is one means of this.
4. One goal for bespoke (custom-designed) software financed by public bodies, including software for research and development projects, should be its reusability. Keeping the software free and open-source is one way to achieve reusability. Strategies shall be devised at the outset of such projects for ensuring reuse of the software.
5. Students in Icelandic educational institutions shall be given the opportunity of learning about and using free and open-source software on a par with proprietary software