"...move to Montana, become a ranch hand, eat only the potatoes you grow and the cattle you raise, and to only think about upstream conflicts when you stare, through squinted eyes across a sun-scorched creek bed, at two fighting coyotes."
Really enjoyed reading this as I’m right at the beginning of my own career wondering how to think about risk and potential. Would you be willing to talk? hjconstas@docforge.net
I emailed you this too but my email's been acting up and in case there's others, this helps it's a good thing to share: Your piece really stuck with me. Especially that tension between chasing potential and settling into permanence.
For context, I’m working on a documentation copilot for developers. It syncs docs with codebase changes, makes docs for new features, and abstracts details for managers as needed. It’s all I think about. I work a day job, but all I think about is what I’ll do for it that night.
Lately I’ve been torn about what comes next. Part of me wants to just pack up and go to SF, dive into the chaos, and see if I can make it work. The other part worries it’s too early, I'll screw up and lose momentum or run out of money.
I’d love to ask for your thoughts on timing and risk given my situation. Knowing when to leap versus when to keep building and hoping it builds traction.
Do Oracle users at least get to open a window while they wait for their queries to finish? Or is the glare from "transforming workflows and business processes to speed their success" making it too difficult to see?
This made my day:
"...move to Montana, become a ranch hand, eat only the potatoes you grow and the cattle you raise, and to only think about upstream conflicts when you stare, through squinted eyes across a sun-scorched creek bed, at two fighting coyotes."
would love your thoughts on some of my stuff. follow me back, I could DM you?
The DM stuff on Substack is kinda wonky to me, but there's some contact info here if you want to reach out! https://benn.substack.com/about
Really enjoyed reading this as I’m right at the beginning of my own career wondering how to think about risk and potential. Would you be willing to talk? hjconstas@docforge.net
Word, glad you liked it. And if you've got questions or thoughts, feel free to email me here: https://benn.substack.com/about
I emailed you this too but my email's been acting up and in case there's others, this helps it's a good thing to share: Your piece really stuck with me. Especially that tension between chasing potential and settling into permanence.
For context, I’m working on a documentation copilot for developers. It syncs docs with codebase changes, makes docs for new features, and abstracts details for managers as needed. It’s all I think about. I work a day job, but all I think about is what I’ll do for it that night.
Lately I’ve been torn about what comes next. Part of me wants to just pack up and go to SF, dive into the chaos, and see if I can make it work. The other part worries it’s too early, I'll screw up and lose momentum or run out of money.
I’d love to ask for your thoughts on timing and risk given my situation. Knowing when to leap versus when to keep building and hoping it builds traction.
Do Oracle users at least get to open a window while they wait for their queries to finish? Or is the glare from "transforming workflows and business processes to speed their success" making it too difficult to see?
I hope so, because I bet the the view from a pj is pretty good