I'm surprised there's no mention of his first 100 days pledge to "announce our withdrawal from the Trans-Pacific Partnership" - something that the EFF has been lobbying for.
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.
BTC transactions are all public in the blockchain so they're not as anonymous as many think.
But as for preventing your identity from being linked to your BTC wallet? There's probably no way to prevent that if the service provider is under US jurisdiction.
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
That's the big use case right now. A more flexible version of http://www.quickmeme.com - though I'm sure users will come up with other cool uses in the coming months.
I recommend using Panjiva.com to do some diligence on suppliers before committing. You can see who else they're supplying in the US, historical data (ie. are they doing more or less US business?) and even pull credit records and other data.
It's not failsafe but you'll get a much more complete picture of a supplier than with Alibaba.
I don't think you can be a part of too many networks
Sure you can.
The opportunity cost is being part of a network that you get more out of. Or building/maintaining your personal network. Or working on something productive.
https://www.eff.org/issues/tpp