forstmeier's comments

forstmeier | 3 years ago | on: Unhinged Engineering

For manual testing, QA is a separate person/team but I'm recommending the developer observe in real time as they review since they're "shuttling" the change into production. QA should also basically be adding in automated tests for their manual evaluations so yes, I'd have them cycle through the development team.

On #6, yes, I'd say squash merge into single commits so single commits going out would be the enforcement measure. And deploys to production occur immediately on merge to `master` which would be blocked on tests passing with additional pushes to that branch triggering test reruns.

forstmeier | 4 years ago | on: Show HN: AskPaulGraham

Yeah lol he's not going to be 100% perfect. There are definitely improvements that could be made in the request parameters being sent to the OpenAI API but I think the actual training data being uploaded and referenced as part of the response could be improve I'm just not sure how. Open to ideas!

forstmeier | 4 years ago | on: Show HN: AskPaulGraham

That would be pretty interesting. I wonder if there would be a way to smoothly integrate that with OpenAI's API.

forstmeier | 4 years ago | on: Show HN: AskPaulGraham

Improving the requests being made against the OpenAI API is probably the biggest thing I'd be looking for right now. I am also considering switching over to their "search" API instead of the "Q&A" one currently available on the "questions" tab.

Thoughts on how it could be improved?

forstmeier | 4 years ago | on: Show HN: AskPaulGraham

Yeah, it may have been too many operations against the OpenAI API - if you try again now it looks like it's cleared up a bit.
page 1