bjacobso

27 ms·

1.
by bjacobso 8mo ago
https://www.youtube.com/watch?v=aueu9lm2ubo
2.
by bjacobso 8mo ago
Try https://www.conductor.build/
3.
by bjacobso 9mo ago
Claude Code et al. asks clarifying questions in plan mode before implementing. This will eventually extend to jira comments
4.
by bjacobso 10mo ago
Seems like the best competitor to Conductor at the moment. They did a great job.
5.
by bjacobso 11mo ago
Sounds good
6.
by bjacobso 11mo ago
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.
7.
by bjacobso 1y ago
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.
8.
by bjacobso 1y ago
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.
9.
by bjacobso 1y ago
I think the main issue is they accidentally created an incredible consumer brand with ChatGPT. They should sell that asset to World.
10.
by bjacobso 2y ago
You should check out https://effect.website/ It might help you implement some of these ideas
11.
by bjacobso 2y ago
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 pr
12.
by bjacobso 2y ago
that is certainly a possibility
13.
by bjacobso 2y ago
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
14.
by bjacobso 2y ago
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
15.
by bjacobso 2y ago
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 int
16.
by bjacobso 2y ago
I think you are looking for https://ts-rest.com/
17.
by bjacobso 2y ago
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
18.
by bjacobso 5y ago
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/inde
19.
by bjacobso 5y ago
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?
20.
by bjacobso 5y ago
I agree, this feels like the direction the framework should go in the future
21.
by bjacobso 6y ago
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
22.
by bjacobso 7y ago
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
23.
Building software to manage the complexities of background checks(engineering.checkr.com)
21 points by bjacobso 7y ago|0 comments
24.
by bjacobso 8y ago
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
25.
by bjacobso 8y ago
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
26.
by bjacobso 8y ago
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&#x2
27.
by bjacobso 8y ago
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&#x2
28.
by bjacobso 9y ago
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&#x2
29.
by bjacobso 9y ago
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&#x2
30.
by bjacobso 9y ago
Checkr | San Francisco, CA | ONSITE | 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 o

More ›