(no title)
SansGuidon | 1 year ago
That's also a fact that the easiest an activity becomes the more we can become addicted to do it without thinking. The less we look for alternatives.
Why doing a meeting of 30min when 3000 lines of code can do it. Who cares who will maintain our code as long as we become the hero of the team by typing 10.000 loc overnight.
We are the faster. We win every discussion by typing more and faster. We impress. We throw more jira issues in backlog than everyone else. We dont see the need to slow down or refuse a task because our typing speed gives us more privilege and power.
So one key thing is becoming constrained also makes us more creative at problem solving. Maybe working more is not the key, maybe coding more is not the key goal. Maybe one line of code or a product can solve our problem. Maybe some llm, maybe our of our 100 ideas per minute, only one is relevant and maybe it won't be useful by next week. Good ideas are not always the newest ones.
I also consider on average programmers read more code than they write. I've often helped very busy people whose time was focused on reinventing the wheel and frameworks because they were proud of their coding skills and avoided looking elsewhere for existing solutions. I also haven't been the fastest programmer but always the one able to read code and find bugs better than peers. I'm not proud of typing more unnecessary and buggy code which will then slow us down through debugging and maintenance.
Observability, and quality is important, more than quantity and speed. And as for most things, speed also amplify some negativity, chaos and noise, in my experiences.
No comments yet.