Working through 100 compile-time errors vs. 100 runtime errors is 100x faster

The data ecosystem around Python is strong, but the difference is much less stark and I find myself reaching for other languages like golang or rust 🦀

Hi 👋 -- Founding engineer @ 2 startups and now working on my own with @clint.social. Looking to connect with the community, and would appreciate the add

Have been liking Codesnap a bunch though 👌

github.com/mistricky/co...

Any good swe is eager to learn and that can take them to all different parts of the stack

This doesn’t feel that uncommon to me.

Shrink your problem space to as small as possible and test 2-3 options.

Pick something, move on, and don't get caught in the paradox of choice.

- Is there momentum and a good community?
- Does your team have experience with it?
- What do peers think about the options?
- What is devx and performance like?

There's a high chance things will change.

Architect your systems to be vendor agnostic as much as possible.

CTO of Wilde here, we’re big users and fans. Just spoke on the data stack show about duckdb. Would appreciate the add!

datastackshow.com/podcast/data...