Hey, who wants to read a story about @Upwork fucking over freelancers in order to upsell their clients on unnecessary services the clients don't want and can't afford? Strap in!

So after my marketing agency closed I started freelancing again. A marketing company that wanted to work with me only hires freelance writers through @Upwork. So I signed up. I wasn't thrilled about it, but that's who they contract with and it's their marketing company.

I've been receiving regular assignments from this company, thru @Upwork, for over a month now. I've written dozens of articles for them. My work has been exemplary. I've been handling repeated rush jobs and delivering. The client was and is very happy. That's coming from them.

While I was wrapping up several assignments this week I was contacted by the marketing company. They asked if I had taken a new full-time job and wasn't available anymore. It seems @Upwork's talent group told them I was no longer available to take assignments.

I was very surprised. Nothing had changed on my end. I still needed the freelance work very much. I told them so. So the marketing company pressed @Upwork and were told there were "compliance" issues that were preventing the marketing company from giving me any more work.

We’ve recently seen research about so-called “bots” and misinformation on Twitter and wanted to share our perspective on why findings that might seem remarkable at first are likely inaccurate. We’re working on a more detailed explanation, but some comments for now.

We continue to be excited by the research opportunities that Twitter data provides. Our service is the largest source of real-time social media data, and we make this data available to the public for free through our public API. No other major service does this.

Many researchers, academics, and journalists use our public API — a set of tools for programmatically accessing information on Twitter. We make all public Twitter content available via our APIs. You can learn more about them here:

The basic issue with much of the research based on our public APIs is simple: The APIs don't provide insight into our defensive actions to protect Twitter from manipulation, including bots.

Because of this, API-based research can't distinguish between accounts we've already identified as bad (and hidden or removed) and real, authentic ones.

Oh are we talking about Sheryl Sandberg again? Well, your reminder that disabled feminists, LGBQT feminists, and feminists of color criticised her ‘lean in’ deal from day one. Don’t let anyone retcon that out of existence.

Like, a pretty narrow slice of feminists actually endorse and support corporate feminism, they’re just white, nondisabled, straight, cis, and noisy so their voices have a bigger reach.

So if your impression is that ‘feminism’ gave her a ‘free pass’ maybe you should question your overall impression of feminism rather than continuing to centre a handful of people as ‘thought leaders’ or whatever.

Critics within feminism have been doing this work for a long time and have been getting shat on it for about as long and I'm tired of seeing them erased. But what do I know — I am, after all, not a feminist.

But I WILL say, from my not-a-feminist perspective, that people who aren’t feminists who are criticising feminism should maybe understand the movement more deeply beyond a handful of high profile celebrity feminists.

Great thread full of potential https://t.co/jA8h08M48z ideas! 💡

📸 Social disposable camera app

Create a digital "roll" with friends. Take pictures from the roll. You can't see them until: the roll is used up, a time limit expires, or you get to a specific location.

🎙 Asynch interview platform

Send a guest a video or audio clip asking a question. Guest replies when able with same medium. Repeat. When done, share produced video/podcast.

✅ 24 Hour Startup Checklist/Overlay

A web app to track the progress of your project: ideation, naming, shipping code, launching.

Page can also be a dynamic browser overlay for live streaming.

Have tools for polls, surveys, sharing, launching to various outlets, etc.

👩‍⚖️ Healthcare "Lawyers"

If health insurance screws you over, no one has your back but you. Instead, can pay a small monthly fee to a service to take care of BS like this for you should issues arise.

Today we’re going to talk statistics and semantics. I’m going to do so via the medium of one of Twitter’s favourite stats 1.7% (aka “intersex is as common as red heads.”). The statistic comes from Fausto-Sterling’s work, which you can see a review of

To understand the statistic, we have to drill down into what the meaning of the word intersex is. Most people think of hermaphrodites. Let’s stress at the beginning there has been no example ever of a human being with both sets of working reproductive organs.

There is a very tiny percentage of people who are born with both testicular and ovarian tissue (what Fausto-Sterling calls “true hermaphrodites”). And when I say tiny, we’re talking intersex tiny, as in 0.0117/1,000 live births, or one in 1,000,000. These are very complex cases.

So, how do we arrive at 1.7%? What Fausto-Sterling does is apply a wider scope. Instead, she argues that intersex is anything that doesn’t fit into a platonic ideal. The platonic ideal, in this case, being a phenotypically perfect XX female and a phenotypically perfect XY male.

This means that intersex, used in the context of the 1.7% statistic, includes people for whom there is no sexual ambiguity. Take for example Klinefelter syndrome (XXY males). As Fausto-Sterling acknowledges, many males can go their whole life and not realise they are XXY.

Google's interview system is not great but there are various reasons why it feels less than it is. Most candidates don't know what the goal of our interviews are. First rule, it is not about finding an optimal solution or any solution at all.

You are interviewed for multiple skills simultaneously. Cognitive skills, communication, leadership are a few to name. If the point is not finding a solution, then what is it? Let me explain.

Your interviewers try to understand what it feels like to work with you on a daily basis. An interview question is just a tool in achieving that, it is not there to specifically measure your skills on a topic but a tool to understand the depth of your thinking.

Before the interview starts, ask them what they want to get out of this interview. Good interviewers should already have a plan and a set of expectations. Ask them what you should do. Don't start coding yet. Ask them you should produce. Discussion, diagrams, pseudo code, code?

Then, start cracking the question. List whatever questions you think it is important to solve this question, ask your edge cases. Get to a point where you are discussing about pros/cons of the solutions. These steps are critical. Don't just start coding. Have a consensus first.

1) Looking back on my "career" with @TheNordicWeb over the last 5 years, in retrospect it's easy for me to join up the dots and make sense of the journey:

#cphftw #sthlmtech #helyes 🇩🇰🇫🇮🇮🇸🇳🇴🇸🇪

2)

- Join & start community initiatives to meet people
- Learn from these people about how special the Nordic tech scene is
- Share this with the world through The Nordic Web
- Realise the real value is in the data, particularly in building network
- Use network to raise a fund

3) In fact, it looks all very strategic, but the reality is anything but.

My lack of vision and goals during this 5 year period was _criminal_

Any movement from one step to the next was never pre-planned and was instinctive, or worse, accidental.

4) While I am embarrassed to think of my headless chicken self, there's also part of me that thinks that none of this would have turned out where it did if I had of been deliberate and strategic about this.

5) In fact, I think my genuine love for the Nordics and the ecosystem is the MAIN reason to explain how I raised my fund & managed to move from step to step.

My story is a good example of how passion can be more powerful than strategy in the early stage of an idea/company.

Why did I leave Google? A thread.

This thread is going to include quotes from Wired's "Three Years of Misery Inside Google, the Happiest Company in Tech" because I'm not a professional writer

When I joined Google, I fell in love with the company immediately. I was excited to come to work, not just for the technical challenges, but because I really felt I was making a difference and working for the good guys.

I spent 20% of my week working on an app that helped people find lost loved ones after natural disasters. I spent more free time speaking to students about technology and diversity. For an entire school year, I taught CS classes twice a week at a local low income high school.

The company was open. We had a weekly meeting called TGIF where anyone in the company could ask questions of, and raise concerns with, the execs. We got real answers.

Just published 15,000+ words on security keys. 🔐📱💻

With SIM attacks at their highest, now is a great time to take a closer look at your online security.

Removing SMS from your two-factor auth is a start, but authenticator apps have downsides too...

https://t.co/Dk0MPJHL2V

Just look at these headlines from recent SIM swap and port attacks.

It's all too established for attackers to find ways to socially engineer control of your phone number and start gaining control of your accounts.

I first talk about some general security tips.

Unfortunately not all websites let you remove your phone number from accounts.

You may consider migrating your phone carrier to @googlefi , which requires email account access to do anything (and can be locked down with security keys and even Advanced Protection)

Beyond SMS, I talk about issues that TOTP authenticator apps (the code generators) have as a form of two-factor auth. They're so, so much better than relying on SMS for your second factor but they still have issues like utilizing shared secrets and lacking phishing prevention.

Enter security keys!

Utilizing public key cryptography they don't have any shared secret between the client and the server. They prevent phishing by taking the website domain into account.

Even if you get tricked by a clone phishing website, your key won't.

Originally, tweet length was 160 minus username length. One day, I turned to Jack and pointed out that I got one more character than him. He said, "That's not fair. We should standardize." I agreed. He said, "How about 140?" I said, "Sure." And he updated the code.

Last year, we upgraded tweet length to 280 and guess what? Use of 'please' is up 54% and 'thank you' is up 22%. I love that! Also, people are asking more questions and having more conversations. All this, and the majority of tweets are still under 140. It worked.

What happens when a skill you have becomes obsolete? No, this isn't a R vs. Stata thread---it's a thread about a working paper w/ @sonnytambe!
https://t.co/w6nLf1tnST

The skill we look at is Adobe Flash, which @apple decided to no longer support back in 2010, which in turn caused demand/interest to plummet, as measured on @StackOverflow and in online labor markets, one of which is our empirical context

Despite the big fall-off in Flash jobs posted, very little else appeared to change in the market for Flash skills: wages for Flash jobs didn't fall, jobs didn't become easier to fill & openings weren't inundated with out-of-work Flash programmers

What happened was that (a) new entrants stopped specializing in Flash and (b) at least some existing Flash specialists started moving to other skills. In short, the demand shock quickly became a supply shock

At the level of the individual Flash worker, using a matched sample, we find (a) no fall-off in their wages, (b) some decline on-platform hours-worked. The most-focused on Flash workers had substantial increases in application intensity and a movement towards new skills

[1/4] Ok this is really funny, check this out.
I was in the process of booking a flight via @OneTravel. Trying to make me book ASAP, they claimed: "38 people are looking at this flight".
Whoa, 38 is a lot, I have to hurry up. But first I have to check how they came up with 38 >>

[2/4] Right click and a quick "inspect" on the number, I found out the element's class name is "view_notification_random".
Awesome variable naming guys.
So you're _randomly_ trying to freak me out. Alright >>

[3/4] So what's your sophisticated pseudo-random algorithm?
Apparently, OneTravel are choosing a number between 28 and 45.
Because as you all know, based on serious psychological research, these numbers tend to make people book their flights fast #sarcasm #not42 >>

[4/4] Here's a bonus graph.
Thanks @IddoYadlin and #WolframAlpha.

Most commit messages are next to useless because they focus on WHAT was done instead of WHY.

This is exactly the wrong thing to focus on.

You can always reconstruct what changes a commit contains, but it's near impossible to unearth the reason it was done.

(thread)

Think about the last time you `git blame`d something.

You were almost certainly thinking "WHY is this like this?", not "What is a one-line summary of what happened in this commit?".

Here's the antidote: use this commit template (stolen from @joeferris).

```
[one line-summary of changes]

Because:
- [relevant context]
- [why you decided to change things]
- [reason you're doing it now]

This commit:
- [does X]
- [does Y]
- [does Z]
```

Leading with the WHY has tremendous value.

First, it captures context that will be near impossible to recover later. Trust me, this stuff is gold.

Secondly, if you train yourself to ask why you're making every change, you'll tend to make better changes.

Give this template a try for a while.

The first time you see a commit message like the above instead of "refactor OrderWidget", you'll be a convert.

help

stuff. just stuff. its all too easy to order more stuff. so much stuff. I dont need any more stuff but I cant stop ordering stuff.