4 ms·
In my experience, it's not techies that talk gobbledegook, it's that those signing off IT work don't want to hear about problems ("this will take years to imple
by zwischenzug 13y ago
In my experience, it's not techies that talk gobbledegook, it's that those signing off IT work don't want to hear about problems ("this will take years to implement"), so it's those who pull the wool over their eyes that get to talk to them.
I've seen a FTSE-100 company destroyed because of adherence to buzzwords and industry standards (nothing inherently wrong with that) without - crucially - any attention to the details of applications to their business. Which is what this Dennis did.
- sebcat 13y agoI've seen entire codebases riddled with method names that could've been taken straight from the latest sales pitch made up by Marketing. I think it depends on what kinda company you are. The more "sales-driven" (for lack of a better wording) your company is, the more likely you are to end up with words like "human assisted training" to describe a non-AI related configuration process. I would say techies also get caught up in this behavior sometimes.
- hkmurakami 13y agoWe had to change the names of our API function calls when marketing updated our product name :(
- Sandman 13y agoWhich means you used a bad naming convention. I hope you updated them to something that is descriptive enough and yet won't need to be changed next time marketing decides to change the product name.
- walid 13y agoWell I have to say that some command/API names on unixes for example are horrible. What's up with killing processes. Can't we just say terminate. Since software is mostly developed by a geeky bunch we sometimes forget that we are actually making something to be presented in an appealing manner to a buyer/licenser.