Mouad_Sidqi.ts

•software engineering and economics
•I hike sometimes 🏔️
• @1337FIL Alumni | TypeScript. 🇲🇦

[Mouad_Sidqi.ts @vmod__]

@ThePrimeagen wdym, AGI is already here

[Mouad_Sidqi.ts @vmod__]

Only in Morocco: ISP's support block competitor's customer numbers.

so if you have a Network problem, you have to also have their SIM card to resolve the issue

[Lee Robinson @leerob]

"Engineering, product, and design are all merging into a 'builder' role"

Yeah... I'm not so sure. This feels like an oversimplification and podcast talking point. Reality is a lot more complex.

Even with 1000 "Member of Technical Staff" titles, someone still has to wake up and care 100x more about Product or Design than anyone else. It is their Main Thing™

That's not to say MTS titles are universally bad, but I think they're an example of this 'builder' talking point that's become bastardized.

AI and coding agents have made generating code easy and yet... you're in for a world of pain if non-engineers ship a bunch of slop and don't have great engineers to tame the complexity.

The SF hivemind has a tendency to overfit what works at startups for every company. And to be fair, sometimes this is true! Startups can be a leading indicator for how the industry is changing and often cause disruption.

However, it is going to be incredibly hard to disrupt the extremely human parts of corporate jobs. You really think there's going to be a PM who also does some engineering and design on the side at JPMorgan Chase?

This is true for the simple parts of most jobs, like people wanting to have ownership over something and do good work, move up a career ladder, support their family, get paid well, make an honest living...

And also the hard parts: internal politics, some critical business system that has a bus factor of 1 which has been running for 15 years and isn't documented anywhere because it's that guy's job security. The real world has a lot of this stuff.

It's easy to pontificate about all roles collapsing but it's actually really nice to have a specific person or team who is an expert in one thing that you can work with. I don't expect that to change. Further, I think AI disruption to knowledge work will take decades to play out because it is more fundamental to the human condition (e.g. sociological/organizational) than pure intelligence.

[Mouad_Sidqi.ts @vmod__]

Are we reinventing phones now?

[Chubby♨️ @kimmonismus]

This came as a surprise: Microsoft has unveiled handheld and desktop devices designed to control one's agents.

It reminds me of what I had expected from OpenAI’s hardware-standalone devices for controlling agents.

[Mouad_Sidqi.ts @vmod__]

@bernoussama why do you use both on the same machine ?

[Mouad_Sidqi.ts @vmod__]

@soub4i I was hoping it was a fake AI image

[Mouad_Sidqi.ts @vmod__]

@mattpocockuk postinstall was and still is a big risk to allow

[Low Level @LowLevelTweets]

what the fuck is this company doing bro

[chan @chantastic]

fuck logitech

[Paul Kuruvilla @RohitPaulK]

@BullTheoryio

[Karri Saarinen @karrisaarinen]

The fallacy of this is that more creates more. More hours, more hiring, more something.

And it is true in a sense. If you put in more work, more work will happen. But I think for most startups, the leverage is really in how differently you approach the problem, how well you cultivate your team, and the strategy.

Any large company can outspend you on hours. They have thousands or tens of thousands more people, spending more hours. If hours worked were the metric, every large company and government organization would always win and do the best work. More hours, better output.

This thinking is often representative of younger founders, where the startup becomes their identity and life. They have a hard time doing anything else, and cannot understand that your work is not the person that is you. But activities outside of work can grow you as a person too and make you do better work.

I’ve never worked this way. As a designer, I always saw the need to take a step back, to take a break. At times, I might work 12 hours or 16 hours, or whatever amount was needed, but it wasn’t the norm. You just can't grind design, you need inspiration. But taking that step away from the work, would give me more perspective, inspiration and I could approach the problem differently or I could just see the solution.

Grinding is never good for any creative problem, and startups or creating new products are often mostly about creative problem solving. Grinding works ok for email jobs, or where you just executing on very clear playbook.

With Linear, we’ve never worked this way. We work reasonable hours, 5 days a week. All of us founders have families. Many of our employees have families. I personally stop every evening, spend time with the family, cook dinner for the family, eat dinner together, and focus on things outside of work. Sometimes I work in the late evenings or weekends, but to me the pride is that I don’t need to. Company should be succesful without it.

My goal is to build a company that is sustainable in the long term, and doesn’t require heroics or personal sacrifices every single day.

There are times when our team is heroic. Launches, incidents, some other work that just needs to be done. They will work late into the night because they know it is the right thing. But we don’t require that every day or every week, and the more this happens, the more I think it is a failure of our company and leadership. The team and the leaders should always keep a reserve to use when something is needed.

Our thinking was also that quality, which we value, doesn’t emerge from working more or stressing people more. It emerges when you create the conditions for it to emerge. Often it is the appreciation, space, time, and how the person feels. A person who is rested will do better work.

I wouldn’t attribute much of our success to working a lot. The success came from having clear thinking, ideas, and focus to do the right things.

I sometimes wish we could move the culture more toward a Zen master.

Real mastery is not exerting the most effort. It is achieving the outcome with the least necessary effort.

[Manu Arora @mannupaaji]

you can create a sticky navbar that morphs when you scroll with pure CSS, no JS or animation libraries required

𝚑𝚎𝚊𝚍𝚎𝚛 {
𝚌𝚘𝚗𝚝𝚊𝚒𝚗𝚎𝚛-𝚝𝚢𝚙𝚎: 𝚜𝚌𝚛𝚘𝚕𝚕-𝚜𝚝𝚊𝚝𝚎;
𝚙𝚘𝚜𝚒𝚝𝚒𝚘𝚗: 𝚜𝚝𝚒𝚌𝚔𝚢;
𝚝𝚘𝚙: 𝟶;
}
@𝚌𝚘𝚗𝚝𝚊𝚒𝚗𝚎𝚛 𝚜𝚌𝚛𝚘𝚕𝚕-𝚜𝚝𝚊𝚝𝚎(𝚜𝚝𝚞𝚌𝚔: 𝚝𝚘𝚙) {
.𝚗𝚊𝚟-𝚋𝚊𝚛 {
𝚖𝚊𝚡-𝚠𝚒𝚍𝚝𝚑: 𝟻𝟼𝚛𝚎𝚖;
𝚋𝚘𝚛𝚍𝚎𝚛-𝚛𝚊𝚍𝚒𝚞𝚜: 𝟶.𝟽𝟻𝚛𝚎𝚖;
𝚋𝚊𝚌𝚔𝚐𝚛𝚘𝚞𝚗𝚍: 𝚛𝚐𝚋(𝟸𝟻𝟻 𝟸𝟻𝟻 𝟸𝟻𝟻 / 𝟶.𝟿𝟸);
}
}

the browser now knows when a sticky element is stuck, all triggered by one container query

available only in chromium browsers only, no firefox or safari which is a shame

[Jared Friedman @snowmaker]

One night I quietly gave our AI agent full access to YC's production database. It made the agent 10x more useful. That's what convinced me that trust-by-default is the only way to get the most out of agents.

[Expo @expo]

Expo UI now runs callbacks on the UI thread.

SDK 56 ships first-class worklet integration for @expo/ui. SwiftUI and Compose components update shared state synchronously, no hop to JS.

Flicker-free input masking, finally. A credit card field formats 𝟺𝟸𝟺𝟸𝟺𝟸𝟺𝟸𝟺𝟸𝟺𝟸𝟺𝟸𝟺𝟸 into 𝟺𝟸𝟺𝟸 𝟺𝟸𝟺𝟸 𝟺𝟸𝟺𝟸 𝟺𝟸𝟺𝟸 on the same frame the keystroke lands.

Full blog post below from @nishanbende ↓

[Mouad_Sidqi.ts @vmod__]

@el_rei_gabriel Obviously the latter

[Mouad_Sidqi.ts @vmod__]

The most real take I’ve seen on X

[Gabriel @el_rei_gabriel]

@ahitposter Most of the time microservices are a push from an engineer who basically wants to use all the “advanced” tooling to gain experience and put it on the CV.

[𝖊𝖛𝖆𝖉𝖊 @encrypted]

wait... you did what?!

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

🚀 Wow, this is finally happening!

npm plans to block postinstall scripts by default in a future release

In the near future (phased rollout), we will likely get a warning

[Mouad_Sidqi.ts @vmod__]

You’re absolutely right! Removing this option definitely nuked your home directory…

[𝖊𝖛𝖆𝖉𝖊 @encrypted]

wait... you did what?!

[Beto @betomoedano]

https://t.co/5Xb5PcH6Cp

[Evan Bacon 🥓 @Baconbrix]

In Expo SDK 56 you can drop-in replace 8 common UI packages with the single universal @expo/ui package.

Makes upgrading much easier in the future