so there should probably be some sort of jargon-user probability setting that would be evaluated by your phrase usage. first off there must be some phrases tha

so there should probably be some sort of jargon-user probability setting that would be evaluated by your phrase usage. first off there must be some phrases that are more commonly used in development than otherwise that it gets correct, a large number of those indicates high chance of being software jargon user. Furthermore all these other phrases are not in themselves common non-software usage, thus if you are using a lot of phrases that might be, with lower probability but still relatively high probability, software jargon this could be set. Now we also get to personal behavior tracking, you are on dev sites a lot chance of using software jargon instead of non-software jargon goes up. Do you use computer for development, chances go up. Of course lots of reasons why they would not track this to keep people from being pissed but still, possible way to improve from tracking. finally allowing people to create profile - which I don't know if they do because I don't use. Of course this kind of software dev jargon workflow would also help other identifiable subgroups with specific jargon sets, like lawyers, or accountants, etc. etc. All these things of o