Lifelists/Software Developer: List

Response Options:

Something came to mind

• Yes. Use Mega (Expert User only): 1 | 2 | 3 | 4 | 5

No individual list question links

• 1. Coded when very tired? 2. Coded when you couldn't think straight? 3. Disagreements over requirements? 4. Disagreements over design? 5. Pressure to meet a deadline? 6. Can't get it right? 7. Don't understand what the code is doing? 8. Can't find the bug? 9. Didn't test? 10. Test in production?

• 11. Missed a deadline? 12. Bad requirements? 13. No requirements? 14. Coded when too hungry? 15. Coded when sick? 16. Work long hours without pay to make it happen? 17. Spagetthi code? 18. Inherited code? 19. Legacy code? 20. Misunderstood or unknown concepts, tools, or functionality in an SDK or IDE?

• 21. Only know enough to get the job done? 22. Pretended competence beyond your true level of competence? 23. Unrealistic estimate? 24. Changing requirements? 25. Have to learn a language on the job? 26. Keep making the same mistakes? 27. Customer keeps changing their mind? 28. Project yanked from you? 29. Unknowns? 30. Have to guess?

• 31. Pretended you weren't a developer? 32. Made excuses for not delivering? 33. Glossed over details? 34. Customer or co-worker doesn't get it? 35. Underpaid? 36. Contract ended for unknown reasons? 37. Trouble working with someone? 38. Not socializing? 39. Hiding? 40. Hiding something?

• 41. Too many bugs? 42. Called a bug a feature? 43. Disorganized? 44. Trouble with eyesight? 45. Confusing or conflicting directions? 46. No examples? 47. No story board? 48. Pretending you know better than the customer? 49. Non-technical person told you how to code? 50. Don't want to communicate?

• 51. Company not embracing best practices? 52. Burnt out from coding? 53. Project scrapped? 54. Ruthless peer review? 55. Coded something the customers don't like? 56. Assumptions? 57. Bad assumptions? 58. Forcing it to seem right, or look right, instead of getting it solidly right to begin with? 59. Rush, rush, rush? 60. Inefficiency?

• 61. Fire drills? 62. Procrastinating tackling an assignment? 63. Not sure how to do it? 64. Overwhelmed? 65. Miscommunications? 66. No communications? 67. Too much communication and not enough working time? 68. Have to do Help Desk or support work rather than code? 69. Data sources not ready? 70. Lost work?

• 71. Unsaved work? 72. Have to do it over? 73. Can't quite get it? 74. Licensing issues? 75. Hardware issues? 76. Issues with coworkers or bosses? 77. Have to do things unrelated to job? 78. People don't care what you do? 79. Lack of respect? 80. People think you are a geek or nerd?

• 81. Ashamed of being smart? 82. Don't get out enough? 83. Technology invalidated? 84. Others think you can do it faster than is reasonable? 85. Enforced bad design? 86. Lack of planning? 87. Not motivated? 88. Bitter about something? 89. Loud work place? 90. Dissatisfied customer?

• 91. Difficult customer? 92. Overly complex? 93. Over-engineering? 94. Project manager or boss doesn't get it? 95. Project manager promising too much? 96. Have to fix someone else's code? 97. No documentation? 98. Hard drive failure? 99. Contention? 100. Blamed for a project failure?

• 101. Making excuses? 102. Pretending? 103. Aggressive timelines? 104. Out of date technology? 105. Surfing the internet for fun when working? 106. Working on non-work project at work? 107. Showing off technical knowledge? 108. Using technical jargon to create a smoke screen? 109. Not trusting your intuition? 110. Doing it another's way?

• 111. Pair programming? 112. Refactoring? 113. Agile? 114. Stand-up meetings? 115. Hoping it will work? 116. Hardware limitations? 117. Co-worker who is incompetent? 118. Have to train others instead of code? 119. Have to write documents instead of code? 120. Difficulty keeping up with new technology?

• 121. Hacking? 122. Security? 123. Too much process? 124. CMM level? 125. Silly solutions? 126. Performance nightmares? 127. Something stupid? 128. Others making problems? 129. You caused a bug? 130. Didn't think it through?

• 131. Versioning issues? 132. Something wrong with the code? 133. Someone took credit for something you did? 134. You borrowed someone's code? 135. Underpaid? 136. Highly-paid consultants not that good? 137. Peers making substantially more than you are? 138. Terms or concepts you don't understand? 139. Architecture issues? 140. Some other issue?

• 141. Too simple? 142. Not acknowledged for long hours worked? 143. Unacknowledged excellence? 144. Something else wrong?

Main list page

Other

Write on Report:

10:43 am
_____ list
Q3. Bgh wjshy nmpoll kji hjgey ghdtegs.