Typescript ( Declarative Polymorphic Type Safety in General ) Allows for Aggressive Solutioning

 


Me, in another role, to a lead engineer on the team, who is so bogged down in code reviews now that the team is more than 3 engineers that he's become a bottleneck.  

What I want to say is "You know, if we had tyepscript, we wouldn't’ need you to spend as much time reviewing. You know that right? like,  yeah, we can be a lot more aggressive with typescript…". He felt he needed to be involved in every MR to thoroughly vett and scan for issues caused by a lack of tribal knowledge. He didn't catch the irony in that sentiment, given how vehemently he had rejected typescript, which does that job automatically, and near instantaneously, at compile and develop time, early in the process, and well before a complex change has come in as a merge request.


Background, our lead doesn't like typescript because the first time we tried to apply it, he lost half a day trying to get  his local env building. We then had a debate on the team, on whether or not to onboard it. I lost.



The point is, the only way to scale a business, is with declarative stable contracts. Otherwise you have n^2 communication overhead costs to maintain your business. Where n is the number of engineers you have purchased to solve your ever more complex business application.

This until your business collapses under its own weight and you can't develop any new features without breaking 10 others.

Comments

Popular posts from this blog

Define "Scalar Value"

AI Self Awareness in Video Games

The World of Conceptual Data Modeling