3 ms·

I was on team dynamic for a long time and have moved to team static. For any long-lived code base, dynamic piles up invisible problems over time. It's great f

I was on team dynamic for a long time and have moved to team static. For any long-lived code base, dynamic piles up invisible problems over time. It's great for short-lived throwaway stuff, but as soon as you know you'll be maintaining a large code base for a long time, the "easier" part of dynamic actually becomes harder than just spelling stuff out. It's obviously a trade-off and not everyone agrees, but that's my personal experience having run large eng teams for both types.

slashdev 5mo ago
This is exactly my experience as well. If it were up to me, I'd start out by using the AI to port a Python web app to a compiled language like Go. Then we could maintain that going forward instead. In reality, a Python code base is maintained by Python programmers, most of whom would vote against such a change.