black-alert

I never walked around the earth and I cannot think of 1 single reason for willing to do that. And although I'm not female I would still expect it to be a risky undertaking, for any living being.

I think we do have a talent shortage, seriously, I see it all the time in the companies I work for. And if you run in an interview like the author describes, it is very likely that the interviewer just lacks talent and happens to be in that position, otherwise he or she would recognise the opportunity and go for a good deal.

But there are also good reasons why companies are often extremely careful hiring new staff. Many companies are desperately seeking the right dev's because they know that the wrong pick can cost them tons of money. The mess a wrong dev can create can do so much damage to the product while it often has to be released within a certain timeframe. I've seen a startup failing because of that.

depends heavily on your bank account

> There is really no way I would maintain that same project without types.

That's bold. Do you think no developer would be able to manage it without TS? In that case you must be a fanboy!

And honestly, are you not using 'any'? And do you think your app cannot crash because of a type error at runtime? And do you trust all the third party libraries you are using that they always provide you with consistent types, also during runtime? I ask this because most TS proponents live in some kind of dream.

Yes it is optional until it gets hard to find a job with typeless Ruby. And indeed split Ruby communities just as with Javascript. The bad thing is that static typing in dynamic languages is HOT, which means if you don't move over to the typed camp you will look old and stupid.

I come from Assembly and C, now working in Javascript. One of the reasons I made the move to JS is dynamic typing, getting rid of that administrative pain and now being able to create stuff much faster. Even in large JS apps I hardly ever have type related bugs at all, and when I have one I fix it mostly within minutes, don't need an entirely different language and ecosystem for that.

Now the JS fanboys discovered and moved (from Coffeescript to Babel ESxx) to Typescript they apparently think that they can write beautiful and bugfree software just because of static type checking! Let them please move to C++ or whatever statically typed language and shoot themselves in the foot by making all those mistakes that have nothing to do with static type checking at all! Oh, and of course hitting the wall because they are missing their precious 'any' keyword!

I totally agree that type checking for dynamic languages should be done in the IDE, tooling. But static typing in the dynamic language world is a hype at the moment, so we'll have to go through a wave static type checking frenzy. For my work I look at horrible code bases, perfectly typed and strictly formatted by tslint..

In some way our brains doesn't seem to be wired for getting rich and famous, most people go very wrong. Being a good and intelligent human being is very different from having just a lot of money and luck.

> People who want to write "beautiful code" are not role models, don't listen to them. They are vain and not productive.

Your thoughts seem to be very subjective. I hope you don't write your code as naive as you wrote this comment.

I code for over 30 years now. It has always been my desire to write beautiful code that reads well, scales well, has no bugs and performs good. Does this makes me a vain imposter and not capable? At this very moment I am working on a total rewrite of an unmanageable codebase that was written by a very 'productive' guy.

I bought the latest version of the MBP with the 'fixed' keyboard last year September. I have sold it 2 months later because one of the keys didn't work well anymore, I had to push that key hard for it to respond. It is amazing that Apple seem to completely ignore all the issues with the new MBP..

The paradox is that the school institution is actually very dumb and stupid where it should be the smartest thing out there.

> Why don't we have more : "We tried it, it is the worst, especially for products which lifespan is more than two months"

Because that last sentence is just rubbish, CSS in JS is great. I'm using it for large projects already 4 years. If your experience is bad you must be doing something wrong. CSS in JS is almost the same as working with (S)CSS, except for extra power to control dynamic elements without having to juggle with classnames.

Redux, made for very large scale applications. Most companies shouldn't use redux at all, just as Dan Abramov said several times that you probably don't need it.

For unknown reasons most front-end developers don't wanna hear that and love to start with mega complexity and boilerplate where just a simple flux store or a library like 'unstated' would suffice. Anything leaner than redux is very welcome for the average companies web app imao.

you mean Python and Ruby like languages are unmaintainable and therefore deprecated? I rarely have a problem with maintainability in JS because of types, but I do have problems with poor constructs, poor readability, dependency issues and so on. It's a typical illusion of TS proponents that code becomes magically maintainable.

JS developers moving to TS should at least do a few weeks of Assembly and C programming to first understand the origin of types. I've spoken too many front-end devs who don't have a clue what a type actually is and at the same time promote TS. It's a godsend we don't need them in scripting languages. Use tooling to catch issues, that's the future, TS is just a whim.