THREAD: There has been a lot of criticism levied against @BernieSanders recently following his comment about "working within the context of what Biden wants" as Chairman of the Senate Budget Committee. This thread will explore why this really isn't all that surprising.

So, today, for the first time in 25 (!) years of Apple, I downgraded. From the 2016 MacBook Pro to my 2013, which I had kept in a drawer...

It was pretty simple to do—Apple Time Machine backups let me do it with one click.

That first tweet captures, in two pictures, how badly Apple has “lost the plot” (to quote @wylieprof). On the right is the Apple MagSafe adapter, from 2013. On the left, what I had “upgraded” to.

Thanks, Apple! I really was nostalgic for worrying about yanking my computer off the table.

Oh and I really appreciated not knowing if my computer was charging. What was great was the little whoop sound you used, so that the speaker before me could be informed I was charging my laptop.

Wracając do sedna dzisiejszego zamieszania z artykułem autosportu / motorsportu. Kubica mówi w nim, że podejmie swoją decyzję w ciągu kilku dni. Rozważa opcję z Williamsem lub posadę kierowcy symulatora w Ferrari. Więc za kilka dni dowiemy się co go czeka za rok. #F1PL

Autosport / motorsport zmienił nagłówek swoje tekstu, bo pierwotnie sugerował on że Kubica jest numerem jeden na liście Williamsa na tytuł mówiący tylko tym, że nadal jest na liście kandydatów. Zrobili to po interwencji zespołu. Same wypowiedzi Kubicy z wywiadu się nie zmieniły.

Trudno powiedzieć czy autor się pośpieszył i wyciągnął inne wnioski niż powinien, a może wie coś więcej, ale nie mógł tego otwarcie napisać. Słowa Kubicy brzmią jednak jednoznacznie: decyzję podejmie w ciągu kilku dni.

How to trade on Expiry day with Nifty straddle?
(System trading on Expiry)

Triple straddle is one of the best and accurate methods for expiry day

If nifty trading at 15720 then will sell three straddles above 50 points from ATM, below 50 points and ATM.

Ex.
Sell straddle 15700(ATM), 15650(ATM-50), 15750 (ATM+50)

Stoploss of 80% on every leg and run your trade till 3 PM

Once SL hit in any Leg just keep holding other leg till expiry with SL (Never or less chance to hit both SL on expiry day)

Trading timing at 9:20 the Morning

1/ The first 18 months of starting a company is often life or death. I must've made 5 different companies that each failed within 9 mo. 😭 Each time the company failed I figured out what I could do better. Eventually startup #6 got to $40K/mo by month 18. Here’s what I learned...

2/ Stay focused! Ignore things that are a waste of time: meetups & conferences, meetings with no clear agenda, fundraising if you're not fundraising, reading lots of tech media articles, etc. Every week should feel like significant progress in the first year.

3/ Your first 5 hires will be the difference between life or death. Choose carefully. Be picky. Many of the things we do at the company still are a result of those early hires' legacy. Have fun as a tight knit team. It will change & evolve as you get bigger so enjoy this moment.

4/ Growth may be flat for the first 9 months. It's gonna be okay. Almost every company has experienced this: Airbnb had to sell cereal in-between, Slack failed as a gaming company first, Tesla sold only 147 cars after 6 years! You probably won't be an overnight success either.

5/ In the beginning, do customer support yourself. You will learn a lot about why your product sucks. I did 5,000+ support tickets when it was the two of us. Delight customers & fix things fast while you learn. It will help you build an amazing intuition about your customers.

So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

Wired first reported on how bad Keystone was 11 years ago when they put it into Google Earth (they seem to put it in all their popular

The fact that Keystone hides itself in Activity Monitor is bizarre. (The only sign of it was excessive CPU usage of WindowServer which is a system process).

I don’t know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about). But either way, I’m not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome)...

...since it's been a decade+ and this still hasn't been "fixed".

There is no reason for auto-update software to need to do what Chrome/Keystone was doing. It also has a long history of crashing Macs.