End-user application

From The Jolly Contrarian
Revision as of 10:24, 17 September 2019 by Amwelladmin (talk | contribs) (Created page with "{{g}}That piece of .php code, that wiki, that excel macro, that SharePoint workflow, that mailmerge — that neat little trick you put together to automate...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The Jolly Contrarian’s Glossary
The snippy guide to financial services lingo.™


Index — Click the ᐅ to expand:

Comments? Questions? Suggestions? Requests? Insults? We’d love to 📧 hear from you.
Sign up for our newsletter.

That piece of .php code, that wiki, that excel macro, that SharePoint workflow, that mailmerge — that neat little trick you put together to automate some tedious routine task and make your own life easier because the combined weight of your employer’s 500m annual IT budget can’t or, more likely, won’t, do it for you. The idea isn’t to make life easier for the meatware after all.

End-user applications threaten the integrity of the firm’s “application estate”, so expect IT to devote a portion of its budget — the portion a kinder organisation might have allocated to giving you those very tools, in fact — to a witchhunt to track you down and terminate you and your stupid EUA, with extreme prejudice.

See also