Ask HN: Does anything beat the uptime of emails and Excel?
On a related note, my partner has managed (as the customer) migrating an examination platform recently, to a "more secure" one with lots of yummy microservices. Or was - the contract has now been cancelled and she's looking for a new job, and possibly therapy, after a torrent of personal abuse caused by bugs she simply cannot fix.
What's sad is that I wish I could say this was unusual. But it's anywhere and everywhere I've worked.
Quite seriously, what are we doing? Why do other apps exist when I will, every single time, be justified in replicating the entire workflow in emails + Excel? I'm at least partially supposed to advise on security, and the only people who won't recite this very rant at me as a reason to ignore all security advice, are the people who can't be bothered to.
The one ray of light is that at least it's easy enough to attach links to access-controlled spreadsheets now, rather the spreadsheets themselves, possibly protected with a password (usually, in that same email).
I thank you for listening to this /rant.
12 comments
[ 0.22 ms ] story [ 40.6 ms ] threadThe solution: build or befriend a relational database developer that will create a bespoke solution of your dreams. The more difficult part is getting c-level buy in and wading through whatever crap middle management believes to be the flavor of the month.
Most of the time, I see _more_ issues when teams over rely on Excel files. Data inconsistencies abound, audit trails are nearly impossible, and security access is difficult to manage. The end goal for most processes is to limit the amount of human touch-points... not increase it.
A - A pretty numerical mindset. Sit in front of their computers all day. Know their processes inside-out.
B - Perhaps not formally trained, but working with data, Bloomberg extracts, a self-taught sense in normalising data.
C - If there's an Excel function that saves time, they know it. This also leads to trader-as-a-developer with personal VBA scripts as that's good enough and there's an IDE in Excel that doesn't need layers of approval to use (which is obviously a disaster) - this also means thinking "If I can do this in Excel in a day, why does it need a development team of 5 to do in a month?"
D - Fast turn-around. That means keeping on top of messages, dates, calendar. And a sense of prioritising this without needing a system to do it. And messages pumped through mail, phone, BBM, conversations all tied together.
E - Don't want to be Nick Leeson and have a grudging acceptance that compliance and audit is a thing.
F - Except when they don't.
Contrast that to typical clerical roles where these things are somewhat 'slower paced' and doing things with Excel/following-up emails becomes a disaster - not in all cases, but in many.
All BAs I know in banking/finance are exceptional communicators that get through points A-F above.