Oh wow, did they maybe search for someone with skills of a "server" and the Indeed algorithm soup got that mixed together with skills in server technologies...?
My local bar is tended by a software engineer. It's only open on Saturday evening cause he does it besides his day job.
But it's great cause he does it for the love of mixing cocktails, and introducing people to great drinks from all around the world.
And he obviously doesn't really need the money, cause when you show an interest, most drinks are on the house.
He uses a pencil, paper and a mechanical calculator to tally up the bill, which I absolutely understand when your career is in IT.
He uses a pencil, paper and a mechanical calculator to tally up the bill, which I absolutely understand when your career is in IT.
When the alternative is either having to search, evaluate, compare, select and configure an application for that purpose that you're never quite happy with, or to scope, design, develop, test, deploy, maintain, eternally find things you wish you'd done better, refactor, realise you're spending your free time on doing more of your job, regret your life choices, resolve to only make this last improvement and then call it good enough, renege on that promise to yourself a week later, burn out, curse that damn app for ruining your hobby...
...yeah, using the most trivial low-tech solution possible does look rather sensible.
At my first and only job involving SQL, the dev database was also the (only) backup.
The company was so cheap, only 2 people could log onto the server at a time, yet there were 5 admins that needed access.
(so they saved a few thousand on licenses, at the expense of half the employees sitting idle at any time, and getting frustrated.
This is fully better than "go be a farmer", at least. Not because nobody wants to be a farmer, but because software developers actually grasp what's involved in bartending, and not just a fictional themepark version.