BC TECH
Saved by @SteveeRogerr

Today we are releasing the public beta of the @stripe extension for @code, which brings Stripe inside your editor. Let me give you some background on why we built this extension, what it does, and where we are going with our developer tools.

https://t.co/FyyHVNQtWA

A thread 🧵

 By bringing Stripe inside code editors, we move Stripe-specific information inside the context where developers already are when they build. We believe this will reduce context switching, reduce friction, and make it faster to integrate, build, and test with Stripe.
We decided to start with VS Code, one of the most popular code editors, and build an extension that would bring in a range of common workflows through a new Stripe panel in the activity bar and a set of custom commands.

Let me walk you through the features:
🛠 Webhooks can be burdensome to work with, so we made it easy to forward webhooks events to your local box. You can trigger events to test - this is integrated with the VS Code debugger so you can easily set breakpoints and step through your code.
📑 Sometimes when you’re integrating events, it's hard to know what the payloads will look like. You can now see the most recent events, and we’ll fetch the full event payload as JSON if you click on it, so you can easily see the properties — all without leaving the editor! 🔥
🗝 Managing API keys can be challenging, and sometimes we forget to remove our hardcoded secrets, which can have dramatic consequences.

So we'll now analyze and lint your code and show you warnings if you leave a hardcoded API key behind by mistake. ✨
📡 Sometimes things go wrong and you need to access the most recent logs to debug things. To make it easier we are bringing you log-streaming directly inside the editor. Simply run the command and get the logs streamed to your editor.
👩‍💻 When integrating Stripe, sometimes you need to look up code examples in our documentation.

Code snippets brings code examples from our docs into the editor, so you have less code to write and everything in one place.
📚 API References are essential to learning about APIs, so we brought you integrated API ref links directly inside the editor. Hover over a method when using our SDKs, and VS Code will link to the method in our API ref.
🖥 Sometimes you need to access the Stripe Dashboard, so we added commands to quickly open the Dashboard's most commonly used sections. Bam!
We are just starting to scratch the surface of what it means to bring Stripe closer to your source code and inside your editor.

What would you like to see in your favorite developer tool? What would improve your developer experience with Stripe?

More from Tech

Tom MacWright
Tom MacWright
@tmcw
it's done.

a visual enigma machine simulator: https://t.co/eLE4Sb97HW
TECH
Laurie Voss
Laurie Voss
@seldo
The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.


I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.


npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.
TECH
Advertisement
foone
foone
@Foone
I got a Toshiba T1200, which has a bad screen, and a dead CMOS battery, and I thought the hard drive was broken too...


but I rebooted it and heard a KTHUNK and a really loud spin-up noise and holy shit, the hard drive works!


and it still has files on it. the newest date is January 1994.


It's a 21mb hard drive, with ~37k of bad sectors.

This fucker is never going to spin up again, so I better go find some serial cables and copy shit off now.


The backlight is fucked so I'm shining a flashlight on it.
without it, it looks like this.
TECH
Resist the Hologram - Stu Cvrk
Resist the Hologram - ...
@STUinSD
Thread – Dump the Legacy Media; Turn to These News Sources

A. We all need sources less tainted by the Big Tech/globalist narratives that are echoed repeatedly throughout the legacy media. My brother sent me a list of alternatives from the Noq report.
TECH
Colby Fayock
Colby Fayock
@colbyfayock
Next.js has taken the web dev world by storm

It’s the @reactjs framework devs rave about praising its power, flexibility, and dev experience

Don't feel like you're missing out!

Here's everything you need to know in 10 tweets

Let’s dive in 🧵


Next.js is a @reactjs framework from @vercel

It couples a great dev experience with an opinionated feature set to make it easy to spin up new performant, dynamic web apps

It's used by many high-profile teams like @hulu, @apple, @Nike, & more

https://t.co/whCdm5ytuk


@vercel @hulu @Apple @Nike The team at @vercel, formerly Zeit, originally and launched v1 of the framework on Oct 26, 2016 in the pursuit of universal JavaScript apps

Since then, the team & community has grown expotentially, including contributions from giants like @Google

https://t.co/xPPTOtHoKW


@vercel @hulu @Apple @Nike @Google In the #jamstack world, Next.js pulled a hefty 58.6% share of framework adoption in 2020

Compared to other popular @reactjs frameworks like Gatsby, which pulled in 12%

*The Next.js stats likely include some SSR, arguably not Jamstack

https://t.co/acNawfcM4z


@vercel @hulu @Apple @Nike @Google The easiest way to get started with a new Next.js app is with Create Next App

Simply run:

yarn create next-app

or

npx create-next-app

You can even start from a git-based template with the -e flag

yarn create next-app -e https://t.co/JMQ87gi1ue

https://t.co/rwKhp7zlys
TECH

You May Also Like

Justin Kan
Justin Kan
@justinkan
1/ Throughout my startup career, I’ve seen many founders have an aversion to sales. This is a mistake that can kill your startup.

2/ Sales is often viewed as either a saving grace or proof that the product isn’t good enough (because it should sell itself). Neither are ever true. Some common mistakes that result in...

3/ Mistake 1: Hire a sales rep before reaching product/market fit to get your initial batch of customers. This is a mistake because founders need to work through their MVP with early adopters to truly understand what it is they’re selling.

4/ Mistake 2: Reach product/market fit, need to scale, and rely entirely on self-serve. For enterprise products that require big commitments and internal shifts, almost no product is self-explanatory enough to sell itself.

5/ Mistake 3: Make a first sales hire who isn’t scrappy enough to help mold the sales process from scratch. Some salespeople are amazing at their jobs, but not cut out to establish the processes that others end up following. This skillset is what @rdedatta calls a “sales ninja”.
STARTUPS
Kate Julian
Kate Julian
@katejulian
1/ Something strange is happening with people’s sex lives. 20-somethings are having sex later and less frequently than previous generations. I spent several months digging into this for @theatlantic. https://t.co/5ehzmWY9wi


2/ This phenomenon—I’m calling it a Sex Recession—really surprised me. It seemed improbable in the age of Tinder, digital porn, and attitudes that are generally permissive and sex-positive.

3/ What’s happening isn’t exclusively American: Similar trends are being observed in other countries, including Japan, Australia, the U.K., Finland, and the Netherlands.


4/ One cause is obvious: Adults under 35 are less likely to be living with a partner than in recent decades, and more likely to be living with their parents—which, it’s safe to say, isn’t great for one’s sex life.

5/ But I also found other explanations, each with profound implications. The first, unsurprisingly, has to do with internet enticements. Netflix and other online entertainment may be substituting for sex.
SOCIETY
Advertisement
Billy Bostickson \U0001f3f4\U0001f441&\U0001f441 \U0001f193
Billy Bostickson 🏴👁&👁 ...
@BillyBostickson
1. Project 1742 (EcoHealth/DTRA)
Risks of bat-borne zoonotic diseases in Western Asia

Duration: 24/10/2018-23 /10/2019

Funding: $71,500
@dgaytandzhieva
https://t.co/680CdD8uug


2. Bat Virus Database
Access to the database is limited only to those scientists participating in our ‘Bats and Coronaviruses’ project
Our intention is to eventually open up this database to the larger scientific community
https://t.co/mPn7b9HM48


3. EcoHealth Alliance & DTRA Asking for Trouble
One Health research project focused on characterizing bat diversity, bat coronavirus diversity and the risk of bat-borne zoonotic disease emergence in the region.
https://t.co/u6aUeWBGEN


4. Phelps, Olival, Epstein, Karesh - EcoHealth/DTRA


5, Methods and Expected Outcomes
(Unexpected Outcome = New Coronavirus Pandemic)
ALL
Robin Berjon
Robin Berjon
@robinberjon
Recently, the @CNIL issued a decision regarding the GDPR compliance of an unknown French adtech company named "Vectaury". It may seem like small fry, but the decision has potential wide-ranging impacts for Google, the IAB framework, and today's adtech. It's thread time! 👇

It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details): https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha

I've read it so you needn't!

Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.

The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.

Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.
TECH
f1talks.pl
f1talks.pl
@f1talks
Oleg Karpov pisze, że gdyby Siergiej Sirotkin zdobył w pierwszej części sezonu więcej punktów od Strolla, to jego kontrakt z automatu zostałby przedłużony na kolejny sezon. Tak się nie stało i Williams ma możliwość szukania innych opcji i to właśnie robi. #F1pl

Czego w artykule brakuje, to informacji, że SMP prawdopodobnie przekazało Williamsowi część środków na sfinansowanie sezonu 2019. W przypadku zakończenia współpracy ekipa z Grove będzie musiała zwrócić te środki. #F1pl

To tłumaczy wysokie kwoty jakich Williams ma oczekiwać za fotel od nowego kierowcy. Jest pewnie próg opłacalności i dopóki nie zostanie osiągnięty, to zmiana z finansowego punktu widzenia nie będzie się zwyczajnie opłacała. #F1pl

Tyle można znaleźć w oświadczeniach prasowych... 😂😂😂
SPORT