I agree that this language can be useful in a specific domain, but you should not underestimate the barriers this creates to actual communication, confusion because you think it means one thing and your colleague thinks it means another, and/or alienating those outside the team that uses it and understands it. This goes for any language, business or otherwise.
This is a real problem, especially for customer facing teams that continue to speak their own language instead of the client's language, and it will destroy your relationships if you do it wrong.
The article is about this language being used to convey expertise when it does not exist (understanding of the language does not imply understanding of the subject you're supposed to know, but may make you sound smart in a meeting).
Obviously feel free to keep using the terms if they work for you, but do so while also knowing the impact of the words.
TL;DR: Words matter, sounds like you are of the same opinion :) As long as we use them purposefully and understand the trade-offs, all good.
This is a real problem, especially for customer facing teams that continue to speak their own language instead of the client's language, and it will destroy your relationships if you do it wrong.
The article is about this language being used to convey expertise when it does not exist (understanding of the language does not imply understanding of the subject you're supposed to know, but may make you sound smart in a meeting).
Obviously feel free to keep using the terms if they work for you, but do so while also knowing the impact of the words.
TL;DR: Words matter, sounds like you are of the same opinion :) As long as we use them purposefully and understand the trade-offs, all good.