Vignesh Chandramohan

Vignesh Chandramohan

@vigneshc.bsky.social

Stream processing, data infra, Table formats. https://vigneshc.github.io/

1.2K followers87 following41 posts

1/ Nice read: medium.com/@xiafan/time... Software engineer growth in AI era: * Build composable tools. * Assume non deterministic outcomes from a group of ai agents. * Understand how LLM works to the next level, like how you would understand to read a query plan.

medium.comTime to Adapt and Become a Better EngineerA colleague recently asked if I think AI agents could do all the jobs humans do. My answer was an unequivocal yes. Given the same sensory…

Vignesh Chandramohan reposted

Insane amount of SlateDB work going on: - snapshot reads - split/merge DBs (zero copy) - deterministic simulation testing And someone just pushed Python bindings in a PR! 🤯

Vignesh Chandramohan reposted

SlateDB 0.5.0 is out! Features: - Checkpoints - Clones - Read only client - Split/merge database foundation - TTL filtering on reads - Last version with breaking byte format changes By the numbers: - 62 commits - 2 new contributors - 10 total contributors github.com/slatedb/slat...

github.comRelease v0.5.0 · slatedb/slatedbWhat's Changed Refactor Block Tests to Use Table-Driven Test Cases by @samsond in #410 Update await calls in README.md by @criccomini in #425 chore: Apply table driven test for sst.rs by @jeffreyl...

Vignesh Chandramohan reposted

Python Folks - which data/workflow engine has the best developer experience for packaging code? We have looked into - Modal, Beam, Airflow, Flyte, AWS Lambda, Prefect, Dagster and Spark. Haven’t seen any approach which is fast, reliable and intuitive.

Vignesh Chandramohan reposted

SlateDB 0.4.0 is out! Features: - Range scans - No DynamoDB needed for S3 - Nightly perf tests - Merge operator groundwork - GC improvements By the numbers: - 57 commits - 5 new contributors - 11 total contributors github.com/slatedb/slat...

Vignesh Chandramohan reposted

Vignesh Chandramohan reposted

The 3 reasons to backfill: 1) new pipeline, who dis? 2) logic changed, recompute 3) whoops downstream lost everything. resend it.

You are up to date.