ryan

@AlejandroRomaan how about SoHo?

NYC friends - looking for a desk to work out for the next couple of months 😊 📍Ideal location: Union sq and above Appreciate any leads!

remember when summer Fridays were a thing?

Thrilled to announce the WorkOS NY office has decided on Isshin Sushi for lunch to celebrate our 3rd Claude Day! We do these once a month: 100+ of us team up to build the internal tools and workflows we’ve always wanted but never had uninterrupted time to ship, then present what we built at all hands tomo.

@bernhardsson @modal new yorkers absolutely know its a rebrand

Side thing but am I the only New Yorker who feels like Hudson Square is a made up neighborhood? I don’t think it existed a decade ago. Anyway, welcome to the hood! @modal is just a couple of blocks away

@aboodman lol, I think the antipattern is long transactions

Another year another user unhappily surprised by the default pg isolation level. `read committed` is a sin against engineering.

@rohitdotmittal the best founders aren't in it for the money

I knew multiple founders who shut down their startups in 2022, returned the money, and joined AI labs. They made more money in the next three years than they would have running a $1B startup for 7 years. Making the call to move on was the best financial decision of their careers. I keep meeting founders in the same position right now - raised rounds, didn't hit escape velocity, feeling stuck. They're cautious about even acknowledging it. Like saying it out loud will make it real, or cost them credibility with investors and their team. But the best founders get to the truth as fast as possible and commit to a decision. Because they decide fast, they try more things, find more opportunities, and land in better places. If you're running out of ideas and energy, and don't see a future, the best long-term decision is to find a home for the company. Too many founders spend years trying to revive something that isn't working, instead of building the next thing. Not everyone who moved on did as well as those 2022 founders. But it was still the right decision. They're all better off now.

@alexisintech sorry to hear this, its a knock. do something that always brings you joy

It is absolutely devastating to announce that after 3 very devoted years, I have been abruptly let go from Clerk. Everyone knows how deeply I loved and championed for Clerk, and I am so absolutely devastated. I’ll be posting more about looking for a new role but this is all I can say right now.. I’m just in shock

I use AI to build things I'm not capable of coding myself - mobile apps, agent runtimes, identity brokerages. this makes me pretty biased in the "do you review code?" debate, but is directionally aligned with PHDs in a datacenter

@mattpocockuk I am now the student again

The "should you read code" debate is dumb because the real decision isn't binary, it's a scale: 1. Reading every line of every diff 2. Scanning every diff, reviewing important lines 3. Ignoring diffs but understanding the 'why' of every PR 4. Spot checking PR's instead of reading every one 5. Ignoring PR's, but doing regular spot checks on the codebase 6. Ignoring the code, but spot checking agent traces to help improve the system 7. Ignoring both the code and the system, let models handle everything Where are you on the scale?

@KentonVarda wait why don't you want super intelligence doing your work for you?

I just declared a moratorium against AI-written change descriptions (e.g. PR and commit messages, also issues/tickets) from my team. AI was writing change descriptions that were worse than useless to me as I tried to review PRs: outlining details of the code that could easily be seen by looking at the code, but omitting the higher-level framing needed to understand broadly what the code is doing. I think people like having AI write these things because the output looks structured and thorough, which makes it feel professional in a way. But this isn't actually valuable. Concise, high-level descriptions are better for everyone. If I need to use my own AI to interpret what your AI wrote then something is wrong. Let AI write code, sure, but for the description, I'd rather see your prompt than your output. We could maybe have extended agents.md with guidelines on writing descriptions, but this seemed a bit pointless since a good, concise change description only takes a few minutes to write -- not a significant time savings to delegate to AI. At least, it doesn't take long if you understand the code -- and if you don't understand the code, then I'm definitely not merging it.

@vadi_ms this is cool

This is me talking to my computer without making a sound. After just a month of collecting data, our model is already approaching dictation in accuracy. We were surprised to see that it generalizes to unseen participants as well! (1/n)

@palashshah laptops take up too much space

why aren’t there bars in nyc where pulling out your laptop is acceptable

@stevekrouse the last two weeks has turned me into a GLM 5.2 evangelist. it feels like a colleague

GLM 5.2 just did the cutest thing It started building an app an awkward way So I started typing out a correction to it Before I finished writing, it REALIZED ITSELF the downsides of it's approach, and pivoted to the way I would've suggested Neat to see how intelligence emerges from coming up with an idea, and then reacting to your own idea

@martyrdison kids are like startups, its always the right time

what people don’t understand about the birth rate decline is that men will often hold back on having children, it’s not just women i’ve been told countless times by men i’ve dated that it’s “not time” (they are in their mid 30s, or early 40s), that the financials aren’t right, or we need to do x, y, z before ‘that’ happens do not blame this all on women. men also do not want to have children

@tunguz it's wild when you start to grasp the knock-on effects of moving to a new level of abstraction, away from code to super intelligence. too many people are still debating whether humans should review PRs

You guys still don't get it: before this year is over, the best software will be made by AI *FOR* the AI.

would only change weeks -> years

@zeeg isn't this poolside?

Why is no one investing in coding focused models? Do people really believe the answer is general purpose training?

I don't exclusively go to conferences to keep up with the latest swag tech, but this is magnetic putty

Few people have shaped the trajectory of AI more than @drfeifei, from foundational research to building at the frontier with @theworldlabs. On July 22, @dwarkesh_sp will host an off-the-record conversation on what's next. Space is limited. RSVP below👇

@shcallaway soft of, but most fall outside platform. the "test" step is closer to UAT than integration testing, and "deploy" doesn't mean prod

Thinking about software factories this morning. A lot of the things that might be considered part of the "factory" could also be considered part of the "platform". Examples: - CI/CD system - Cloud infra - Developer tooling Even "loops" seem to fall under platform. Isn't design -> build -> test -> deploy -> iterate the ultimate loop? This is what we call the "software development lifecycle" and enabling it has been the core responsibility of platform engineers for many years now. Is Factory Engineering just a rebrand of Platform Engineering?