- on Sept. 16
Q: Tell us a bit more about your session
A: Let's pin with some strong points on the language:
And some drawbacks:
- It's a dynamic and loosely typed language: great flexibility, but you can harm yourself in a very bad way!
- Refactoring is a nightmare!
- Tooling sucks badly!
In today's world developing a software, a website or whatever you do, among all the other things it is also the 'art of optimizing limited resources'.
If you think about it, we have limited resources in terms of: - People that belong to our development team. - Time spent on design and coding of each person involved.
If you - like me - do not want to waste your time in useless tasks when starting (or taking control of) a project, you start with an assessment session in which you look around at all the languages that are used and which tools are available to ease your job out (and possibly avoid the juniors to make disasters to recover later).
Wouldn't be better if the language (and the tooling) could help us enable some of the rules - with explicit evidence of where the problem is and maybe a hint on how to correct it - and avoid us to lose time writing useless tests, while we should focus on design?
TypeScript does just that!
Q: Tell us a bit more about yourself