If you identify with that problem,
and you want to solve it,
and you are open to advice...
Go to church, and be intentional to connect. Find a bible study, fellowship group, volunteer opportunity, or prayer meeting. Sit at church on Sunday with somebody from the bible study. Get lunch with one of those people. Find somebody at church who shares a hobby. Do your hobby together.
You have to put in the effort.
Growth is uncomfortable.
Real connection takes time.
Maybe you find something similar in other spaces, but I am certain you can find it in church.
Non-technical people have suggested using other tools like n8n or make.
Being able to write tests, use version control, and make full use of a programming language I am proficient with are perks.
It is also enshittification resistant unlike other platforms. I still might use them for something lightweight.
I have rolled my own solutions in previous roles and it worked well for very simple tasks (analyze this output and make sure it meets this criteria or try again...) I would be concerned about complexity if there were more steps, tool calls, or the need to compose multiple agents out of the same nodes, tools, state, etc...
Curious to hear more what you mean about compacting histories? Langgraph state management is simple enough and a custom reducer function gives you full control of context management...
Go to church, and be intentional to connect. Find a bible study, fellowship group, volunteer opportunity, or prayer meeting. Sit at church on Sunday with somebody from the bible study. Get lunch with one of those people. Find somebody at church who shares a hobby. Do your hobby together.
You have to put in the effort. Growth is uncomfortable. Real connection takes time.
Maybe you find something similar in other spaces, but I am certain you can find it in church.
reply