Re:GitHub CLI allows you to close, reopen, and add metadata ...
by dmitshur on Tuesday May 12, 2020 @09:41PM
(#23162491)
If anyone is interested in learning more about the various trade-offs considered during its initial design, I gave a talk¹ about it in 2017, and wrote about some internal implementation details in a blog post².
Re:GitHub CLI allows you to close, reopen, and add metadata ...
by benhoyt on Tuesday May 12, 2020 @09:50PM
(#23162552)
Nice! I'm not sure exactly why a rather minor update to the GitHub CLI is near the top of HN, but looking at your project (and then seeing the link to your presentation) made it worthwhile for me.
Re:GitHub CLI allows you to close, reopen, and add metadata ...
by jquast on Thursday May 14, 2020 @10:54AM
(#23180265)
It's worse than that with Amazon.
The AWS Elastic Beanstalk CLI imports my package, but, when prompted to interview with AWS, they absolutely insisted that I perform their clowny online technical screening.
They trust to use my code in their product, but they don't trust that I know basic programming skills. The real kick in the shins is that I successfully passed this screening years ago, which they don't seem to want to count. Anyway, there are a thousand other candidates, f'em.
Re:GitHub CLI allows you to close, reopen, and add metadata ...
by dmitshur on Thursday May 14, 2020 @01:51AM
(#23175830)
(I didn’t downvote this comment.)
I agree it’s interesting, but I’m glad they’re using it. It’s better than them not using it. From looking at the history, I saw they rolled their own GraphQL client first, and started using my package only a month ago. See https://github.com/cli/cli/pull/719 and https://github.com/cli/cli/pull/758.
Also, to clarify, I did most of the development of the package in 2017 on my own accord, and joined Google in 2018. They didn’t pay me to work on it.
[1] https://github.com/cli/cli/blob/ad3a5903b2d327c1da8959708ef9...
[1] https://dmitri.shuralyov.com/talks/2017/githubql/githubql.sl...
[2] https://dmitri.shuralyov.com/blog/25
Anywho, building the package wasn't as altruistically motivated as I first imagined, since he was paid by Google to build it.
Edit: why the downvotes?
The AWS Elastic Beanstalk CLI imports my package, but, when prompted to interview with AWS, they absolutely insisted that I perform their clowny online technical screening.
They trust to use my code in their product, but they don't trust that I know basic programming skills. The real kick in the shins is that I successfully passed this screening years ago, which they don't seem to want to count. Anyway, there are a thousand other candidates, f'em.
I agree it’s interesting, but I’m glad they’re using it. It’s better than them not using it. From looking at the history, I saw they rolled their own GraphQL client first, and started using my package only a month ago. See https://github.com/cli/cli/pull/719 and https://github.com/cli/cli/pull/758.
Also, to clarify, I did most of the development of the package in 2017 on my own accord, and joined Google in 2018. They didn’t pay me to work on it.
[1]: https://magit.vc/manual/forge/
Found the answer: https://github.com/cli/cli/blob/ad3a5903b2d327c1da8959708ef9...