Generics enabled by default in Go tip

Re:Generics enabled by default in Go tip by Taek on Saturday August 21, 2021 @08:54AM (#28256606)

You definitely want to optimize for people who are new to a codebase. Over enough time, the codebase grows to a point where essentially _everyone_ is new to each area of the code, because nobody has touched that code in 2-3 years and the person who wrote it may not even be with the project anymore.

Even for your own single-person projects - if you get fancy with the code, 6 months later you find it's a lot harder to get back into and mess around with than if you had written the code as though you were presenting it to a beginner.

[ Parent | on HN ]

Re:Generics enabled by default in Go tip by erik_seaberg on Saturday August 21, 2021 @08:10PM (#28261764)

Management is responsible for making sure that doesn’t happen, by retaining experts and demanding documentation and investing in ramping up new experts. Making the code bigger because each line does less is not going to save us from nobody understanding prod, and a short learning curve puts a low limit on the value of our staff (who quickly run out of tools and stop improving in clarity and productivity).

[ Parent | on HN ]

Re:Generics enabled by default in Go tip by fiddlerwoaroof on Saturday August 21, 2021 @01:32PM (#28258846)

You want patterns that are well-known to the maintainers, but this is different from “optimizing for the new”: consistent idiomatic use of a library like XState or Ramda in a JavaScript project can cause a high onboarding cost (because the new developers don’t know the library well) without any corresponding ongoing cost.

[ Parent | on HN ]