ApolloHospital

Looks bearish and could test 3827.
Cmp 4377, if it manages to close above 4433, then trade fails.

This post is pretty bizarre, but it manages to hit on so many false beliefs that I've seen hurt junior data scientists that it deserves some explicit

(1) The notion that R is well-suited to "building web applications" seems totally out of left field. I don't feel like most R loyalists think this is a good idea, but it's worth calling out that no normal company will be glad you wrote your entire web app in R.

(2) It is true that Python had some issues historically with the 2-to-3 transition, but it's not such a big deal these days. On the flip side, I have found interesting R code that doesn't run in modern R interpreters because of changes in core operations (e.g. assignment syntax).

(3) "Most of the time we only need a latest, working interpreter with the latest packages to run the code" -- this is where things get real and reveal some things that hurt data scientists. If this sentence is true, it's likely because you don't share code with coworkers.

(3) Really is a broader issue in data science: people only think of what they need to do their work if no one else existed and code was never maintained. Junior data scientists almost always operate on projects they start from scratch and don't have to maintain for long.

Starting a startup is hard. This thread will contain some key advice I think are particularly noteworthy:

1. “If you’re not embarrassed by the first version of your product, you’ve launched too late.” - @paulg The first version of my product was not great, but hey, it worked.

2. Don't build in a vacuum. You should build your product out in the open for the world to see. You will gain valuable feedback from users if you build publicly, and provide insights which ensure you are building a product users truly want. cc @rrhoover @sama

3. As a young founder, a massive weakness is age and the lack of credibility. Developing partnerships, trying to acquire customers. etc have all taken so much longer. In fact, when I mentioned my age, a few investors just walked away. cc @Jason

4. Work on what makes you feel excited. Working on something that you don't believe in will cause you to make rash product decisions, resulting in loss of user loyalty. @fredwilson

5. Take care of yourself. While doing the occasional code sprint can be incredibly useful, working 24/7 and disregarding your health just to build a great product is not a wise choice.

In regards to the #CapitolCoup, I’m in a unique position. I monitored forums ahead of time and then was present for the coup itself.

These are my observations based on what I saw and the evidence that’s been collected so far. I reserve the right to adjust my analysis as needed.

Let’s talk about the organization of the coup first. Seeing some people insist that the coup must have been highly planned and coordinated.

Yes and no. This was a #StochasticCoup. We’ll see little evidence of direct communication between Trump and the insurrectionists.

Within the insurrectionists, there was not one group that executed the storming of the Capitol.

Rather, there were a number of smaller groups working independently towards the same goal. I expect you’ll see little evidence that these various groups communicated with each other.

What you will see is detailed planning and coordination within these small groups.

Then there were the joyriders, those Trump supporters who weren’t directly involved in any plotting but who were more than happy to go along for the ride once the coup was in motion.

After four years, the insurrectionists were carefully attuned to Trump’s messaging.

Every tweet and statement of his was treated as marching orders and carefully dissected for meaning.

It’s why shutting down Trump’s Twitter account was so important.