3 ms·
The thing is that TS is effectively a compiler (I know it isn't _really_ but it is in all but name). Literally millions of developers write code for languages t
by onion2k 6y ago
The thing is that TS is effectively a compiler (I know it isn't _really_ but it is in all but name). Literally millions of developers write code for languages that use a compiler very happily[1]. Having a compile step isn't a bad thing, and the fact it takes a few seconds is fine. Having a development cycle where you're concerned about how productive you are down to the number of seconds things take is just silly. The problem is with the way you work. You need to chill out a bit, take more time over your code, and think things through more. By the sounds of it you can make yourself about twice as productive just by saving your code half as often.
[1] A lot of them look at JS and TS like it's actually worse because there isn't a compiler step.
- cryptica 6y agoThe way I work, I spend several days or weeks thinking, drawing diagrams about the main concepts and architecture, but when it's time to implement, I like to get the project done as quickly as possible. I don't usually encounter unexpected problems on projects; that's what the planning is for. If you've figured out the right architecture ahead of time and you've solved all the obvious technical hurdles in your mind ahead of time, then implementation is very straight forward and yes iteration time makes a huge difference.