3 ms·
Systems are too large to understand the consequences of our changes. We should be using as many automated tools for figuring out how to make change as possible.
by moron4hire 9y ago
Systems are too large to understand the consequences of our changes. We should be using as many automated tools for figuring out how to make change as possible. "Reasoning about code" only works for academic scale programming.
- sametmax 9y agoDepends of the system. Google/Dropbox/Instagram/Facebook/Mozilla use cases are not most people use cases. (Plus they do use Python anyway)
- cwyers 9y agoGudio has worked for Google and Dropbox.
- moron4hire 9y agoNo, I'm talking much smaller. Unless all your job is to glue services other people write, the number of things you really need to know to understand a full, non-trivial system are too much for any one person. The only reason any of this works is because we can compartmentalize and choose to ignore whole chunks.