@pedma7 Same general workflow here; but...it's the inevitable debugging session six weeks later that concerns me. One way I've mitigated is by ratcheting up the documentation. But still.
@lisperati 'tough' interviews done right by both parties become a win-win. And the audience, especially, wins. So a win-win-win?
I hope we get more of these.
@mark_l_watson Awesome; thanks for the background!
I'm not nearly as far along as you; need to start working with Ollama Cloud.
So far I've had a good experience working with gptel to access models available via opencode 'go'. Next step is using gptel with models via opencode zen.
@jasonfried Solid idea. I suspect this would turn into 'founders therapy' session with the interviewer playing role of mediator, therapist. Regardless, I'd listen!!
@orrdavid Spectacular! Does the service come by and water daily? Also, how particular are they about placement for light, hvac settings, etc?
Having bonsais myself (kept outdoors) I'm amazed at the variety you've enjoyed so far. And indoors!
@KeyPaganRush Any thoughts on the sheer volume of code produced and then the (necessary) follow-on debugging, pruning? I'm starting to see tooling to support this, but was curious how you are approaching it. Thanks!
@Gingfacekillah Such a key point! Tangential: "...be willing to do stuff that doesn't scale..."
Question: what percentage of your effort goes towards this tedious / hands-on work?