Top mistakes that developers do when they come to work.

1. Top developer mistakes
@hanokhaloni
Hanokhaloni
hanokhaloni

2. Let’s talk about…
NGSOFT_

4. a project is a system set to
accomplish particular tasks under
time constraints

5. Pre-Prod Prototype Alpha Beta
Polish /
QA
Publish Sales
Months
A typical project

6. Pre-Prod Prototype Alpha Beta
Polish /
QA
Publish Sales
12 – 24 Months
A typical project

8. Pre-Prod
• FRI morning
Prototype
• FRI 1300
Alpha
• FRI 1900
Beta
• SAT 1000
Polish /
QA
• Sat 1400
• PLAYTEST!
Publish
• Sat 1600
Sales
• Sat 1900
~36 Hours

9. Developer quiz

10. According to stackoverflow, how
many developers are there in the
world (2021)?
A) 5 million
C) 10 million
B) 25 million
D) 45 million

11. According to stackoverflow, how
many developers are there in the
world (2021)?
A) 5 million
C) 10 million
B) 25 million
D) 45 millionIn 2030

12. According to calcalist, how many
developers are there in the israel
(2021)?
A) 400,000
C) 300,000
B) 200,000
D) 100,000

13. According to calcalist, how many
developers are there in the israel
(2021)?
A) 400,000
C) 300,000
B) 200,000
D) 100,000

14. What’s the US male/female ratio of
software developers (2021)?
A) 71% male, 29% female
C) 81% male, 19% female
B) 50% male, 50% female
D) 86% male, 14% female

15. What’s the US male/female ratio of
software developers (2021)?
A) 71% male, 29% female
C) 81% male, 19% female
B) 50% male, 50% female
D) 86% male, 14% female

16. The average age for a software
developer is
A) 30 years
C) 35 years
B) 40 years
D) 45 years

17. The average age for a software
developer is
A) 30 years
C) 35 years
B) 40 years
D) 45 years
Actually
39.8

18. According to stackoverflow,
percentage of developers with less
than 5 years of experience is?
A) 15%
C) 35%
B) 25%
D) 40%

19. According to stackoverflow,
percentage of developers with less
than 5 years of experience is?
A) 15%
C) 35%
B) 25%
D) 40%
Actually
35.67

20. There is an exponential
growth in junior
developers

22. Top developer mistakes

23. Your job is all about
code

24. What does a carpenter do?

25. What does a busdriver do?

26. It’s not about the tools

27. It’s not about being a code
monkey churning out working
code

28. You don’t become a 10x developer
by typing 10 times faster

29. Solve problems with less code*

30. Tip - Always ask yourself -
Would I like to use this software?
If not -
How can I do something different?

31. If only the business
would get the
requirements right

32. It doesn’t quite work that way…

33. It assumes that someone else’s job
is to tell the developers what to
do?

34. Great ideas were prototyped
without understanding the
requirements

35. You users rarely understand the
requirements

36. We need to evolve software

37. Requirements rarely lie on the
surface…

38. They’re buried deep beneath
layers of assumptions,
misconceptions, and politics

39. Tip - Often the first step is to
discover the real problem

40. Pro Tip - Use modularization to
support change

41. The only thing that
matters is speed

42. Typing speed alone will not
improve your performance

43. Allow yourself time to think

44. Plan before coding

45. Once the problem is clear the
coding is easy

46. Optimising work (so that everyone
is busy all the time), has been
proven to be wrong

47. You are paid to think

48. Tip - Optimise the learning

49. Pro Tip - Practice some TDD

50. My job is to code - not
to understand the
problem domain

51. Knowledge of tools is important,
but it’s not just that

52. Domain experts are too close to
the problem

53. Try to see the real problem in the
real world

54. The best programmers has
enough domain knowledge

55. The programs use domain terms

56. Tip - work on common language
with domain experts

57. Pro Tip - Learn about BDD

58. Software architecture is
for experts

59. If you can’t explain it, it means that
you don’t understand

60. Where do software architects
come from?

61. Describe the system

62. The system is
written in C++
and uses
microservices
deployed on
AWS

63. The system
allows users to
transfer money
securely
between each
other.

64. The system is
written in C++
and uses
microservices
deployed on
AWS
The system
allows users to
transfer money
securely
between each
other.

65. What ideas help you decide where
to place failure?

66. What’s the tourist map?

67. You are the of architect of your
own code

68. Tip - Answer - What does it do and
how does it do it?

69. Pro Tip - Can you explain the
system to your mother?

70. Asking for help is a sign
on ignorance

71. Smart people, ask questions

72. The more you know about
something, the more you know you
don’t know

73. Dumb people, think that they have
all the answers

74. Be comfortable with uncertainty

75. Ask questions!

76. Tip - Ask questions!

77. Pro Tip - Asking the same question
too many times might be a
problem…

78. Testing is someone
else’s job

79. How do you know your code
works?

80. Do you automate your tests?

81. If we fix a problem, how can we tell
it has been fixed?

82. Use double booking

83. Tip - Automate tests

84. Pro Tip - Prove that your code
works without running your
product

85. I would like to do a
better job, but my boss
won’t let me

86. Does anyone limit you to use a
debugger?

87. Does anyone limit you to use a
keyboard?

88. You have to tend your tools

89. It is better to ask for forgiveness
than to ask for permission

90. Tip - your estimates should
include refactoring and testing

91. Pro tip - spare some time to
improving your tools

92. In Closing

93. Your job is all about code
If only the business would get the
requirements right
The only thing that matters is speed
My job is to code - not to understand the
problem domain
Asking for help is a sign on ignorance
Testing is someone else’s job
I would like to do a better job, but my boss
won’t let me

94. We are the experts,
it’s our profession

95. We must take responsibility
for our work

96. @hanokhaloni
Hanokhaloni
hanokhaloni