najork

Super cool seeing you take an LSP-first approach here, decoupling the developer experience for people building with Marimo from any specific editor.

Unit tests to assert a spec are great, but they don't provide any context as to why the spec was defined as it was. This context is critical when making changes to the spec, so unit tests on their own aren't sufficient in my experience.

It's super cool how they generated the 3D model on the fly, I'd love to spend some time playing with the microscope they used in the video.

How've you found `uv` as a package manager? I've generally been a fan of Astral's tools in the Python ecosystem and I'm considering making the switch from `poetry`.

Agreed, and Apple's differentiator has always been seamless integration. With the iPhone, they own the boundary layer between the physical and digital worlds. It's an obvious place to introduce AI for daily tasks without requiring any behavioral changes from the users.

Curious, which contexts do you prefer chatbots in?

At the end of the day, there will always be people making sweeping generalizations counter-positioning themselves against the hype in order to drive engagement.

There are plenty of companies capitalizing on the AI hype cycle which won't manage to build durable businesses, but there are also plenty of use cases where AI is meaningfully accelerating people's workflows.

Situations where it's effort-intensive to create something from scratch but cheap to validate the output of a model and iterate on it until you're happy seem to be the sweet spot right now. Code co-pilots, generative artwork, copywriting, etc. Granted, these are all incremental improvements rather than fundamental evolutions to how we do work thus far, so that aspect seems overblown, but writing it all off as smoke and mirrors is disingenuous.

Kudos guys, I've been super impressed with your development velocity. Marimo is a pleasure to use.

Radiant | Full-time | Onsite (SF) | Software Engineer (Frontend)

Radiant is on a mission to accelerate AI adoption in the enterprise.

We're looking for frontend developers with a proven track record of successfully owning and executing against meaningful outcomes in an end-to-end manner. We’re seeking highly motivated individuals who are strong generalists and comfortable flexing beyond core engineering responsibilities into other domains as needed.

As an early member of the Radiant team, you’ll play a key role in defining and establishing foundational aspects of our company, including the product and culture.

We’re hiring individuals in SF. We believe that we do our best work with regular face-to-face interactions and encourage a hybrid schedule.

If this sounds interesting, we’d love to hear from you.

Reach us at { team at radiantai dot com }

Silicon Valley has been around for far longer than zero interest rate policies.

I agree with the author’s sentiment that product teams fail because of a lack of trust, but don’t think it’s necessarily ego-driven.

It’s challenging to build a company with a high-trust culture. While many companies say it’s one of their values, I’d bet it only holds true for a small minority of them in practice, especially when things aren’t going according to plan.

When an organization is failing to execute against its goals, regardless of the root cause, the natural tendency is to introduce more process and exert more top-down control. Ironically, this drives away the most capable, creative problem solvers, who’ll look elsewhere for fulfillment.