It's free for local use from npm.

Better PR descriptions explain why.

Could you go into more details about the errors you encountered along the way?

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?

See the previous comment and the Twitter screenshots, have a nice day.

https://twitter.com/nudpiedo/status/1599444651462733824?s=20...

Brings to mind Haus-Rucker-Co's (https://www.spatialagency.net/database/haus-rucker-co) Fly Head Helmet (https://www.spatialagency.net/2010/07/26/hausrucker_1-960x69..., https://www.spatialagency.net/2010/07/26/hausrucker_8-960x12...)

Having tuned in a few times to watch https://twitter.com/AdamLearnsLive on twitch, I was inspired to take notes throughout my development process. What I noticed of Adam13531's note taking was they wrote down every question that came to mind as they worked down the rabbithole of learning that is software development.

For my own practices, I've added in a bit of an OODA loop process. My intent is to systematically balance between deciding and executing, focusing on accumulating knowledge towards achieving a goal.

When I'm stuck, or dealing with unknowns, the brainstorming in each of Observe, Orient and Decide enable me to gain some flow.

Later, I can observe where I had blindspots, or anchored to certain contexts or scopes. I'm noticing I could develop checklists to go through to avoid repeating those biases.

The second brain is emerging out of this. I keep these notes as a sibling project to all the software projects I'm interacting with.

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

Is it to spare keystrokes in method definition, or rather, in method invocation?

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 :-)

Yeah, should be invocation, there's a nice example on the feature request (https://bugs.ruby-lang.org/issues/14579):

  def login(username: ENV["USER"], password:)
    p(username:, password:)
  end

  login(password: "xxx") #=> {:username=>"shugo", :password=>"xxx"}

I'll add to the voices here mentioning vulnerability. I believe it takes strength and courage to choose vulnerability.

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.

I guess some people just don't get quality onboarding content from compliance.

I checked your profile hoping maybe you had a quality onboarding compliance content startup. Maybe one day...

Aww thanks! The one thing that sticks after all those clicks: don't accept deal sweeteners outside of the papered contract!

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

…

I really connected with the writing. Thank you for taking that time.

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 am glad you liked it.