The client was always a scary landscape to me. Not necessarily because of the many inconsistencies of the browsers. Not because of the idiosyncratic and plain silly parts of javascript, the chosen language of the client. Not even…

I don't trust the client. This, I always thought, is a good thing. A back-end developer should not trust the client. Every input should be validated and mistrusted, all possible interactions with that less (and less-than)… https://t.co/ass4i10pP7
I think some of the inherent conflict, not enmity - never that obvious, between front-end and back-end stems from such mistrust. How can we not mistrust them? To us they are a load of hippies using toy languages and eldricht incantations to work around… https://t.co/8x77CB0OGS
But, something has changed. The browser-wars have quieted down somewhat. Javascript performance has begun to approach a qualitatively acceptable domain. HTML has matured and with FlexBox and Grid even CSS is starting to make some sense (if I squint at it).
And now we have Web Assembly. I'm not going to poke into that with my time and effort, I lost enough nights to assembly back at university. After that i took a look at Java and later C#, and decided that life is far too short to spend it managing… https://t.co/OicCf6EqoE
Still, my main fear lingers. I can now write code in a language that suits me and the problem-domain. I can make the interface in HTML and CSS that makes sense (even to me) and have that all run on the client. Think about this! Purely… https://t.co/rJnPCSwemM
But, still, can I trust it?
I can have the client run my code and do the majority of the work there, and just send the tasty, valuable morsels of calculated data back to my vault in the cloud.

The client remains on the outside, in the wild. A renegade piece of code. A… https://t.co/jKyjQVgnVV
What do we do to trust the client, like we trust our servers? I realise the inherent fallacy of trusting some unknown, transient server in some cloud-provider's hopefully well-protected lagoon. Nevertheless it feels like less of a stretch than actively… https://t.co/cc9TSVzYzU
What I need is to somehow sign my code and make sure that code is what produced the input i receive back. Something that follows my code out into the wilds and tags along with data back to certify that it was really produced and transmitted in… https://t.co/rFo3SDFlst
/end

More from For later read

You May Also Like

My top 10 tweets of the year

A thread 👇

https://t.co/xj4js6shhy


https://t.co/b81zoW6u1d


https://t.co/1147it02zs


https://t.co/A7XCU5fC2m
MASTER THREAD on Short Strangles.

Curated the best tweets from the best traders who are exceptional at managing strangles.

• Positional Strangles
• Intraday Strangles
• Position Sizing
• How to do Adjustments
• Plenty of Examples
• When to avoid
• Exit Criteria

How to sell Strangles in weekly expiry as explained by boss himself. @Mitesh_Engr

• When to sell
• How to do Adjustments
• Exit


Beautiful explanation on positional option selling by @Mitesh_Engr
Sir on how to sell low premium strangles yourself without paying anyone. This is a free mini course in


1st Live example of managing a strangle by Mitesh Sir. @Mitesh_Engr

• Sold Strangles 20% cap used
• Added 20% cap more when in profit
• Booked profitable leg and rolled up
• Kept rolling up profitable leg
• Booked loss in calls
• Sold only


2nd example by @Mitesh_Engr Sir on converting a directional trade into strangles. Option Sellers can use this for consistent profit.

• Identified a reversal and sold puts

• Puts decayed a lot

• When achieved 2% profit through puts then sold