“Typed language? Yeah, I’m using a keyboard.”
I am happy there is no obvious “any” type in Rust.
There is, it’s just not easy to use
Yeah, at some point my new team switched off null safety, because some consultants told them to.
Ride into the Danger Zone …
Indeed, and just as my old team fell for consultants, my new team also went ahead and let them add some overcomplex garbage into their codebases. And crap still keeps piling up. It’s just like it’s impossible for them to understand that from an average consultants perspective the only way to go forward is to keep adding complexity, wether they are aware of it or not.
Oh, the consultants know, but they get paid, don’t complain about “risks” and “code debt”, and management only sees their delivery on time without increasing operation costs
Does it compile???
… Compile???
I am currently teaching python and JavaScript devs Typescript. Everytime they hit a problem they switch to any
Sigh
Must be the same people who just comment out failing unit tests.
“Your crappy tests are failing again on my branch. I’ve commented them out until you fix them.”
Sadly that sort of thing got so common where I work that I’ll run the tests three times before considering looking into the error message to see if it is something I broke.
From time to time we take some days just to fix tests with inconsistent results, but there’s always more popping up.
Serious answer: You can’t write tests for untestable code. Your code needs to be pure if you want reliable tests: https://en.m.wikipedia.org/wiki/Pure_function
For integration tests, they should handle retries themselves
typescript is not a strongly typed language
I mean that is the first step. ¯_(ツ)_/¯ The next step is to start defining the types more strictly than any.
Hmmm a more reasonable first step would be to just not even type anything until you’re ready. But TS makes it hard to iteratively type parts of your codebase over time. One could type using JSDoc syntax for these cases, though.
Yeah, true
I’m in this post and I don’t like it.
That being said I try to have specific types in my typescript but coming from working without typescript, there’s so much more words involved using typescript and for what I use it for I don’t really see the use case. Sure it helps you realize what part of the script needs what data types but it adds so much more complexity in the code that I’m not really sure it’s worth in the first place.
Typescript saves ridiculous amounts of time in bugfixes and is IMO a lot more readable than JS.
I don’t know how many times TS has complained about some type mismatch in my code that made me scratch my head for 2 seconds to only then realize I was doing something stupid. With plain JS that would’ve been no issue, until I have some obscure bug 30 minutes later and have to figure out it’s source.
Also, whatever piece of code you are working on, to do anything you have to have the types of your variables/functions in mind. If you have to keep track of all of them in your head, you will definitely mess it up at some point or have to look through a bunch of different methods/files to track down the source of some piece of data to be certain what’s contained in it.
So yeah, TS might take slightly longer to type out, but it saves you a lot of dev time.
I mean I guess that could be helpful, I’ve never really had that issue so I have yet to see the benefit of it. I just find it useless work that you’re typing out for something that the engine itself isn’t going to be able to see anyway, which means you’re going to have to have unit tests coded in regardless. And I wouldn’t say just a little more coding, typescript when implemented into my project doubled the amount of code provided, I’m trying to use it because I do understand it’s a standard, but I really don’t understand why it’s a universal standard, considering that everything it does is completely syntax sugar/coder side and it doesn’t actually interact with the underlying engine. I feel the same way about coffee script honestly.
Just wait until you have to work as part of a team on a big project. The lack of types will murder the team’s productivity
TypeScript is essentially the “measure twice, cut once” approach to JavaScript.
Yeah, anything can be anything in JS and the type declarations don’t make it into the compiled JS, but allowing anything to be anything starts to become fairly dangerous when the size of your projects starts to grow and especially when you’re working with a team.
Rather than writing functions and just hoping they always get called with a parameter that has the properties you expect to use, TypeScript helps you make sure that you always are calling that function with the right object in the arguments. You don’t need to debug some runtime error up and down 8 frames in the call stack because this week you named a property “maxValue” but last week you used “maxVal” or you forgot to parseInt some string because you thought it would be coerced - you just need to make sure your types match and eliminate that type of debugging altogether.
All in all, TS really just enforces a bit of sanity to the foot gun that is vanilla JS.
Yeah I fully agree typescript does help in terms of knowing what type of types you should be supplying to functions, and for the most part I do use it for non-library purpose/anything that doesn’t rely on a third party, I just feel like typescript isn’t worth it when you have data that’s returned at run time that’s controlled by a third party service. You end up coding more in class definition files then you would just using normal tests
