> we end up with a mix of both Zod and types and sometimes types that need to be converted to Zod

In my code, everything is a Zod schema and we infer interfaces or types from the schemas. Is there a place where this breaks down?

Not that I know of aside from code comments (which I like), but I much prefer writing TypeScript to Zod

> it expects a level of correct-design-up-front which isn't realistic for most teams

It requires a business that is willing to pay the maintenance cost of event sourcing in order to get capabilities needed capabilities (like an audit trail or replayability).

Trove | Senior Engineer - Warehouse Management System | Remote (US) | $140k - $185k + Equity

Trove powers recommerce for Patagonia, On, Canada Goose and many other retailers. We're looking for a Senior Engineer to develop our Warehouse Management System that enables circular retail at scale.

Tech challenges: ReWMS, a custom WMS written in TypeScript, is optimized for condition grading pre-owned goods during receiving. ReWMS integrates with e-commerce platforms and 3PLs.

Requirements: Experience working with warehouse management systems.

Apply: https://job-boards.greenhouse.io/trove/jobs/8160561002

Trove | Senior Engineer - Warehouse Management System | Remote (US) | $140k - $185k + Equity

Trove powers recommerce for Patagonia, On, Canada Goose and many other retailers. We're looking for a Senior Engineer to develop our Warehouse Management System that enables circular retail at scale.

Tech challenges: ReWMS, a custom WMS written in TypeScript, is optimized for condition grading pre-owned goods during receiving. ReWMS integrates with e-commerce platforms and 3PLs.

Requirements: Strong experience with logistics/supply chain tech.

Bonus: WMS platform experience (Manhattan, HighJump), TypeScript.

Apply: https://job-boards.greenhouse.io/trove/jobs/8040316002

New Relic, Datadog, etc are selling their original offering but now with otel marketing.

I encourage the author to read the honeycomb blog and try to grok what makes otel different. If I had to sum it up in two points:

- wide rows with high cardinality

- sampling

Trove | Staff+ Engineer - Warehouse Management System | Remote (US) | $190-234K + Equity

Trove powers recommerce for Patagonia, REI, Canada Goose and many other retailers. We're looking for a Staff+ Engineer to architect our Warehouse Management System that enables circular retail at scale. Note: The JD says "Principal Engineer", but please apply if are qualified for any staff+ engineer position.

Tech challenges: ReWMS, a custom WMS written in TypeScript, is optimized for condition grading pre-owned goods during receiving. ReWMS integrates with e-commerce platforms and 3PLs.

Requirements: Strong experience with logistics/supply chain tech, database optimization, asynchronous processing. Bonus: WMS platform experience (Manhattan, HighJump), TypeScript.

Apply: [https://job-boards.greenhouse.io/trove/jobs/7987271002](https://job-boards.greenhouse.io/trove/jobs/7987271002)

Many do. In their GitHub repos right next to the code.

In what cases is your join causing a table lock?

That is a feature. Compose instead of extending.

Yes, there are bad places to work. There are also places that require detailed time tracking, do not allow any time to write tests, have very long hours, tons of on-call alerts, etc.

How long until it becomes the rule because of some arbitrary "productivity" metric? Sure, you may not be forced to use it, but you'll be fire for being "unproductive".

That's the case at Shopify already: https://twitter.com/tobi/status/1909251946235437514