Agree, think about it as scribbles we make on the scratch pad when thinking through a challenging math question. It mostly serve as input to our ongoing thinking process, rather than persistence of thoughts.
I read it as an experiment and hypothesis. The author is on a quest to prove their hypotheses. I appreciate the insight into the work in progress and the potential outcomes. It's more beneficial for me than waiting several months to see it fully proven.
The decision to open source is surprising at first glance. But it makes a lot of sense. With the greatly enhanced coding productivity, the ROI for tweaking open source tools is quite high. This puts closed source tools at a significant disadvantage in terms of customization.
They are a little late to the AI coding assistant market, this move enables them to capture market share rapidly and slow down the competitors in building up data moat.
This is awesome and has huge potential to improve developer productivity!
The only thing that it gives me pause is that it requires a very broad Github authorization. Do you really need to "be able to read and write all public and private repository data"?
I haven’t used the SO recruiting tool. But I’d imagine it would let me skim the questions a candidate have been asking / answering. So I get a sense of their technical / communication skill, and passion about their domain.
As an engineering manager I found LinkedIn to be very inefficient in finding quality talents at scale. There isn’t enough signal to gauge which candidate is worth bringing in for interviews. There seem to be a large opportunity for new business here.