Yep. Jira isn't an antipattern; inverting the first value of the agile manifesto is an antipattern, whether you do it for Jira or any other tool (or process).
1. Don't (unless there's an extremely good reason to do so). Ask yourself: is there a net benefit gained by forcing a developer to learn and use your DSL, ignoring their likely familiarity with general purpose languages that could solve the same problem? For starters, any application where humans won't be reading/writing a large amount of the DSL is probably out.
2. Avoid anything that resembles natural language. If you're writing a true natural-language interpreter, you're not writing a DSL. If you're writing a DSL that looks like natural language, people will be tempted to apply the grammar rules they already know from that language, rather than the strict grammar of your DSL, resulting in frustrating errors. It's a whole lot easier to memorise the rules in a language of keywords and symbols, because you don't have to first banish your existing knowledge of natural language.
3. Don't try to accomodate "non-technical" users performing intrinsically technical tasks. There's no point creating a "friendly" DSL over HTML and CSS if the people authoring in the DSL still require an in-depth knowledge of the box model, responsive web design etc. All you've done is kicked the can down the road and created a false sense of capability.
I used udev to run the script as soon as the drive is mounted. The tricky part was ensuring the drive would mount automatically when inserted, even if I wasn't logged in. I tried a range of different tools, and eventually settled on autofs.
The first is that I consider what I'm doing to be a hobby, and therefore tax-exempt. The point was more about the challenge of writing the bot than seriously imagining that my trivial algorithm could make money. Because it's currency trading, I expect the Australian Tax Office would disagree with my definition, but there is one thing in my favour -
The second reason is that, despite hitting almost A$2000 profit around January, as we head into tax time it's sitting at less than $500. Also, I've never realised any of these profits - I withdrew the original A$500 investment, but everything else just keeps getting reinvested. I don't think the ATO is going to be too troubled that I've got a little under A$500 worth of pretend-money floating around in the aether somewhere.
Bottom line, I'm not going to worry about tax until there's enough profit that I can pay an accountant to worry about it for me, and possibly pay some backdated taxes. The up-side to automated trading, even for small-time personal investors, is that the ATO regards it as "carrying on a business of share trading" rather than investing as an individual, and their rules appear to be a bit simpler in that situation.
I only use one SD card and one camera, so I just store the name of the last file copied (e.g. DSC02745.ARW) and the next time the card is inserted I only copy files that come after that one when sorted by name. It would be pretty easy to extend to multiple cards and/or cameras, but I've never had the need.
1. When I plug my camera's SD card into the front of my Linux server it automatically copies off any new photos and sorts them into a YYYY/DD/MM folder structure.
2. I wrote a cryptocurrency trading bot because I'm too lazy/uninterested to actually learn anything about the market. It seemed to do pretty well when the market was flat or going up. Hard to tell if it's doing badly now or if it's just reflecting the state of the market. I almost forgot to include it in this list because it's so thoroughly automated that I rarely bother to check it.
3. I assisted the owner of pvoutput.org with adding support for the automated data upload format from my PV inverter. Then I wrote a script that automatically polls my electricity meter using a RAVEn USB device to upload the net import/export of power.
4. Maybe other things that I've forgotten about because they're automated...