I'm not so quick to label him an asshole. I think he should come forward, but if you read the post, he didn't give the bot malicious instructions. He was trying to contribute to science. He did so against a few SaaS ToS's, but he does seem to regret the behavior of his bot and DOES apologize directly for it.
In my experience building a couple ChatGPT apps and, through colleagues, working with OpenAI folks, I'm not sure they should be building anything in their current state. Seems quite disorganized over there.
Talk the LLM and have it explain code. Write very small examples by hand and make sure you understand how they work. Big software is just a bunch of those small things working together.
I think a lot of the people in positions of power in the AI industry think that AGI/superintelligence will solve the climate crisis, aging, scarcity, and many other tough problems by doing novel science. I hope they are correct.
I've lived in California for 20 years so this is my first year of non-draught. We've been enjoying the unusual prevalence of greenery in Orange County.
…says every charlatan who wanted to keep their position. I’m not saying you’re a charlatan but you are likely overestimating your own contributions at work. Your comment about feeding on data - AI can read faster than you can by orders of magnitude. You cannot compete.
I think we all need to respond by being very, very flexible and open minded about how to contribute to society going forward. I'm on the back end of my career but I imagine it's terrifying for newcomers. Stay agile! We're all in this together.
How about just be punctual, respecting the time others have agreed to meet with you? Simpler solution than what this article suggests. People will abuse that system just the same anyway.
I suspect a lot of the traffic shift is from Google replacing the top search result, which used to be Stack Overflow for programming questions, with a Gemini answer.
It’s not a huge impediment but it adds up through: extra lines of sig code I now need to essentially ignore as I read as well as waiting for precommit hooks to check a giant codebase for compliance, plus extra rbi files in git. If engineers followed convention over config and tested types where necessary, no need for inline types. Just use TS if you want types.
As long as Matz is firmly against, inline typing should never be a part of Ruby. I started working on a large Rails codebase that adopted Sorbet and it is nothing but an impediment to progress.
Counter question: how does a training set, representing a window into the past, differ from your own experience as an intelligent entity? Are you able to see into the future? How?