#Happiestmind - #daily
consolidating from more than 2 months , next rally 🚀soon
weak on closing below 1300 only.

@CAPratik_INDIAN @Investor_Mohit @PAlearner @Rishikesh_ADX

On December 25 Mr Pool retweeted August 16 message about the Phoenix and that the worst was still on the horizon to come. 1/*

Maybe now we can assume that November 3 message meant "FUD" nor "FUN". Putting the word in capital letters seems to indicate the aspect the word fud has in our space, FUD. 2/*

Brad started it on December 22 (1/3 posts (Don't say? Sure) = 13 = Plan B). 3/*

And immediately the SEC followed dropping the bomb (1.3 billions (Don't say? Sure) = 13 = Plan B). 4/*

FUD materializes, Bitstamp is one of the first that haltes XRP trading and so on. 5/*

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.

THREAD: I'm looking at a Huawei P20 from China, let see what can I found

The 1st app I reversed is an app called Decision

Look at the name of the files contains in the assets folder:
- airport_china.txt
- city_china.txt
- cityinfo.db
- parkinglot_china.txt
- railwayinfo.db
- trainInfo.db
- trainstation.db

Interesting, no?

For example, the trainstation database contains:
- address
- name
- latitude
- longitude
- city

In the manifest of this application, there is a GeoReceiver

It is 2018 and this error message is a mistake from 1974.
This limitation, which is still found in the very latest Windows 10, dates back to BEFORE STAR WARS. This bug is as old as Watergate.

When this was developed, nothing had UPC codes yet because they'd just been invented.
Back when this mistake was made, There was only one Phone Company, because they hadn't been broken up yet. Ted Bundy was still on the loose. Babe Ruth's home run record was about to fall.

When this bug was developed, Wheel of Fortune hadn't yet aired. No one had seen Rocky Horror. Steven Spielberg was still a little-known directory of TV films and one box-office disappointment. SNL hadn't aired yet. The Edmund Fitzgerald was still hauling iron ore.

WHEN THIS STUPID MISFEATURE WAS INVENTED, THE GODFATHER PART II HAD JUST OPENED IN THEATERS.

So, why does this happen? So Unix (which was only 5 years old at this point) had the good idea of "everything is a file" which mean you could do things like write to sockets, pipes, the console, etc with the same commands and instructions.

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.