bjacobso

The tagged-union / function-call point is where I keep ending up too. Once a config needs “one of these shapes” or “this thing with these arguments”, data formats grow conventions on top (type: keys, YAML !tags, $ref), and every consumer reimplements them.

I’ve been building Forma (https://forma-lang.com), a small typed Lisp aimed at that zone. Everything is (head args...), so a tagged value and a call are the same syntax, and you declare the vocabulary yourself:

  (job nightly-export
    :schedule "0 3 * * *"
    :retry (backoff :max 5))

job and backoff are forms you define with typed holes. The checker reports errors at the line you wrote, even after macro expansion. The output is plain JSON (or generated Effect TypeScript, but could target any language), so the app reading it doesn’t embed the language.

Try https://www.conductor.build/

Claude Code et al. asks clarifying questions in plan mode before implementing. This will eventually extend to jira comments

Seems like the best competitor to Conductor at the moment. They did a great job.

Sounds good

Take a look at https://conductor.build/ - they really pioneered this whole direction of using git worktrees. Cursor will soon look like their app, Opencode will soon look like their app, etc.

I migrated from ts-rest to Effect/HttpApi. It's an incredible ecosystem, and Effect/Schema has over taken my domain layer. Definitely a learning curve though.

I believe Effect Schema fully supports Standard Schema, the issue is that it supports much more than Standard Schema, so not all schemas will work and thus provide compile time errors.

I think the main issue is they accidentally created an incredible consumer brand with ChatGPT. They should sell that asset to World.

You should check out https://effect.website/

It might help you implement some of these ideas

I agree, some of there examples are a little overly complicated by their quest to be hyper composable. In fact they should probably remove that example. I am currently using it with Remix, and using their @effect/platform package to produce a simple web handler (request: Request) => Response (thank remix for heavily promoting the adoption of web standards).

I fully agree parts of the ecosystem are complex, and likely not fully ready for broad adoption. But I do think things will simplify with time, patterns will emerge, and it will be seen as react-for-the-backend, the de facto first choice. effect + schema + platform + cluster will be an extremely compelling stack.

that is certainly a possibility

I've had a very similar experience, and have been slowly moving from zod and ts-rest to @effect/schema and @effect/platform/HttpApi as well as migration to Effect Match from ts-pattern. There is a learning curve but its a pretty incredible ecosystem once you are in it for a bit.

I think the real turning point was typescript 5.5 (May 2024). The creator of typescript personally fixed a bug that unlocked a more natural generator syntax for Effect, which I think unlocks mainstream adoption potential.

https://twitter.com/MichaelArnaldi/status/178506160889445172... https://github.com/microsoft/TypeScript/pull/58337

From my understanding trpc is very similar, however, the rpc mechanism is not a standard. ts-rest produces openapi schemas and speaks REST over http, as well as a typed client.

That being said, I am actually slowly migrating off ts-rest and adopting @effect/schema and @effect/platform/HttpApi, I foresee this being the direction the typescript ecosystem heads in over the next few years. However, the APIs are not stable yet and it has a bit of a learning curve, so would not adopt lightly

zod is great, but I have been moving to @effect/schema and think it deserves a mention here. @effect/schema is the evolution of io-ts, which originally inspired zod.

It supports decoding as well as encoding, and fits natively into the rest of the effect ecosystem.

https://effect.website/docs/guides/schema/introduction

It does come with the cost of importing effect, so might not be the best in certain scenarios. However, there are smaller options than zod if that is a concern.

I think you are looking for https://ts-rest.com/

I don't think the TikTok ban is an adjudication of the TikTok scrolling behavior or addictive feedback loop. It's an adjudication on the idea that a company that controls those technologies could be help accountable by the United States.

I think the current US stance is: we are allowing the crop dusting of american high schools with digital heroine, however, we demand the right to potentially regulate it in the future. A Chinese owned TikTok sits outside that potential regulation where a Facebook or YouTube exists within that potential regulation.

China themselves ban TikTok for kids, and only have an educational version available.

I just started playing with inertia and am pretty impressed. Was able to get it integrated with a rails project (which was already setup with vitejs) pretty easily. Then I can have templates like this: `app/views/welcome/index.ts` and its json is generated by `app/views/welcome/index.json.jbuilder`. Basically vanilla rails but the rendering is done as a react component.

Why would YouTube risk the optics of manipulating likes for a few percentage points, sometimes, in Biden's favor?

Is it possible there are other explanations?

I agree, this feels like the direction the framework should go in the future

I'd also like to +1 on Cadence/Temporal. It's a really great mental model and framework for thinking about workflows.

This is more of a proof of concept but it can also support DSLs (although we found the go client is easier to understand than DSLs): https://github.com/checkr/states-language-cadence

Checkr (YC S14) | San Francisco, CA and Denver, CO | ONSITE | Senior Engineers

I'm Ben, an engineering manager @ Checkr. We are an API for background checks- it may sound boring at first but there are interesting problems to solve and we've seen lots of success in the market.

A little about our stack: Ruby/Sinatra/Rails, MySQL and Mongo, Kafka, React and Angular frontends, Golang and Python microservices, Kubernetes and Docker for deploying, Presto for our data warehouse, moving to gRPC for internal service communication.

If any of that sounds like fun, drop me an email: [email protected]

For the curious: https://engineering.checkr.com/building-software-to-manage-t...

gRPC talk at RailsConf: https://www.youtube.com/watch?v=CtYNKOOZgsA

Checkr (YC S14) | San Francisco, CA | ONSITE | Senior Engineers

I'm Ben, an engineering manager @ Checkr. We are an API for background checks- it may sound boring at first but there are interesting problems to solve and we've seen lots of success in the market. We are hiring for all sorts of engineering roles, and are working on expanding the product beyond APIs to target traditional enterprises and innovate in a space that sorely needs innovation.

A little about our stack: Ruby/Sinatra/Rails, MySQL and Mongo, RabbitMQ and Kafka for queueing, React and Angular frontends, growing Golang and Python microservices, Kubernetes and Docker for deploying, Presto for our data warehouse, moving to gRPC for service communication.

Come help us redefine background checks!

We are looking for: Backend, Frontend, Fullstack, DevOps, Data/ML, BI, Security, Designers, PMs, Program Managers

If any of that sounds like fun drop me an email if you want to learn more: [email protected]

A little about me/checkr: https://www.youtube.com/watch?v=ynYHG0P494o

Checkr (YC S14) | San Francisco, CA | ONSITE | Senior Engineers

I'm Ben, an engineering manager @ Checkr. We are an API for background checks- it may sound boring at first but there are interesting problems to solve and we've seen lots of success in the market. We are hiring for all sorts of engineering roles, and are working on expanding the product beyond APIs to target traditional enterprises and innovate in a space that sorely needs innovation.

A little about our stack: Ruby/Sinatra/Rails, MySQL and Mongo, RabbitMQ and Kafka for queueing, React and Angular frontends, growing Golang and Python microservices, Kubernetes and Docker for deploying, Presto for our data warehouse, moving to gRPC for service communication.

Come help us redefine background checks!

We are looking for: Backend, Frontend, Fullstack, DevOps, Data/ML, BI, Security, Designers, PMs, Program Managers

If any of that sounds like fun drop me an email if you want to learn more: [email protected]

A little about me/checkr: https://www.youtube.com/watch?v=ynYHG0P494o

Checkr (YC S14) | San Francisco, CA | ONSITE | Senior Software Engineers

I'm Ben, an engineering manager @ Checkr. We are an API for background checks- it may sound boring at first but there are interesting problems to solve and we've seen lots of success in the market. We are hiring for all sorts of engineering roles, and are working on expanding the product beyond APIs to target traditional enterprises and innovate in a space that sorely needs innovation.

A little about our stack: Ruby/Sinatra/Rails, MySQL and Mongo, RabbitMQ and Kafka for queueing, React and Angular frontends, growing Golang and Python microservices, Kubernetes and Docker for deploying, Presto for our data warehouse, moving to gRPC for service communication.

Come help us redefine background checks!

We are looking for: - Engineers: Backend, Frontend, Fullstack, DevOps, Data/ML, BI, Security - Product: Designers, PMs, Program Managers

If any of that sounds like fun drop me an email if you want to learn more: [email protected]

A little about me/checkr: https://www.youtube.com/watch?v=ynYHG0P494o

Checkr (YC S14) | San Francisco, CA | ONSITE | Senior Software Engineers

I'm Ben, an engineering manager @ Checkr. We are an API for background checks- it may sound boring at first but there are interesting problems to solve and we've seen lots of success in the market. We are hiring for all sorts of engineering roles, and are working on expanding the product beyond APIs to target traditional enterprises and innovate in a space that sorely needs innovation.

A little about our stack: Ruby/Sinatra/Rails, MySQL and Mongo, RabbitMQ and Kafka for queueing, React and Angular frontends, growing Golang and Python microservices, Kubernetes and Docker for deploying, Presto for our data warehouse, moving to gRPC for service communication.

Come help us redefine background checks!

If any (or all) of that sounds like fun drop me an email if you want to learn more: [email protected]

Checkr (YC S14) | San Francisco, CA | ONSITE | Senior Software Engineers

I'm Ben, an engineering manager @ Checkr. We are an API for background checks- it may sound boring at first but there are interesting problems to solve and we've seen lots of success in the market. We are hiring for all sorts of engineering roles, and are working on expanding the product beyond APIs to target traditional enterprises and innovate in a space that sorely needs innovation.

A little about our stack: Ruby/Sinatra/Rails, MySQL and Mongo, RabbitMQ and Kafka for queueing, React and Angular frontends, growing Golang and Python microservices, Kubernetes and Docker for deploying, Presto for our data warehouse

Come help us redefine background checks!

Drop me an email if you want to learn more: [email protected]

Checkr (YC S14) | San Francisco, CA | ONSITE | Senior Software Engineers

I'm Ben, an engineering manager @ Checkr. We are an API for background checks- it may sound boring at first but there are interesting problems to solve and we've seen lots of success in the market. We are hiring for all sorts of engineering roles, and are working on expanding the product beyond APIs to target traditional enterprises and innovate in a space that sorely needs innovation.

A little about our stack: Ruby/Sinatra/Rails, MySQL and Mongo, RabbitMQ and Kafka for queueing, React and Angular frontends, growing Golang and Python microservices, Kubernetes and Docker for deploying, Presto for our data warehouse

Come help us redefine background checks!

Drop me an email if you want to learn more: [email protected]