What problem does this solve? How does it differ from Docker?
820 karma · joined December 17, 2012
As far as I can tell Typescript itself doesn't have a concept of a "Model". Which makes sense because its not a web framework - its a programing language
https://www.google.com/search?q=Model+https%3A%2F%2Fwww.type...
Example: https://www.pugetsystems.com/nav/peak/tower_single/customize...
It's a web browser, but instead of being open source (Chromium) or a non-profit (Mozilla Foundation), it's run completely by a single for-profit company. Seems pretty backwards to me, but maybe I'm missing something?
- Treated me like an equal.
- Offered me a ton of new opportunities which resulted in lots of salary bumps.
That makes no sense. It would be against the company's interest to do that for many reasons.
Is "meta review" really a value add for software companies? Is this advice for Managers of peace-time companies who can't find anything more valuable to do with their time?
Imagine for a second that the manager is wrong in his/her judgement. Now the developer has to choose between arguing with the manager and risk being viewed as insubordinate or just going along with the feedback and letting the software suffer the consequences.
Why assume everyone here keeps a knowledge base? I personally don't.
I imagine their thought process went like this:
Types: People like strongly typed languages, maybe if we call our events "types", they will like Redux more?
Reducers: Switch statements are so boring and uncool. Lets call this "reducer" instead of "events switch statement".
Store: Lets call the state tree "store". The term "State tree" is too explicit and a core principle of Redux is misdirection.
Actions: Mere mortals will associate the term "action" with functions and procedures, but Redux is not for mortals. "Action" will be our term for payload.