anchor.diff:  something negotiated in the contract underlying this particular calculation. In other words, even though it 
   represented (across the full range of clients for this tool) a multi-million dollar disadvantage, we were 
   still supposed to directly do it wrong.
  +TL:DR it's not just your professor, sometimes it's your job to do it specifically wrong
   
  -
  -TL:DR it's not just your professor, sometimes it's your job to do it specifically wrong
  -____
  +[small]#- By a former Bank Employee, https://www.reddit.com/user/ituralde_[ituralde_]#
positive.code: # Specs vs Common Sense
  
  So I was browsing through http://reddit.com[reddit] and came across this picture: 
  
  image::http://i.imgur.com/KtKNmXG.png[AssholeTeacher,640,400,role="center"]
  [small]#source: https://www.reddit.com/r/pics/comments/3pmyh3/teachers_logic_in_grading_math/[reddit]#
  
negative.code: will pay a visit to the school and hopefully this teacher stops killing kid's motivation to learn 
  and specially learn math.
  
  For a *final statement* I will leave here another comment from the thread that really rounds things up 
  with this topic by explaining a real life example of how common sense might not make your life easier 
  all the time:
  
  [source]
  Hey, former dev at a bank here.
  Being "better" isn't strictly right. This isn't just your professor being an asshole, I was on an actual 
  project that had pretty much this exact same problem.
  Project involved effectively automating some collateral value calculations. We were given a spreadsheet 
  with some sample values and were given the maths and were told to match output. We didn't bother to check 
  that the formatting rules truncated at certain point (at the millions). We get into UAT and the business 
  