exactly this, verification should always been on the code

if someone fresh wants to contribute, now they will have to network before they can write code

honestly i don't see my self networking just so that i can push my code

I think there are valid ways to increase the outcome, like open source projects codifying the focus areas during each month, or verifying the PRs, or making PRs show proof of working etc,... many ways to deter folks who don't want to meaningfully contribute and simply ai generate and push the effort down the real contributors

Why are folks seemingly so averse to sending an email / hopping on a channel to actually talk to maintainers before just firing off code? I've been on both sides of this; I have been young and green and just fired off contributions without stopping to think, do they event want this?. Codebases are rarely built primarily out of zillions of shotgunned patches, they are more like a garden that needs tending over time, and the ones that are the best tenders are usually the ones that spend the most amount of time in the garden.

> honestly i don't see my self networking just so that i can push my code

But that's good outcome. You would rather spend time on projects where you agree with the project policies.

for the workflow DAG, what type of backend are you guys using? is it like temporal or self-built durable workflows

we built an execution engine ourselves https://github.com/simstudioai/sim/tree/main/apps/sim/execut... and for the infra for background jobs, we use https://trigger.dev/

Zenact AI | Founding Engineers & Interns | Full-Time + 6-Month Internships | Onsite Bangalore | Location flexible for internships (India) Tech: Golang • Python • AI Agents

At Zenact AI, we are building AI agents that test apps like real users. I personally faced this problem at Zomato for over 6 years while handling many bugs and incidents.

We launched recently and already got 35+ signups from leading unicorns & soonicorns in India.

Backed by the Zomato mafia.

Team comes with deep expertise from Zomato’s scale journey.

## Roles:

* Founding Engineers.

* Interns (6 months). Must’ve built serious projects or freelanced early in college.

## Tech Stack:

Golang, Python, Java(5%), Appium, AWS, Docker

## You’ll work on:

* Building the platform from the active feedback from the customers, with heavy focus on improving the end to end latency of testing.

* Fine-tuned vision & reasoning models (currently 92% accuracy vs SOTA ~60%)

* AI agents for mobile testing, reasoning flows.

Apply: shoot a mail to sri@zenact.ai or fill form here: https://forms.gle/yWproMowhA4ZF4gv6

first i thought the website would say how many elephants left in the world (like white rhinos)

It does now.

seems obvious in hindsight, but never knew CT scans are used in manufacturing QC

Zenact AI | Founding Engineers & Interns | Full-Time + 6-Month Internships | Onsite Bangalore | Location flexible for internships (India)

Tech: Golang • Python • AI Agents

At Zenact AI, we are building AI agents that test apps like real users. I personally faced this problem at Zomato for over 6 years while handling many bugs and incidents.

We launched recently and already got 35+ signups from leading unicorns & soonicorns in India.

Backed by the Zomato mafia.

Team comes with deep expertise from Zomato’s scale journey.

Roles:

Founding Engineers.

Interns (6 months). Must’ve built serious projects or freelanced early in college.

You’ll work on:

* Building the platform from the active feedback from the customers, with heavy focus on improving the end to end latency of testing.

* Fine-tuned vision & reasoning models (currently 92% accuracy vs SOTA ~60%)

* AI agents for mobile testing, reasoning flows.

Apply: shoot a mail to sri@zenact.ai or fill form here: https://forms.gle/yWproMowhA4ZF4gv6

one thing that is getting clear is that the gains from model enhancement is getting saturated

thats why we are starting to see a programming of ai, almost like programming building blocks

if there is a pathway for models to get smart enough to know when to trigger these hooks by themselves from system prompt or by default itself, then it wouldn't make sense to have these hooks

being on the developer side, the realtime dashboard for admin ui is really useful for end to end testing

so many of the eventually consistent stores reflect so late that its a pain to work with their SDKs

out of curiosity, what kind of metrics or observability do we get for events that got dropped due to some issue

credit balance api is pretty cool

always liked the v0 feature where they notify to top up when the balance runs low

when do apps invoke the credit balance api? before sending events or they poll asynchronously and keep a local cache about the credit balance?

i guess caching would be a bad pattern too as the app may not function immediately after the top up of credits

most of the current systems that need a reliable managed service for distributed locking use dynamodb, are there any scenarios where s3 is preferrable than dynamodb for implementing such distributed locking?

Using only s3 would be simpler, less setup, less code, also less expensive