mlafeldt

6 ms·

1.
Open sourcing Listkeeper: Looking back at my suspended Twitter app(artofserverless.com)
1 points by mlafeldt 3y ago|0 comments
2.
This is the Way(thisistheway.us)
4 points by mlafeldt 6y ago|0 comments
3.
Freelancer by Choice(sharpend.io)
2 points by mlafeldt 7y ago|0 comments
4.
The Limitations of Chaos Engineering(medium.com)
1 points by mlafeldt 9y ago|0 comments
5.
Antifragility 101(medium.com)
1 points by mlafeldt 9y ago|0 comments
6.
Getting Things Right With Checklists(medium.com)
2 points by mlafeldt 9y ago|0 comments
7.
by mlafeldt 9y ago
Good question. It is true that Google's Disaster Recovery Testing events are also about breaking things on purpose as a means of preparation. However, those events are typically large-scale, company-wide drills targeting not only criti
8.
by mlafeldt 9y ago
I agree with Arcsech in that Chaos Engineering is most useful in the context of distributed systems. However, this doesn't mean that you can't learn something new from experimenting in, say, a local VM. As a matter of fact, Netfli
9.
Every Day We Must Sweep(medium.com)
1 points by mlafeldt 9y ago|0 comments
10.
The Burden of Running Systems(medium.com)
1 points by mlafeldt 10y ago|0 comments
11.
by mlafeldt 10y ago
Yes, we have. See https://medium.com/production-ready/chaos-monkey-for-fun-and... As for chaos being a hard sell: https://medium.com/production-ready/chaos-engineering-a-shif...
12.
The Power of Less Code(medium.com)
3 points by mlafeldt 10y ago|0 comments
13.
Chaos Engineering 101(medium.com)
2 points by mlafeldt 11y ago|0 comments
14.
The obvious, the easy, and the possible(mlafeldt.github.io)
1 points by mlafeldt 11y ago|0 comments
15.
Teaching Go Programs to Love JSON and YAML(mlafeldt.github.io)
1 points by mlafeldt 11y ago|0 comments
16.
If it hurts, do it more often(mlafeldt.github.io)
1 points by mlafeldt 11y ago|0 comments
17.
Getting started with the Mesosphere DCOS(mlafeldt.github.io)
3 points by mlafeldt 11y ago|0 comments
18.
From zero to staging and back(mlafeldt.github.io)
1 points by mlafeldt 11y ago|0 comments
19.
My writing workflow(mlafeldt.github.io)
2 points by mlafeldt 11y ago|0 comments
20.
Bring your tools with you(mlafeldt.github.io)
10 points by mlafeldt 11y ago|0 comments
21.
Video game hacking(mlafeldt.github.io)
2 points by mlafeldt 11y ago|1 comments
22.
by mlafeldt 11y ago
I recently wrote a blog post on my favorite podcasts: http://mlafeldt.github.io/blog/podcasts-2015-edition/ Here is the list: * Beats, Rye & Types ( http://beatsryetypes.com/ ) -- An entertainin
23.
Writing goals(mlafeldt.github.io)
1 points by mlafeldt 11y ago|0 comments
24.
How to get rid of waste(mlafeldt.github.io)
1 points by mlafeldt 11y ago|0 comments
25.
Being obsessed with tools(mlafeldt.github.io)
2 points by mlafeldt 12y ago|0 comments
26.
Useful writing apps for OS X(mlafeldt.github.io)
2 points by mlafeldt 12y ago|0 comments
27.
by mlafeldt 12y ago
It is true that the only way to get better at writing is to sit down and write. I write at least 250 words each day no matter what. I recently published a blog post on that habit, which you might find helpful as well: http://mlaf
28.
by mlafeldt 12y ago
Hey, I'm the one who developed the cookbook. The openssl_x509 resource looks interesting. I'm going to take a look at it. Thanks for the link! The bash resource works because it uses the system path by default. We actually no long
29.
by mlafeldt 12y ago
I'm the one who co-authored that article with Gregory Brown (@sandal) and wrote the Chef cookbook. Since the project was great in so many ways, I also shared some additional content on my personal blog today: http://mlafeldt
30.
Infrastructure automation by example(practicingruby.com)
1 points by mlafeldt 13y ago|0 comments

More ›