2 ms·

That is not what I meant by a Merge Queue, this is: https://news.ycombinator.com/item?id=21584144 https://news.ycombinator.com/item?id=21584144. > The thing wi

That is not what I meant by a Merge Queue, this is: https://news.ycombinator.com/item?id=21584144 https://news.ycombinator.com/item?id=21584144. > The thing with engineering is you try to optimize your choice using math and science as much as possible. In software no such optimization procedure exists. It's comparatively easy to optimize something with an absolute answer. Ex: will this building fall down with x design? It's practically impossible to optimize something like: will our software development process allow us to deliver new functionality faster and win market share? There is far more ambiguity in software development than in other fields. https://en.wikipedia.org/wiki/Software_engineering#Definitions_and_terminology_controversies https://en.wikipedia.org/wiki/Software_engineering#Definitio... https://en.wikipedia.org/wiki/Software_engineering#Criticism https://en.wikipedia.org/wiki/Software_engineering#Criticism

deltaonefour 5y ago
>That is not what I meant by a Merge Queue, I meant exactly what you're referring to. Source code isn't the only thing that can go under source control. As long as the file isn't fully binary and is in a somewhat readable human format it can be subject to version control and therefore a Merge Queue. >It's practically impossible to optimize something like: will our software development process allow us to deliver new functionality faster and win market share? This is my point. It's impossible in the same way optimizing a painting of still life is impossible. Therefore it's not really engineering. >There is far more ambiguity in software development than in other fields. Edsger Dijkstra, had it right.