Read on Twitter
Having robust tooling and process for development is important, and how not having it can silently suck up your organization's money.
Let's understand this as a case study,
Consider you save your code 15 times a day and go to the screen to see the result.
1 /
Let's understand this as a case study,
Consider you save your code 15 times a day and go to the screen to see the result.
1 /
And if it takes 2 minutes to reflect the changes in screen. (Maybe it involves rebuild, server start, switch from code to screen and hit refresh, steps to reach on specific view)
So total time in a day you spend waiting is 2*15 = 30 mins.
2 /
So total time in a day you spend waiting is 2*15 = 30 mins.
2 /
If there are 30 devs in your org, the total average time spent in waiting will be 30 * 30mins = 15 hours.
In a month it will be 20 * 15 = 300 hours.
And in a year 300 * 12 = 3600 hours.
Let's say average cost / per hour in your org is 500 Rs.
3/
In a month it will be 20 * 15 = 300 hours.
And in a year 300 * 12 = 3600 hours.
Let's say average cost / per hour in your org is 500 Rs.
3/
So total cost per year just waiting will be 3600 * 500 = 1800000 (18 lakh).
Now, this might be less or more for your org, but the point is you are spending a large amount of money on things which could be solved by investing a few days in improving the tooling.
4/
Now, this might be less or more for your org, but the point is you are spending a large amount of money on things which could be solved by investing a few days in improving the tooling.
4/
Here I have put only one problem out of many with low ball numbers.
But the sad reality is you might be spending 20 - 40% (maybe more) of the time in non-productive things like
- Waiting for the build to finish, test to run, deployment to finish.
5/
But the sad reality is you might be spending 20 - 40% (maybe more) of the time in non-productive things like
- Waiting for the build to finish, test to run, deployment to finish.
5/
- Realizing issues late, because you don't have proper linter, static type checker, proper test for your code.
- Zero configured IDEs, manual code formatting.
- Spending time to understand system due to lack of documentation.
- Communication delay due to cross geo timings
6 /
- Zero configured IDEs, manual code formatting.
- Spending time to understand system due to lack of documentation.
- Communication delay due to cross geo timings
6 /
- Re-iteration because the design was not discussed or thought through initially.
(And many more)
So the point I am trying to make here is to automate the repetitive task and fix the tooling and process where ever possible.
7 /
(And many more)
So the point I am trying to make here is to automate the repetitive task and fix the tooling and process where ever possible.
7 /
And convince your org to invest time in fixing tools/process instead of just focusing on shipping features. Do it by realizing them the cost per year they are spending on it if it is not solved.
Also, make it as your development hygiene to keep improving your tools/process.
8/8
Also, make it as your development hygiene to keep improving your tools/process.
8/8
