Re:Computer science is not software engineering
by nthj on Saturday December 26, 2020 @11:32AM
(#25544400)
More complicated functionality has moved to integrations/APIs in the past 8 years.
When you’re trying to ship an extensive application and building out features that few customers may ever use, types absolutely slow you down. When you’re integrating with a 3rd-party API, you have two differences:
1. relatively high confidence the API won’t change much, which makes implementing typed code lower risk and higher ROI
2. a slower feedback loop over the “reload the page” of rolling your own, so types catching issues earlier than heavy integration tests is much more valuable
I use untyped Ruby/Rails code for all of the CRUD, and golang AWS lambdas for anything integrating with SDKs/APIs. Best of both worlds, in my experience.
When you’re trying to ship an extensive application and building out features that few customers may ever use, types absolutely slow you down. When you’re integrating with a 3rd-party API, you have two differences:
1. relatively high confidence the API won’t change much, which makes implementing typed code lower risk and higher ROI
2. a slower feedback loop over the “reload the page” of rolling your own, so types catching issues earlier than heavy integration tests is much more valuable
I use untyped Ruby/Rails code for all of the CRUD, and golang AWS lambdas for anything integrating with SDKs/APIs. Best of both worlds, in my experience.