李赛博 (seb)

3K posts

李赛博 (seb) banner
李赛博 (seb)

李赛博 (seb)

@khepin

Bug writer for @AnthropicAI. Pizzaiolo for friends and family.

San Francisco, CA Katılım Mayıs 2008
349 Takip Edilen484 Takipçiler
李赛博 (seb)
李赛博 (seb)@khepin·
In 2020 I spent a whole month fixing flaky tests on CI that were OK locally Now I can just yell "claude... there's flaky tests on CI!!! FIX'EM" and come back after 1 day to fixed tests???
English
2
1
2
70
Matt Stauffer
Matt Stauffer@mattstauffer·
Guess the cat is out of the bag! I've been writing PHP since the late 90's, and its growth as a language has paralleled mine as a developer. I'm happy and honored to be able to be a part of a group of people working to continue advancing the language so many of us depend on!
The PHP Foundation@ThePHPF

We are very happy to welcome Matt Stauffer as the newest Board member for The PHP Foundation! Matt brings decades of experience and we are grateful for his insight as we move forward. Welcome, Matt! 🤩 🐘 🚀 Read more: thephp.foundation/blog/2026/03/2… #php #thephpfoundation #phpc

English
71
32
638
24.4K
李赛博 (seb)
李赛博 (seb)@khepin·
@thorstenball I like how you pretend 20m would even be enough to figure out anything in Google cloud. Anything like that is 2h if I have to do it directly
English
0
0
2
15
Thorsten Ball
Thorsten Ball@thorstenball·
Agents Actually Don't Help lol, Episode 4213: - Client wouldn't connect to new service I'm working on - "huh? but works locally, something about prod?" - Hand 5 lines of log files to agent - Agent goes and, in 30 seconds, uses 6 gcloud CLI invocations to find the relevant logs - Says: "Docker image doesn't include this file, let me fix" - 1min later it's fixed Yes, could've done it myself. Yes, could've figured out the log commands. Yes, could've fixed myself. But we're talking about 1.5min vs. 20min because I would have had to look up gcloud invocation and figure out how to embed file directly with Vite. Not insurmountable, obviously, but just stuff that's truly valuable to know longer term.
English
7
1
70
10K
李赛博 (seb)
李赛博 (seb)@khepin·
@aarondfrancis Always configure my terminals with "text mode" so cmd + arrows go to begin / end of line and alt + arrows go to next / prev word. I've had that work well on iTerm and also in alacritty. But... yes, have to configure the terminal for it.
English
0
0
0
36
Aaron Francis
Aaron Francis@aarondfrancis·
Help me understand how you use hotkeys in terminals. Some people expect Cmd+Arrow to go to the start or end of a line, but Cmd is consumed by the terminal emulator, it never gets sent to the PTY. If it works, it’s because the terminal is remapping it What do you expect?
English
34
0
43
20K
李赛博 (seb)
李赛博 (seb)@khepin·
@mattstauffer Just gonna repeat others here. But no issues having them in 1password. Though for sites that do weird auth on multiple domains, that might be a source of issues.
English
0
0
1
236
Matt Stauffer
Matt Stauffer@mattstauffer·
Every single time I've tried to install a passkey--bar none--I've regretted it. Something goes wrong, whether in their system or in my memory (sure, I generated a passkey, but where is it? 🤷‍♀️), and I cannot ever make them work. Is it just me? Are y'all using passkeys?
English
26
0
13
10.6K
李赛博 (seb)
李赛博 (seb)@khepin·
@aarondfrancis Works great with tools that help you work in worktrees. Couldn't do it if i had to use the git commands from memory each time.
English
0
0
0
8
李赛博 (seb)
李赛博 (seb)@khepin·
@aarondfrancis So I'm not even using my main checkout anymore for anything other than creating a worktree on a branch. and to merge things back in when done.
English
1
0
0
14
Aaron Francis
Aaron Francis@aarondfrancis·
Why do people like git worktrees over discrete checkouts? (This isn't bait, it's research)
English
269
4
363
137.8K
李赛博 (seb)
李赛博 (seb)@khepin·
@aarondfrancis You should checkout the worktrunk CLI if you haven't yet. Makes working with worktrees much easier. Mine's setup with hooks that will start the server on a per worktree port, setup my terminal tabs / panels upon entering etc...
English
0
0
0
53
Cute Baby
Cute Baby@nachunja·
$XYZ Block • 6000 Employees • $10.4B Gross Profit $TOST Toast • 6500 Employees • $1.6B Gross Profit $SHOP Shopify • 7600 Employees • $5.6B Gross Profit If the Chosen 6000 can somehow accelerate growth, it'll be for the history books
English
9
2
75
7.5K
trash
trash@trashh_dev·
pov: you just got fired in a lowercase letters
English
16
15
735
30.5K
Taylor Otwell
Taylor Otwell@taylorotwell·
@youyuxi @theHankTaylor At Laracon India I did legit say the only S tier software I’ve used is Sublime Text and Vue.js 🤗
English
4
0
161
9.6K
Taylor Otwell
Taylor Otwell@taylorotwell·
Why is there always drama in slop stack lang 😂
English
15
3
192
34.9K
Chris Power
Chris Power@typecraft_dev·
Are you feeling nervous? Are you having fun? It’s almost over. It’s just begun
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
14
1
87
17.3K
李赛博 (seb)
李赛博 (seb)@khepin·
Yup. I'm out. It was a great wild and fun ride while it lasted
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
2
0
2
242
李赛博 (seb)
李赛博 (seb)@khepin·
Will github reach NO-NINES reliability this month?
English
0
0
1
82