Idk, just wanted to know your opinion, since you referenced it.
Myself, I disagree with both halves. Performativity is harmful, giving words power like that is harmful.
The term is uniquely fitting, as it derives from "master copy" and not the maybe potentially unpleasant analogy that's used with bus clocks. Even trunk would have been better, but nothing conveys the notion of "this branch is what the software is" quite as well.
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
Idk, just wanted to know your opinion, since you referenced it.
Myself, I disagree with both halves. Performativity is harmful, giving words power like that is harmful.
The term is uniquely fitting, as it derives from "master copy" and not the maybe potentially unpleasant analogy that's used with bus clocks. Even
trunk
would have been better, but nothing conveys the notion of "this branch is what the software is" quite as well.We agree to disagree :)
how about the term 'bug' ?
Yeah, it's pretty irresponsible. But how do we rename debug builds, debug asserts, and most importantly, the debugger?
I don't have the final word.
My votes would be
1) testing builds
2) asserts (should be turned on on production as well)
3) .... tracer
teleports behind you
removes all asserts and logging statements at compiletime
Nothing personell, kid
😎