binocarlos

It feels like this question wants to be saying "what price did you buy bitcoin"? :-)

Plus the fact that Vitalik seems genuinely interested in the development of the underlying technology and isn't too fussed about making more money than he already has. An example of this is offering to fund Ethereum infrastructure projects from his own pocket because he was seeing what was happening with ICO money: https://www.ethnews.com/vitalik-buterin-responds-to-raiden-i...

gotty is such a useful tool - especially with interactive mode turned on and you can ssh from the browser

100% this - I've spent many years feeling like I'm one abstraction away from having a killer library that would get me the initial crud based app done in a single line of code...

I've never actually managed it - the edge cases mean I end up chasing my tail around instead of "just coding the app".

Now I use small libraries for individual parts (like menus and forms) but even then 50% of the app becomes special edge case forms anyway. Accepting that the job is to just implement the spec and not invent a rube goldberg machine is an important lesson to absorb.

If this is a joke then it belongs on Reddit /r/jokes - if it's not a joke it belongs on /r/LateStageCapitalism

This seems to be a popular answer - i.e. go is the web framework.

I read a comment only yesterday: "I don't know any half decent Ethereum developers who are not currently millionaires". I felt poor and excluded.

Then I remembered how it felt in 2000 where all you needed was a website for pet food and folks would throw money at you.

The morning paper by Adrian Colyer: https://blog.acolyer.org/

define poorly maintained - do you mean "not pushing half finished code often"?

There are times writing a bash script it feels like "omg - a programming language would be much easier for this task"...

So I write a tiny program in the lang of my choice and invoke it from that place in the bash script.

The balance between the two tools is great - your advice is spot on for me.

Thats a fantastic tool - there is scope for running it for queries on CI. A bit like a code coverage tool but for db query performance.

so perhaps Ethereum miners will sell their graphics cards and buy disks?

depends if you are using a static site builder or not - for example hugo will easily automatically create RSS of your content with very little config.

I've been using kube-lego (https://github.com/jetstack/kube-lego) to automate certs for Kubernetes ingress for the past 9 months. It is a joy to just add a domain to a manifest, kubectl apply and then hit a browser with a certificate working. Thank you LetsEncrypt for making the Internet more secure.

I remember writing documentation for a Perl system in 2001 - it was using MySQL MyISAM tables and the main developer had a few hundred thousand lines of Perl that acted as the same kind of client attempt at transactions. It was a mess and huge amounts of money were spent on trying to get the thing to work. A few months later InnoDB came along and made it apparent that trying to write transaction logic in the client was a very bad idea, which seems to be the point of this article.

An example (from a case I was involved as a witness in only last week). A jury must be 100% confident that the evidence presented confirms their beliefs. The judge will say "do not decide based on if you believe it happened but instead on the evidence presented". There a world where the jury can believe it happened (and deliberate for 4.5 hours) but still come out with not guilty because the physical evidence is not there. In historical sexual abuse cases (of which this was one) - the CPS (Criminal Prosecution Service here in the UK) will not take on the case if they did not think there was a good chance of winning and yet the only real evidence here was witness testimony and no forensics. It didn't matter that the jury obviously believed it happened - they did their job and realised that was only an opinion and not backed by evidence.

No idea what instruction set the Apple device uses but Google just announced alpha access to their Tensorflow Processing Unit: https://cloud.google.com/tpu/ on Google cloud

I agree I made it complicated - I mean he is very nice and very clever

Adrian Colyer has the highest ratio of being genuinely lovely to being smart of anyone I've met

Good question - I had probably hit enter for `gail.com` having typed it out at one point - then muscle memory of typing `gmai` + enter -> google suggest = 'gail.com'

haha amazing - the 'm' key on my keyboard broke a few months ago - I'm fairly sure I account for at least 2% of the hits that month!

I have to say I humbly agree with this advice - the NoFile.io name got me clicking (the most difficult hurdle) - then when stuff started to animate I thought 'oh' and closed the window. Perhaps this is small minded of me :-)

There are a number of projects and storage solutions that you can use depending on what is important. Using persistent volumes and external storage like EBS is one way. Using distributed file-systems with local or network attached storage like Portworx or Ceph is another. I’m not sure using NFS for the post in this example demonstrates what you would be doing in the real world however.

Yes stateful sets became beta in k8s 1.5 - it's very much a win to run your test suite against a recent (within seconds) production database container that was spun up by CI. Yes you can do this with VMs but that would take 30 seconds :-)

A docker graph-driver that deals with layers as first class citizens - what a great idea! Hopefully this will make my docker builds quicker :-)

This quote from the Readme stands out:

> The LCFS filesystem operates directly on top of block devices, as opposed to over two filesystems that are then merged.

A serverless framework using k8s to hide the servers make a lot of sense

This is an excellent article which really highlights the underlying trade-offs when you choose node for your service (i/o bound work vs cpu).

Unless you know for sure what limits you will hit - it makes sense to iterate quickly and find out. Then, if the service is actually hitting limits (and probably not the ones you thought) - re-write it in a multi-threaded concurrent language like go, elixr etc - or a language designed to solve the actual problems the service is hitting (which might be disk i/o or other infrastructure level things not language choice)

sagas are a steep learning curve and absolutely knowing what a generator function is essential before opening the docs. They are a very productive tool and worth the time imho.

They allow your redux containers to concentrate on selecting state and triggering actions and the async stuff stays out of the way in 'workers'.

Defo worth a look if your redux project has more than a few pages.

I think this is a smart move by Docker. The experience of docker-compose for local development is sublime. The option to deploy that local stack to any number of schedulers but with the same core container runtime feels like the right kind of prod-dev parity. Choice being the main point I'm making.

You tell a story very well :-)