Meanwhile, some new details emerged about the days leading up to Altman’s firing. “In the weeks leading up to his shocking ouster from OpenAI, Sam Altman was actively working to raise billions from some of the world’s largest investors for a new chip venture,” Bloomberg reported. Altman reportedly was traveling in the Middle East to raise money for “an AI-focused chip company” that would compete against Nvidia.
As Bloomberg wrote, “The board and Altman had differences of opinion on AI safety, the speed of development of the technology and the commercialization of the company, according to a person familiar with the matter. Altman’s ambitions and side ventures added complexity to an already strained relationship with the board.”
“According to people familiar with the board’s thinking, members had grown so untrusting of Altman that they felt it necessary to double-check nearly everything he told them,” the WSJ report said. The sources said it wasn’t a single incident that led to the firing, “but a consistent, slow erosion of trust over time that made them increasingly uneasy,” the WSJ article said. “Also complicating matters were Altman’s mounting list of outside AI-related ventures, which raised questions for the board about how OpenAI’s technology or intellectual property could be used.”
When using any new language or framework I can get up and running very quickly.
Used to take time to read the intro docs and then start digging around trying to find the features I need. Now I can straight ask it how to do certain things, what is supported and the best practises.
If I see a block of code I don’t understand I can ask it to explain and it will write out line by line what it’s doing. No more looking for articles with similar constructs or patterns.
It’s amazing at breaking down complex SQL.
Many tedious refactoring tasks can be done by it.
Creating mappers between classes is very good because it can easily pickup matching properties through context if types and names don’t match.
Generating class from a db table and vice versa.
If you have a specific problem to solve rather than googling around for other solutions you can ask it for existing methods. This can save days or more of discovery and trial and error.
It’s really good generating test cases based on a method.
Recently I implemented a C# IDictionary with change tracking built in. I pasted the code in, it analysed it and pointed out a bug then wrote all the tests for the change tracking.
It did better than I thought it would. Covering lots of chains of actions. Which again found a bug.
It’s fairly good at optimising code as well.
As for the mistakes you should be able to spot them and ask it to correct. If it does something invalid tell it that and it will correct.
You have to treat it like a conversation not just ask it questions.
Like Google you have to learn how to use it correctly.
We also have bing enterprise which uses search results and sources its answer. So I can look at the actual web result and read through.
The hallucination thing is basically a meme at this point by people that haven’t really used it properly.
As a newer developer is has been amazing for me and alot of experienced developers also recognize how much benefit it provides so im honestly confused by your standpoint.
You’ll find the old guard hates change and will shit on things like this without even trying them.