DEV Community

ktfth
ktfth

Posted on

Adventures in TypeScript Typescript System

Write modern systems is a hard task, if you not followed the tendencies accross the internet. There's something important to consider here, you need time to live and enjoy the life isn't?

Become a successful programmer or a developer, and even a engineer, you need to consider those thing's. And it's magical!

In my past experiences I dedicated some time to learn almost every concept I need to know how to be prolific with JavaScript, when TypeScript come to live, I just ignored what I've learned from JavaScript and try to clean my mind and focus on this new language.

For me, learn the new language quietly become a hard task, to setup the environment, understand how conditioner the compiler give me answer's and apply this effectively on a profitable project is a major thing that I wanted, to avoid loss all the perks the language offer.

But something come to mind, why I need that? And how to capture indicators of that change?

This kind of questions come to mind, with TypeScript and all the other technologies we choose. When something new pop's up, you need to hack around and discover your way, nothing delivery's more value than a good approach of what's you expect, the client expect or your users need.

Useful stuff to follow:

  • source code
  • change logs
  • channel's
  • reverse engineering other application's
  • put thing's together

Don't trust other people say, if you want, try yourself and move fast!

Understand concept's behind a certain technology's, involve a bunch of experimentation and collaboration.

What you want to achieve? My goal is money, and I believe the money is in certain way a expression of wisdom.

Be carefully with anxious bahvior to adopt a technology just by the fact is cool, search your own way to make a change in the world with good quality code and discover why create a state of art piece of software is a concern. Sleep well without the fear of your software stop, without any clues for a investigation is a bad thing to happen.

Here the piece of wisdom extract from type system of TypeScript:

  • Modern compiler infrastructure
  • Tools supporting the language without a need to run at your own the code you need to made
  • Flexibility at choices you need to made to deliver portable code
  • Interop with JavaScript concept's
  • Good mapping of what you are doing with your code
  • Reusability with documentation based on types you or other's made it
  • Modern modules base on the language
  • Huge community
  • Supported by big company

This is my thoughts about a good roadmap to learn new things, It is not perfect, but I feel comfortable with that, to cut a pathways down.

Nice to here from you if you can type your opinion about this approach and let's hack together?

Cheer's!

Top comments (0)