BC INTERNET

Saved by @CodyyyGardner

$Alberto Gimeno \U0001f3f3\ufe0f\u200d\U0001f308\U0001f1ea\U0001f1f8\U0001f49c\U0001f90e$

Alberto Gimeno 🏳️‍🌈🇪🇸💜🤎
@gimenete 5 years, 5 months ago 877 views

Save to PDF Share See On Twitter

I'm going to tell you a little bit how we work on features at GitHub. It's simple, but very powerful in my opinion. At GitHub we have a high performance culture.

We are deploying changes almost all the time while keeping the service running and the deployment failure ratio needs to be super low! We are constantly working on new medium/big features, we have frequent deploys and required peer reviews.

How do we know that big features are not conflicting with each other in functionality and in version control. How do we merge the work done in these non-trivial features? How do we do prevent peer reviews slow down our productivity?

With basically two things: split the work in small batches and feature flags. We don't have long-lived feature branches. We do very small changes all the time and deploy them.

We could split a feature in tens or hundreds of PRs, but until it is beta or GA, we don't expose it to users by using feature flags.

A change in the data model, a new endpoint, a change in one screen in the UI,... all those are small changes: easy to reason about, easy to review, harmless to deploy, very low chance that it conflicts with something else.

Also these batches can be worked in parallel so you can have a few PRs waiting for review, but typically you can keep doing work on another small part of the feature.

I'm writing about this because when talking about feature flags most people think about features already finished. We use feature flags for features under development too! And it is super helpful and changes the way we work with git.

Like I said, we don't use long-lived feature branches, which simplifies everything because allows us to do incremental changes to our features and reduce the deployment failure.

More from Internet

Pasquale "Pat" Scopell...
@ThyConsigliori

29 December 2020 #MAGAanalysis #Overturn

Comments On @OptimisticCon Article:

The key supporting effort appears to be underway on Trump’s operational timeline

As we emphasized yesterday, J.E. Dyer commands us: "But do hold the line."

Eric Seufert
@eric_seufert

Facebook -- having taken out full-page ads in the NYT, Washington Post, and WSJ -- is generally seen as the primary victim of the new app privacy controls coming in iOS14. But Google is perhaps even more vulnerable to ATT. Why has Google remained silent? (1/X)

2/ First, background: here's a high-level overview of how ATT / IDFA deprecation impacts advertisers and ad networks, and why this whole ordeal has put advertisers and ad networks into a state of panic:

3/ Google is equally as susceptible to harm from ATT as Facebook. Google's UAC product -- esp its tROAS and tCPA campaign objectives -- relies as much on IDFA-indexed monetization and engagement data as FB's mobile product does. But Google has one big weakness wrt ATT: YouTube

4/ Broadly, view-through attribution accounts for a disproportionate % of conversions from YouTube app install impressions. This means: user sees the YT ad, doesnt click, downloads app later, & Google is able to claim it by reconciling IDFA seen at impression to IDFA seen in app

5/ View-through attribution is nonexistent in the ATT paradigm as it relies on the IDFA; some significant portion of YT's attributed conversions will evaporate. So why isnt Google vocally opposing ATT? Two reasons: consumer optics and its duality as ad network / mobile platform

Advertisement

Giovanni Pagano
@giovanni_pag

What are the implications of using hacked data for research?

A short thread inspired by the fact that, before AWs took it down, #Parler was extensively hacked and user data was leaked.

The #Parler dataset seems crazy interesting for doing research, and my first reaction after the breach was to shre it with other #CompSocSci ppl.

However, I started having second thoughts, so what follows is to organize ideas and have it somewhere I can look back to.

2/n

Generally speaking, as far as the ethics of research goes a good advice would be to handle hacked data with caution.

First of all, there's an issue of quality. Data might be altered or incomplete, and the source cannot be considered accountable (assuming src is anonymous).

3/n

Secondly and more importantly, a researcher using the data would probably be violating users’ consent and acting against the data collector's will.

Finally, users’ privacy is at stake, since researchers could see material that users didn’t agree for other people to see.

4/n

Sharing private information without consent might put people at risk of harm.

This is all the more true in cases such as the #ParlerHack, where the leaked information is of particularly sensitive nature, and there’s a high risk of unintended consequences.

5/n

Paul Bannister
@pbannist

This interview from @OSchiffey has great quotes that directly refute the nonsense that many privacy advocates spout about how the death of cross-site tracking will help ad-supported publishers on the open web. https://t.co/bj1gWPKOei 1/

The interview is with a senior leader at a major global ad agency. Someone who actually knows what advertisers are talking about, where they are directing their spending, and what the future trends will be. Not a privacy advocate who knows nothing about the advertising market 2/

First, privacy advocates spread misinformation and bad research data that ITP hasn't hurt publisher revenue and/or hasn't affected advertiser spending. And yet here is an unequivocal answer as to the impact of ITP on advertiser spending. 3/

The agency exec also clearly shares the opinion that the end of 3PC will push money away from the open web, exactly what privacy advocates claim won't happen. 4/

She also talks about how context matters, but so does audience. Audience targeting is effectively dead without 3PC and non-Chrome browsers are doing nothing to change this. 5/

Claire Ryan
@aetherlev

Right, I did some reading and here’s what likely happened with Parler. Lots of crossed wires here.

First up: someone noticed that Parler uses sequential integers in the API endpoint to get content.

An API endpoint is just a URL with a value added onto the end that tells the system what you want to get back.

Using sequential integers means that a hacker can set up an automated script to start at 1 and count up, trying API calls over and over again, to get back content from Parler.

Parler apparently had no restrictions on this API endpoint, which frankly blows my mind as a web dev.

If you had a working URL, it just spat out whatever it had whether you were logged in or not.

It seems that EVERYTHING that had been uploaded - video, photos, text posts - was accessible whether it had been deleted or restricted in the app itself. Even uploaded photos of licenses etc etc.

I cannot describe how amateur hour this is, if true.

You May Also Like

Anu Satheesh
@AnuSatheesh5

Beautiful story of Shri Krishna, Mata Rukmini & Satyabhama which teaches the importance of Bhakthi.
Devotion is important than anything.
#bhakthi
🕉
Satyabhama, royal princess was very proud of herself. Rukmini was very humble, her devotion was pure to Shri Krishna.

One day, Rishi Narada( Kalahapriya) arrived in Dwaraka and met Sathyabhama. In between the conversation he hinted that Krishna exhibits affection more to Rukmini than her. Worried Sathyabhama asked what can should be done to gain Krishna's undivided attention.
@SriramKannan77

Narada asked Satyabhama to make a vow, that she will hand over Krishna to him as a slave, if she cannot trade wealth equivalent to Krishna's weight. Narada thus convinces Sathyabhama that Krishna will admire her for sacrificing all her wealth for him.

Sathyabhama was sure that she have enough wealth to balance Krishna.

She went to Krishna and told about her vow to Narada. Krishna patiently listened to her and accepted the challenge. Satyabhama arranged to bring large scales to weigh and brought all her precious jewels.

Krishna patiently sat on one plate of the Scales (tula). Sathyabhama started piling up the gold, jewels on the other plate. She kept adding more and more wealth, but the pan with Krishna did not even budge. Even after keeping all her jewels the scale did not move a little

Quinn Cummings
@quinncy

Gather round, Gentle Readers. It is time I tell the story of the worst decision I ever made in an office. Some of you have heard this. Some have not. Whatever you do in your office today, this week, the rest of this year, you can console yourself by recalling this tale.

A long time ago, I was a talent agent. I worked for a woman named Susan Smith, who had her own small boutique agency. She was known for three things:

1. She had fantastic taste in clients. If there is someone you admire, odds are good that at some point, she was their agent,

2. She could negotiate a deal like few who have ever trod the earth. Casting would give her all the money they had budgeted for that part, plus a little more, plus promising to get her dog Barnaby groomed. She was magnificent to watch.

3. She was insane.

I'm sure you're thinking, "Quinn, it's the entertainment industry, they are all insane." Yes, many are. So consider this; if you told someone you worked for Susan, people who worked for insane people would look and you and whisper, "I hear she's insane."

Advertisement

Nigeria Stories
@NigeriaStories

The Story of how Mary Slessor Stopped the killing of Twins but sadly died of Fever.

All you need to know

Retweet to educate someone

Killing new-born twins was common practice in the 19th century among the Ibibio people of Nigeria, but one Scotswoman went to great lengths to put an end to this.

Aberdeen-born Mary Slessor was one of the few missionaries in Africa who learnt the local language, adapted to the native customs and environment and gained the trust of the locals in order to make a truly positive impact.

Her father, a shoe-maker from Buchan, became incapacitated by alcoholism and Mary more or less became the breadwinner for the family.

From the age of 11, she worked as a ‘half-timer’ mill girl in the Baxter Brothers and Co Ltd, spending half the day at a school provided by the mill owners and the other half working for the company

Ramblings of a Sikh
@RamblingSingh

1/ Jassa Singh Ahluwalia & his role in the history of Shri Harmandir Sahib (A Thread)

2/ Jassa Singh was born in 1720/21 at a village called Ahlu in the Lahore District of Punjab.

3/ Jassa Singh was educated in Delhi, in Persian, Arabic & more, under the care & supervision of Mata Sundari Ji.

Mata Sundari Gurdwara in Delhi.

4/ In 1733, Jassa Singh's mama, Thag Singh (ਤਾਗ ਸਿੰਘ), requested Mata Sundari Ji's permission to take Jassa Singh back to Punjab.

5/ At first Mata Ji refused but eventually gave permission for Jassa Singh to go with his mama, giving Jassa Singh a blessing and weapons, informing him, it was now the right time to take up arms.

Simon DeDeo
@SimonDeDeo

This is a pretty valiant attempt to defend the "Feminist Glaciology" article, which says conventional wisdom is wrong, and this is a solid piece of scholarship. I'll beg to differ, because I think Jeffery, here, is confusing scholarship with "saying things that seem right".

Imagine for a moment the most obscurantist, jargon-filled, po-mo article the politically correct academy might produce. Pure SJW nonsense. Got it? Chances are you're imagining something like the infamous "Feminist Glaciology" article from a few years back.https://t.co/NRaWNREBvR pic.twitter.com/qtSFBYY80S
— Jeffrey Sachs (@JeffreyASachs) October 13, 2018

The article is, at heart, deeply weird, even essentialist. Here, for example, is the claim that proposing climate engineering is a "man" thing. Also a "man" thing: attempting to get distance from a topic, approaching it in a disinterested fashion.

Also a "man" thing—physical courage. (I guess, not quite: physical courage "co-constitutes" masculinist glaciology along with nationalism and colonialism.)

There's criticism of a New York Times article that talks about glaciology adventures, which makes a similar point.

At the heart of this chunk is the claim that glaciology excludes women because of a narrative of scientific objectivity and physical adventure. This is a strong claim! It's not enough to say, hey, sure, sounds good. Is it true?