Explore >> Select a destination
|
You are here 
|
jack-vanlightly.com | ||
| | | | |
www.allthingsdistributed.com
|
|
| | | | | Werner Vogels on building scalable and robust distributed systems | |
| | | | |
buttondown.com
|
|
| | | | | Building an intuition for the mathematics behind the "TLA" in "TLA+" | |
| | | | |
www.hillelwayne.com
|
|
| | | | | My job these days is teaching TLA+ and formal methods: specifying designs to find bugs in them. But just knowing the syntax isn't enough to write specs, and it helps to have examples to draw from. I recently read Chris Siebenmann's Even in Go, concurrency is still not easy and thought it would make a good case study for writing a spec. In it, he gives an example of Go code which deadlocks: | |
| | | | |
128bit.io
|
|
| | | One of the things that really gets me excited about my new job is being able to use new technology. Sure, sometimes new technology is risky but I see groups befitting more then failing due to usingnewer technology. As always when talking about new technology, NoSQL seems to come up because there are a good number of people switching parts (or all) of theirapplication to use NoSQL databases to get by limits or to help withscalability issues. | ||
