Umar Rasydan

This is great writing and what high-quality recruiting looks like today. Some notes on what I love... It's very easy to read and not trying to sound fancy. It uses basic words. You should write how you speak! It's humble, including some numbers, but not trying to overhype. There's a level of comfort in himself and his ideas you can feel. It makes you root for him and his background. You might even relate to some of the examples (I also learned video editing at a young age). People want to work with people they like. It uses humor without being over the top. This makes it feel written by a human and not some AI slop. "I don’t care if you are broke film student who works at Starbucks or an OpenAI researcher getting paid a milli by Papa Sam." Finally, one of my favorite parts is just cutting the normal resume / application crap and going straight to what you've built. "Do not send me your resume. If you wanna do design here, show me a design for Clicky. If you wanna be a filmmaker here, great, record a video for Clicky and show me." Nice work @FarzaTV!

Code is actually the right abstraction. Too often I see the future of software engineering diminished down to, effectively, writing and reviewing markdown files. Yes, it will be hard to review thousands of lines of agent code. But maybe the takeaway is that you want less code? Rather than just giving up ("well I guess we won't read the code, or we'll read this lossy markdown summary") this should be a signal forcing you to think about better systems. - How can we make our codebase more verifiable? For example, fast/robust/stable tests, or moving to a typed language. - How can we deslop or improve the architecture/abstractions of the code generated by agents? For example, spending more time up front on the codebase architecture/types before yolo generating all of the code. - How are we going to maintain and evolve this codebase over time? The slop compounds. One great solution here is... you guessed it, learning from the past decades of software engineering! For example, you might just have the wrong abstraction entirely, leading to a ton of duplicated code. I think the markdown folks *are* right in some ways. If you are using skills every day, for many different prompts and workflows, isn't that effectively "coding with markdown"? Kinda. There's been plenty of ink spilled on the merits and benefits of skills. To me, skills make your style of working legible for agents. They don't replace code and that's not really the point. In reality, there's this messy and constantly re-evolving future in which both of these things are true: 1. Skills (and markdown) are important for how you give input to the agents and ensure high-quality code & systems are created 2. Looking at the actual code will not be replaced by markdown summaries or a collection of spec documents that ignore the lower level details of the code In summary: reality has a surprising amount of detail (and nuance)!

Just gonna leave this here. chatgpt.com/codex/switch-t…

Coinbase confirms they deliberately had no multi-zone support for their global trading service: meaning they knew if the AZ went down it operated in, all trading would stop. So all trading stopped for 8 hours yesterday. They will now (finally?) look into multi-AZ Overdue, IMO

Coinbase’s CEO lays off a ton of employees and says: “Non-technical teams are now pushing code to production with AI” less than 24 hours later: coinbase’s trading engine goes down and somehow even the status page breaks too

@ivokun @srg_io still waiting on the link! haha

@UmarRasydan missing may 14th cc: @srg_io

Xendit KL is hosting a few community meetups this month, bringing together builders, engineers, and tech enthusiasts across cloud, databases, and systems programming. Upcoming events: Google Developer Group Cloud KL Meetup - May 6 MongoDB User Group KL Meetup - May 7 Rust Malaysia Meetup - May 13 If you’re in KL, come join us, meet the community, and learn alongside other builders. Details and links in the comments.

Google Developer Group Cloud KL Meetup - May 6 gdg.community.dev/events/details… MongoDB User Group KL Meetup - May 7 meetup.com/mongodb-usergr… Rust Malaysia Meetup - May 13 linkedin.com/posts/rust-mal…

We’re introducing the Cursor SDK so you can build agents with the same runtime, harness, and models that power Cursor. Run agents from CI/CD pipelines, create automations for end-to-end workflows, or embed agents directly inside your products.

1. Techtamu Minda Cerdas Baharu (April 18) → openkelas.bcl.my/event/kl01 2. The Builders' Stories (April 24) → luma.com/0fu82tob 3. Notion AI Unhakathon (April 28) → luma.com/jizs8xh9 4. Designers Who Build (April 30) → luma.com/uuow50fd

4 events for builders, designers & the AI-curious: • Apr 18 — Techtamu Minda Cerdas Baharu • Apr 24 — The Builders' Stories • Apr 28 — Notion AI Unhakathon • Apr 30 — Designers Who Build RSVP links below

Please do better @hannahyeoh

I wrote this early this morning and I wasn't sure if I would actually publish it, but here it is: blog.samaltman.com/2279512

I have waited years for someone to challenge this nonsense phrase on mainstream media. An indictment of the liberal PEP media that it took Tucker Carlson to do it. And he undeniably did it well.

Congrats to the @cursor_ai team on the launch of Composer 2! We are proud to see Kimi-k2.5 provide the foundation. Seeing our model integrated effectively through Cursor's continued pretraining & high-compute RL training is the open model ecosystem we love to support. Note: Cursor accesses Kimi-k2.5 via @FireworksAI_HQ ' hosted RL and inference platform as part of an authorized commercial partnership.

Islamophobia has gotten so out of control that even an annual *NYPD iftar* that goes back to the era of Bloomberg (who was no friend to Muslims) is being met with bigoted venom.

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

Software engineering changed more in the last 3 months than the preceeding 30 years. Everything about running a software company needs to be rethought from first principles.

If you heard: "Don't bother learning to code, AI will do it all." They're wrong. Here's why. adventures.nodeland.dev/archive/yes-le…

lol - into the graveyard collection again?