A long time ago I coded up a feature for SocialCoder which converts a link - any link - to a short URL. I use it all the time for sharing links to volunteer profiles and to volunteer opportunity listings.
A new opportunity listing is posted by a charity.
I review and publish it, tweet about it, then click a button to send the charity an emailed notification of next steps.
Could it be a mail provider problem? Unlikely.
Maybe a bug, an infinite loop or recursion in my code? More likely.
I changed the notification email address so that it would only spam me, and not the charity.
But now that it was just me being spammed, and not the charity rep, I was able to calm down enough to see what had happened.
You could say it was a learning moment. So what did I learn?
Don't use HTTP GET when a POST is more appropriate. If the request parameters were in the body of the request, and not in the URL, the link would have been fine to share.
The feature that sends email should not have been available to anonymous users.
In coding terms, the controller action was missing an [Authorize] attribute. yeah ...oops.
Although the consequences of this mistake were relatively minor, affecting only me and the charity rep's Inbox, I still needed to calm down before I could see the problem clearly enough to effectively trouble-shoot. Maybe I'm drinking too much coffee. Maybe.
Being able to code a fix, run unit tests, and deploy that fix, all within within minutes is such a valuable thing.
Thank you to the @Azure team who made this so easy.
More from Tech
Machine translation can be a wonderful translation tool, but its uses are widely misunderstood.
Let's talk about Google Translate, its current state in the professional translation industry, and why robots are terrible at interpreting culture and context.
Straight to the point: machine translation (MT) is an incredibly helpful tool for translation! But just like any tool, there are specific times and places for it.
You wouldn't use a jackhammer to nail a painting to the wall.
Two factors are at play when determining how useful MT is: language pair and context.
Certain language pairs are better suited for MT. Typically, the more similar the grammar structure, the better the MT will be. Think Spanish <> Portuguese vs. Spanish <> Japanese.
No two MT engines are the same, though! Check out how human professionals ranked their choice of MT engine in a Phrase survey:
https://t.co/yiVPmHnjKv
When it comes to context, the first thing to look at is the type of text you want to translate. Typically, the more technical and straightforward the text, the better a machine will be at working on it.
Let's talk about Google Translate, its current state in the professional translation industry, and why robots are terrible at interpreting culture and context.
Straight to the point: machine translation (MT) is an incredibly helpful tool for translation! But just like any tool, there are specific times and places for it.
You wouldn't use a jackhammer to nail a painting to the wall.
Two factors are at play when determining how useful MT is: language pair and context.
Certain language pairs are better suited for MT. Typically, the more similar the grammar structure, the better the MT will be. Think Spanish <> Portuguese vs. Spanish <> Japanese.
No two MT engines are the same, though! Check out how human professionals ranked their choice of MT engine in a Phrase survey:
https://t.co/yiVPmHnjKv
When it comes to context, the first thing to look at is the type of text you want to translate. Typically, the more technical and straightforward the text, the better a machine will be at working on it.
