If you play music in modern times, this movie is also informative. I think most musicians who really make innovative tunes are aware of these trade offs, it maps to real life well. There's musicians who make music for other musicians and they're trying to say something they know most people will have a little difficulty hearing.
I guess it tends to be superseded by other forms of rot, people writing a bunch of tests that aren't against the critical path, money going down the drain... I agree, it _seems_ like what you say is true. I'm not a computer scientist, I'm just saying I've tried TS at a couple of shops, and as they team grows TS slows us down. Maybe it's just stochastic or random, but at the end of the day there's no academic "proof" types improve developer productivity. The only thing that sort of gets me is how everyone sort of assumes TS is 'best practice' but there's really no evidence besides gut feeling. My gut feeling is now telling me TS is not beneficial... I'd love to play devils advocate against my own position so feel free to tear me apart...
My experience is by definition anecdotal, but what I've found is as the team grows more and more work seems to focus on defining the types, futzing with the types, talking about the types instead of talking about features. I come from a Clojure/script background so I suppose I'm trying to say if (in building UI's) if you bake in strong immutability and a functional approach (like re-frame... but JS) types, to me, become less and less of a concern. Of course it's highly dependent on the business requirements.
I come from a clojure background, maybe that's why I don't enjoy TS. I find that large projects, so much code is un-necessary, people spend a lot of time troubleshooting types instead of building functionality. Of course it depends on the project. Social security #'s is a different scenario than something like a game or frivolous retail...
null coalescing is good, but I personally found that Typescript doesn't offer many advantages on a large team. I know it's not cool these days! But it just slows me down and if you're reasoning about functions I never run into that many production level issues with types, but maybe that's just my brain I dunno!
I used Typescript for 2 years, and I'm happy to report I'm dropping it and encouraging my team to do the same. Types are for compilers, not people, and personally I think there's more disadvantages than advantages re: time.
Ah, didn't know that. I feel like Covid has me, personally, thinking a lot about how age never mattered more, so that's why it stood out, or seemed off to have 'missed' or whatever. (Futurist world of micro-cities of only young people, old people in rural areas in sterilized cubes and what not)
I know, thanks for your response. I'm 42 so paranoid my tech skills are becoming irrelevant. What a pathetic thing to worry about during a pandemic. Anyway, I think you're really onto something because as a musician I always want to video chat but have everyone be responsible for tuning into a 3rd party, like for group jamming for instance. Keep up the good work!
Also - outside of the bay (I live in Chicago) you actually make more money working for a startup (at least I do) than for a larger company (as a senior engineer with a lot of early stage experience). I think it might be the nature of the market here.
I am a former high school teacher working with Chicago kids age 15-22 (yes). I don't know about you, but they're children to me. They are simply not equipped with enough information to make rational choices in a system that has either by design or evolution _completely failed them_.