37 ms·
>> shell scripting instead of programming. I was at a discovery conference (lawyers) listening to a vendor pitching the cost of writing some ediscovery syntax
by sandworm101 10y ago
>> shell scripting instead of programming.
I was at a discovery conference (lawyers) listening to a vendor pitching the cost of writing some ediscovery syntax to delve through a 50gb database of emails. While he was talking I performed a grep search on my ubuntu netbook, with the database on an encrypted thumbdrive. In a matter of minutes I convinced the client that he didn't need coders to do much of anything, that an idiot lawyer with a laptop could do it from his hotel room that night (which I then did). The vendor left the room very angry with me.
The downside was that rather than the 100k I saved the client, all I could ethically charge was my rate for 6hours of overtime.
- flukus 10y agoI 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.)
- edoceo 10y agoSo for a lawyer on overtime that's still more than a coder makes for 6h work.
- sandworm101 10y agoNot really. Bringing in an outsider takes time and money. You cannot just grab some kid off the street. You have to go with a vetted pro, someone who can be trusted to handle the material. He or she must be briefed about the task and then be supervised. The result is a report and presentation that me and the other lawyers have to read and attend. It takes weeks. I, already on the inside and not needing any briefing or supervision, got it done overnight.