It's not surprising that banks are interested in blockchain technology, if not necessarily Bitcoin itself.
Patenting technology is very common by these companies and it is almost always a protection measure against them being sued for using it.
Someone living near my parents looks to have uploaded a hundred or so "chemtrail attack" videos. I honestly had no idea that people in the UK were into that sort of thing, but that's the internet I guess.
Having just gone through all of the tutorials and documentation, I can see this type of thing shaking up configuration management in enterprise environments quite significantly. The amount of headaches I have keeping several environments (Dev, Staging, Test, UAT, Pre-Prod, Prod) in sync - across any project I've worked on - would be far better maintained using this kind of container-based management.
Hmm. I must say I'm amazed you could generalise in that fashion - I can't speak for your personal experience, but we certainly don't treat English people as 'the enemy', and to claim that that is a consideration for an English person choosing to work in Scotland is rather laughable.
"Nightwatch got its name from the famous painting The Night Watch by Dutch painter Rembrandt van Rijn. The masterpiece is prominently displayed in the Rijksmuseum, in Amsterdam - The Netherlands".
...which was called such because the painting got dirty and buried under tons of varnish; the actual title is "The Company of captain Frans Banning Cocq and lieutenant Willem van Ruytenburch preparing to march out."
I have endless TextEdit files strewn around my hard disk with very similar contents, I need to hoover them up every now and again. It's really useful to type something out like this, even just to map the problem out in your mind.
I found it useful to start writing an email to some people concerned. I usually start with "it don't work", then because I don't want to look stupid I explain a bit what doesn't work, I feel the need to explain my thought about why do I don't look like unimaginative, and then I write down how I would check if I'm right, because I don't want to look like I'm not scientific, then I just try the test because I'm not supposed to be lazy, and then usually I trash the email because I found the bug.
This is one of the reasons I like to provide detailed commit messages, and encourage my team members to do the same. I treat the commit message like a short email to the team (even if that's only future me) about why and how I made the change. Summarizing the change in writing often uncovers logical flaws or missing edge cases. I've aborted my commit (after copying the notes for reference) more times than I'd like to admit when I've realized that I've not thoroughly tested something or missed updating that admin report that would be affected, etc. The act of 'telling someone' exercises different pathways in the brain and helps you think about the problem differently. As someone already pointed out - it's a flavour of rubber duck programming. It also works really well in a team environment where your CI system emails the whole team the commit notes. You get a low ceremony quick design review. "Did you update the X system/form/report when you changed Y?" replies happen more often than you think, and junior devs can actually learn a lot about an existing system just by seeing the approach used by other team members.
It's also a miniature version of literate programming. You can go through all the commits and get an explanation of how the program evolved -- not just the actual lines changed.
I quite liked the look of EBean, though I haven't really used it much. Even so, it's fairly easy to plug in a JPA manager (in my case, Hibernate) and use the helper classes provided for DB management.
Edit: should add that I'm mainly familiar with the Java play framework aspects, not so much the Scala end.
