29 ms·
I work at a non-IT place & am seeing these types of low/no code automation attempts first hand. It's equal parts inspiring and terrifying to see. Inspiring bec
by Havoc 7y ago
I work at a non-IT place & am seeing these types of low/no code automation attempts first hand. It's equal parts inspiring and terrifying to see.
Inspiring because they are actually getting stuff done.
Terrifying because they lack all the basic caution programmers learn over time. (Don't test in prod etc)
Nor are the safety rails programmers assume are there necessarily in place in non-IT shops. e.g. Roll back mistake with version control
Interesting times ahead
- shaftway 7y agoI've seen this, and it's horrific. It was 2008, and I worked for a large investment bank (think in the Goldman Sachs echelon). I was on a transition team moving risk analysis for $1bn in synthetic CDO assets from Excel spreadsheets to a formal system. There was zero documentation. Formulas were not internally consistent. Their version of version control was saving a new copy of the spreadsheet every day. Their version of day-to-day analysis was copying tabs with a specific naming scheme so that the macros would pick up yesterday's data properly. Have you ever seen a spreadsheet generate XML? Shell out to a command line program? Import the XML that command line program generated? Generate a CSV file? And then FTP that CSV file to a central reporting system? I have, and it haunts me to this day.
- Havoc 7y agohaha yes exactly that. Finance crowd with VBA macros can be daunting once they've built an edifice that is as unstable as it is mission critical. Noobs armed with RPA point & shoot cannons isn't far behind. Only a matter of time before that ends in a self-inflicted data leak.