This is more accurate, I've written enough code in my life to never really want to do it again ....but I still love creating (code was merely the way to do it) so LLMs help with my underlying passion.
I don't find the same, like you, principle/CTO engineer, there's a world of difference between simplistic prompt/vibe coding and building a properly architected/performant/maintainable system with agentic coding.
That's great and I'm the same, 40s multiple founder and I was ready to hang it up after my last exit -- had 0 passion to code anymore and now I'm back and LLMs are reigniting my passion to create again.
Same, I have a bunch of skills defined ith proper YAML headers and semantic triggers installed, I make a point of listing not too many but making it quite specific.
Even with that, I have to be very specific in triggering a skill and it's hit or miss if it picks up on the skill -- usually I have to say there is a skill with this go and use it.
That's really interesting, I love the idea of being able to use columnar support directly within postgresql.
I was thinking of using Citus for this, but possibly using duckdb is a better way to do. Citus comes with a lot more out of the box but duckdb could be a good stepping stone.
Its a really handy tool. I've queried basically everything you can w/ duckdb - csv, json, s3 buckets, MS SQL servers, excel sheets, pandas dataframes, etc - and have had very few issues.
reply