Jargon is unnecessary if the thing being described can be easily and effiiciently described in layman's terms.
Firstly, I can't claim any sort of authority on this unless I explain my credentials. This is usually not something I like doing because it's usually done to show off and that is something I can't stand. Unfortunately, I need to explain WHY I am qualified to make any sort of judgment on this.
I have solid Engineering Honours degree from 20 years ago and I am currently going back over some of my maths hence I am on this site for some info from time to time.
I have over 16 years of commercial engineering experience most of which has been as a Software Designer. My employee/client list has included some of the biggest and most prestigious companies in the world including the world renowned IBM Research Facility in England and Motorola. As well as being involved in Software Design (mostly embedded software) I have had technical authority over other designers in both companies listed above.
I have also ran my own recruitment firm and have interviewed and recruited engineers.
I also spent a few years Freelancing to earn more money.
OK so when it comes to having an opinion on software and IT in particular I believe I am speaking from some professional and commercial experience rather than as a 19 year old "read a book and think I know it all" weekend hobbyist.
Jargon in both fields is sometimes necessary and sometimes it has been introduced deliberately to block others from accessing the knowledge. This is regularly done to:-
1)Boost the image of the person doing it because they look like experts to the untrained eye.
2)Boost their job security by making them look irreplaceable.
Part of what I used to do was identify such people and weed them out. My "kill list" on this is pretty depressingly impressive.
For some proof of this, have a dispassionate look at some of the words and phrases used in IT.
How many of them seem "Sexed up"?
I use the expression "Trekkied up" sometimes to mean the same thing because it amply illustrates the common (but not exclusive) type of person who works in that field.
For final proof, simply find a decent engineer and actually ask him yourself. A decent engineer is a decent engineer and doesn't need jargon to confuse others.
Hope that explains my point.