2 ms·
I always love these stories. I'm pretty sure half of the over engineered apps where I'm working could be replaced by a handful of shell scripts. One particular
by flukus 10y ago
I always love these stories. I'm pretty sure half of the over engineered apps where I'm working could be replaced by a handful of shell scripts. One particular one recently had us adding a whole lot of tables to the database with the accompanying sql and code so we could monitor performance in real time. The information could have easily been generated from our log files with a sed script or a flex program.
- sandworm101 10y ago(without breaking at-client priviledge) The full task wasn't exactly simple. It started with a failing part in a product. The issue was when exactly the manufacturer should have been aware of the issue. All we had was a database of emails to and from local reps, who as it turns out had been fixing the problem for a long time by telling customers to disable certain features. This fix caused other damage. From the email pile I created a graph showing when customers emails started to mention problems, when the first reps started telling them of the fix, and when those reps started talking to each other about this fix. My client-manufacturer then had an idea of when his organization should have gotten the message and put a stop to things. This then informed the negotiations. So it was cross-referencing a list of vendor emails addresses, customer email addresses, some keywords, and putting it into a timeline. Bash bash bash, a solid night's work but nothing needing actual code. Had this gone to trial we would have had the ediscovery vendor come in and do a full and proper report. It didn't, and both sides looked took my report as useful enough to come to an agreement. (I gave them my bash scripts and they verified my conclusions themselves.)