cpb

How can we cultivate more of this thinking in Rails, where is that watering hole?

I want to support some colleagues with automating some of the setup of routine video editing. Can't consider this impressive work without that clarity!

I tried having ChatGPT do TDD to vectorize n-ary trees, but it made mistakes that indicated it didn't understand it's output:

- the expected vectors in the tests were the format it suggested for binary trees

- when asked to represent a vector as a tree, produced one correct tree and another incorrect tree. (Correctness as determined by how it chose to encode a tree as a vector).

It took some iterations to get it to fix the tests, but I grew weary of coaching it through each of the problems as we encountered them. Maybe if I was at my keyboard rather than on my phone I could have had it complete the task quicker.

So, what errors did you encounter along the way? How did you overcome them?

When shooting my shotgun for finding more references, what I've done/know/questioned about a piece of code shows up too.

Your second definition reads that `with_longer_parameters` is a keyword argument with no default.

Still, you've illustrated the keystroke savings with your choice of parameter names :-)

I am starting to recognize that the courage is required because it can be a filter. It isn't just the chance that a "nurse or phlebotomist" might judge you harshly, there are many people in the world that'll sooner reject than connect with you.

Still, if we are to be true to ourselves, perhaps vulnerability can minimize the total amount of pain in our lives. It'll take weighting the acute pain of rejection as vulnerable as lesser than the chronic pain of acceptance with insecurity.

May we be so fortunate to choose.

Easy to say when no one's offering, I guess.

There is a lot in my current context the writing resonates with. Nice to find that others have been on this path too, and that we benefit from a lot of the same techniques.

Thanks for putting this out there as an invitation to draw people together.

I read it at a point in time for my startup when we had done as many Customer Discovery interviews as we could in our local market, and were trying to achieve a first sale or pilot project with customers in more innovative markets. The inquiry phase of solution selling connected with and reinforced the customer discovery process, but provided some indication of how to move forward, and cautions about moving forward too early with a proposal.

The key to sales is solving problems. You claim to have a product that addresses a large "potential" - what problem, and for who, does it solve? Can you measure the impact of the solution?

If you have a product that solves a problem, what is the least intrusive thing you can ask of a potential customer for you to identify if they perceive they have that problem, and if they recognize the impact of solving it?

If you cannot mutually identify the problem and impact of the solution, a prospect may only entertain your talkative nature to solve the problem of looking busy to their superiors.

Track the observable characteristics of your prospective customers that are the best indicators of if they have the problem you solve, or not.

Figure out how long it takes you to identify if they have the problem, or not.