SHARE
TWEET

Don't put BASIC code in your emails

a guest Dec 13th, 2011 17,157 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. From: Ray
  2. To: All
  3. Subject: in late tomorrow
  4.  
  5. All,
  6.  
  7. 10 GOTO Subject
  8. 20 PRINT "I am going to be " + Subject
  9. 30 END
  10.  
  11. Thanks,
  12.  
  13. Ray
  14.  
  15. ==================================================================================
  16.  
  17. From: John
  18.  
  19. Line 20- is never reached, optimized out.
  20.  
  21. Perhaps you mean gosub?
  22.  
  23. ==================================================================================
  24.  
  25. From: Eric
  26.  
  27. I detect an infinite loop:
  28.  
  29. - read the subject
  30. - read "All,"
  31. - read line 10
  32. - goto the subject
  33. - read the subject
  34. - ...
  35.  
  36. and as we all know: recursion is preferable to side-effect based looping.
  37.  
  38. (def read-email [email]
  39.   (read-subject email)
  40.   (read-email email))
  41.  
  42. ==================================================================================
  43.  
  44. From: Ray
  45.  
  46. Re-factored with apologies:
  47.  
  48. 10 Subject == getConfig(Email[Subject])
  49. 20 PRINT "I am going to be " + Subject
  50. 30 IF getConfig(Email[TO]).RespondedToThisEmail
  51. 40     PRINT "You took this way too seriously - now the email will never end"
  52. 50     GOTO 40
  53. 60 ENDIF
  54. 70 END
  55.  
  56. Thanks,
  57.  
  58. Ray
  59.  
  60. ==================================================================================
  61.  
  62. From: Dave
  63.  
  64. Did this message go through an E & A?
  65.  
  66. ==================================================================================
  67.  
  68. From: Eric
  69.  
  70. Why are we writing code without tests?
  71.  
  72. ==================================================================================
  73.  
  74. From: John
  75.  
  76. At least it’s going through PQA.
  77.  
  78. ==================================================================================
  79.  
  80. From: John
  81.  
  82. But will it have two ship its before tomorrow?
  83.  
  84. ==================================================================================
  85.  
  86. From: Ray
  87.  
  88. I am so glad that you all are so interested in my project!  In order to move
  89. forward more efficiently, I have created a wiki page to continue to track the
  90. progress:
  91.  
  92. http://devwiki.../Basic_In_Late_Email
  93.  
  94. Please feel free to add yourself and comments to the page going forward.
  95.  
  96.  
  97. Thanks,
  98.  
  99. Ray
  100.  
  101. ==================================================================================
  102.  
  103. From: Dave
  104.  
  105. It's kind of scary how far outside the process this project has gotten in such a
  106. short time. We really need to reign this in.
  107.  
  108. For example, I'm assigned to setting up an E & A, and I can't help but notice we
  109. have no story cards for this project. We really need to get those cards written
  110. (let's think in MMF's here, gang).
  111.  
  112. Oh, and Jackie, we'll need to get a Kanban board set up ASAP.
  113.  
  114. I think we're all agreed that we'll do a review of what Ray has already done
  115. followed by a retro on Friday.
  116.  
  117. ==================================================================================
  118.  
  119. From: Eric
  120.  
  121. Is this part of an Impact Area? Should we even be doing this without executive
  122. oversight?
  123.  
  124. ==================================================================================
  125.  
  126. From: Davin
  127.  
  128. Good point Eric.
  129.  
  130. This project is of core importance to this company, and we should give weighty
  131. consideration to forming 2 oversight committees and a special impact area for
  132. this. I'm also wondering if we can earmark any of this for an innovation grant
  133. to help offset the cost to us. Marketing needs to weigh in...
  134.  
  135.  
RAW Paste Data
Top