#Weekend #homework
Will post few
#52W high or near #52W High ,
#ATH stock in this thread
#strength
#momentum
#Blacksmith #stocks to watch

@YouTube

Manipulation Sign:

If you are compromising too much, there is a chance that you are getting manipulated.

Why are you the one that's always compromising?

How come the other person always gets their way?

Be more curious.

If something seems off, stick up for yourself.

'Wait, you sure I am being manipulated?'

I have no clue, that is only something that you can decide for yourself.

'Dang is there anything I need to look out for?'

Plenty..

But let me give you a few things to look out for.

👇

I see manipulation as skillfully controlling someone's behavior for egotistical or unethical purposes.

'How come people don't leave when it's happening to them?'

Because most people have 0 clue that they are being manipulated.

1. Guilt Trip

You ever made a mistake around someone, only for them to hold it over your head?

The will always bring up the mistake when you 2 are not seeing eye to eye.

These people will use that mistake as leverage to get what they want from you in the future.

Look out.

2. The Rationalizer

This person will commit the worst acts & find a way to rationalize it.

Example: cheaters when they get caught.

They have every excuse in the book for why they did it.

Heck, they are so good at rationalizing, they will make it seem like your fault.

Most software founders, particularly in B2B, need to get radically better at sales. @Steli , who is the best person for explaining the scrappy stages in the beginning and then building out a team with scripts and processes, wrote a guide to:

For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.

The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.

This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.

"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.

So here is a secret: Not everything I write goes anywhere. I have at least 4 books completely written and edited that never went on submission. I have books that stalled out at 20k. I have docs on my computer with opening paragraphs I don't remember writing. But! 1/

Every now and then an idea sticks with me like that corner of tortilla chip that just won't go down your throat. It happened with SPARROWHAWK, which began as 40k of a YA story, died, and was reborn as a comic, thanks to @christopher_j_r and @boomstudios. And now... 2/

It's happening with THE WILLOWS, a short story that you'll see in @UncannyMagazine next year. This Southern Gothic horror story began as an attempt to sell my next Romance to @AbZurdity after the Blud books in 2014 or so. And she didn't buy it. Guess why? 3/

Turns out, it wasn't a Romance! It was Southern Gothic Horror. Even the bones of it screamed strangeness, not sexiness. I loved the taste of the world, but I hadn't found the right story yet. Tried to write it 2 more times and failed. Until I finally understood what it was. 4/

So I took the 50 pages I'd written and cut half of them, twisting the story around from a gothy Romance inspired by the band the Civil Wars and turned it into a spooky descent into madness. And it looked back at me from the abyss as if to say, DUH. Sometimes... 5/

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.