stackzero

8 ms·

61.
by stackzero 8y ago
> In my opinion everyone company likes to only benefit from experiences earned elsewhere but never like to provide folks a place to earn the same in their company ^ this, can't agree enough.
62.
Ask HN: Rust knowledge sharing, patterns, idioms, etc.
4 points by stackzero 8y ago|0 comments
63.
Ask HN: Is “public key” a misnomer?
1 points by stackzero 8y ago|1 comments
64.
by stackzero 8y ago
There are certainly many moving parts- but there's nothing quite like running kubectl create -f <somefile> and sitting back to watch your entire application stack spin up
65.
by stackzero 8y ago
The canonical example of serverless is for handling web requests i.e. 1 function per HTTP route. Database will still need to be on a static server. Managing user login / state etc. will be cumbersome across multiple different functions
66.
by stackzero 8y ago
It can be abit of a pain if you're not using linux OS as the server. Setting up secure image registries or registries in general is also tricky. It can be tricky learning how to debug dockerised applications because of the extra layer
67.
by stackzero 8y ago
Click bait of a title... I think the more important thing this article is trying to say is: use a good heuristic to solve your problem, if it can't do so then ML may be something to look into.
68.
Ask HN: Software engineer in the interim
2 points by stackzero 8y ago|0 comments
69.
by stackzero 9y ago
Firefox: Octotree Chrome: Momentum
70.
by stackzero 9y ago
Distributed systems and their architecture - Samza, Kafka and interesing approach to data modelling - Terraform spin up Kubernetes clusters with a few MAC addresses - Raft
71.
Paging in production?
1 points by stackzero 9y ago|2 comments