Explore >> Select a destination
|
You are here 
|
blog.pragmaticengineer.com | ||
| | | | |
www.industrialempathy.com
|
|
| | | | | One of the key elements of Google's software engineering culture is the use of design docs for defining software designs. These are... | |
| | | | |
maheshba.bitbucket.io
|
|
| | | | | Since moving from academic research to industry in 2017, I've worked on two software projects. Each one started as a small, clean-slate1 skunkworks effort involving 2-3 people and gradually expanded to a large, conventional software engineering effort with dozens of engineers. The first of these (from 2017 to 2021) was Delos at Meta, a Chubby/ZooKeeper/etcd-like control plane storage system. The second was a new Kafka engine (from 2022 to 2024) that can run on any disaggregated storage layer (and powers the Confluent Freight product, where S3 is used as that storage layer). Nearly every system at Meta depends in some way on Delos as of 2025 (e.g., this article describes an example dependency chain); Confluent Freight just became generally available and time will tell if it succeeds commercially, though early results are promising. this prior post might explain why I think clean-slate innovation is critical in systems.? | |
| | | | |
miekd.com
|
|
| | | | | Personal website of Maykel Loomans, a digital product designer from the Netherlands. | |
| | | | |
channellife.com.au
|
|
| | | Etisalat by e& plans to standardise on Red Hat technologies for its network and IT, aiming for greater efficiency and innovation. | ||
