nullxone

7 ms·

31.
by nullxone 10y ago
I concede your point. I suppose the nice thing here is that we both now have two ways of doing the same thing. I've explained why I prefer running the underlying tooling; hopefully it will be useful as one of those snippets of internet
32.
by nullxone 10y ago
I used that for a while, and it worked for me too, but found that it took a long while to reload the app, and also some time for node-inspector to bring up all the files. There's babel-watch ( https://github.com/kmagiera
33.
by nullxone 10y ago
In some respects yes. In my mind the debugger is a last resort tool, when other feedback loops don't provide enough information. Where it really shines though, is when debugging rather terrible spaghetti like code, where a debugger rea
34.
Show HN: Debugging Babel and Node done right
22 points by nullxone 10y ago|10 comments
35.
by nullxone 11y ago
Well written accounts of what went wrong, always accompanied by remediation measures for the future. Some insight into systems at Google scale, and the fact that in the end it's people running the show :) Examples: https://s
36.
Google Cloud Status – Summary, Description, Root Cause, Prevention(status.cloud.google.com)
2 points by nullxone 11y ago|1 comments
37.
by nullxone 11y ago
Hi, author here. Goals here are: - To treat a Kubernetes cluster and Kubernetes nodes as the fundamental units of infrastructure, abstracting out the underlying provider. - Excellent developer workflow: https://github.com/ha
38.
Pangaea: Point and Shoot Kubernetes with Exactly One Command(hasura.io)
10 points by nullxone 11y ago|1 comments
39.
Frontiers of App Development: A Story of Containers and Kubernetes(hasura.io)
11 points by nullxone 11y ago|0 comments