frigen

I read my contracts. I make a risk assessment. I weigh it against likelihood.

I rarely question clients contracts unless they fuck with the payment terms, or unless they impose unreasonable work guarantees. Almost nothing else matters in a contract.

If the contract is unreasonable I don't hestitate to say "this bit isn't practical". If they don't agree to adjust to fair and reasonable terms I drop the client/contract.

I really hate working for companies who impose exploitative terms because they hold the more powerful position in the relationship. I'd rather tell em to go elsewhere.

True, but ideally the framework would lead programmers automatically to ways of doing things in the "right way" instead of overusing local state.

A "better react" would make it natural and obvious to use store versus local state in the appropriate way.

My theory is that any technology that can be simpler will be replaced by one that IS simpler.

New technologies like react either need to fix their problems like lack of integrated state management or be replaced by something that does do it right.

The criticisms of the linked post are valid.

I agree that reactjs would have been better without setstate, instead with tightly integrated Redux, which would remove much of the Redux boilerplate.

For the most part, this is what this reframe thing aims at as far as I can tell.

Setstate really should be long term deprecated, it's a design error in react.

There's really no limit to VCs.

Disappointing that this refers to LinkedIn instead of placing responsibility at the feet of Microsoft.

Someone, at sometime, has previously predicted just about anything and published it, making them appear prescient.

I love JS for front end, but Python is MUCH better suited to back end work, where a synchronous programming style fits perfectly.

>> there's no acceptable way to pass a function body to another in Python

What exactly does this sentence mean?

I'm puzzled that your efforts to pursue expertise in the JavaScript field have not met your expectations.

I set out on the same quest and expected great pain but instead have found enormous satisfaction and success in the JavaScript ecosystem.

Along with massive pain associated with build tools.

Unikernels are a better simpler tech than containers but somehow we're stuck with containers.

Reactjs with create-react-app

Once you've built a couple of reasonably sized applications, then learn Redux.

It's semantics and all about how you interpret MVP.

My MVPs typically are pretty much complete applications. I can't see it being any less whilst still being new and innovative.

I never played D&D.

Promise.

I'm a good storyteller when I'm deeply happy and confident.

Unikernels are a much better solution to the problems that Docker solves.