Software development topics I've changed my mind on

> Typed languages are essential on teams with mixed experience levels

I'm 30 years in now, and on balance, whilst they have clear advantages, I'm still not convinced that typed languages are essential, particularly for low level or module programming.

Unless you can happily deal with '"four" + 1' your language is typed. The question is whether you want type errors reported upfront or you have to wait to find them at runtime (necessitating high test coverage).

One of these days I'd like to see a "typed assembler". It still matters what the contents of registers mean, even if they all look the same to the instruction set.

Interesting take, to me it is not so much about the type of coding (high vs low level) but more about the size of the project.

Dynamic languages work great for scripting and rapid prototyping, but if you are working with a team maintaining a large monolith, I would rather have a statically typed language and avoid at least a class of runtime issues due to dynamic typing.

Case in point, I love writing my Jupyter notebooks with Python but am amazed that entire platforms like Dropbox (and instagram?) chose Python as their default language.

I think the sentiment was they help significantly when you have inexperienced programmers. (That has also been my experience)

What do you mean low level?

Do you think the Linux kernel could be written in a language without types enforced?