I read that as combined, up to this point in time. You have 20 engineers? If you haven't spent at least $20k up to this point, you've not explored or experienced enough of the ins and outs to know how best to optimize the use of these tools.
I didn't read that as you need to be spending $1k/day per engineer. That is an insane number.
EDIT: re-reading... it's ambiguous to me. But perhaps they mean per day, every day. This will only hasten the elimination of human developers, which I presume is the point.
> No, there is Github Copilot, the AI agent tool that also has autocomplete, and a chat UI.
When it came out, Github Copilot was an autocomplete tool. That's it. That may be what the OP was originally using. That's what I used... 2 years ago. That they change the capabilities but don't change the name, yet change names on services that don't change capabilities further illustrates the OP's point, I would say.
To be fair, Github Copilot (itself a horrible name) has followed the same arc as Cursor, from AI-enhanced editor with smart autocomplete, to more of an IDE that now supports agentic "vibe coding" and "vibe editing" as well.
I do agree that conceptually there is a big difference between an editor, even with smart autocomplete, and an agentic coding tool, as typified by Claude Code and other CLI tools, where there is not necessarily any editor involved at all.
Thanks... 2 years felt a bit too recent. I think I was trialing copilot in late 2022, and then got turned on to ... codeium/windsurf in late 2023. The years are merging together now. :/
That's silly. Gmail is a wildly different product than it was when it launched, but I guess it doesn't count since the name is the same?
Microsoft may or may not have a "problem" with naming, but if you're going to criticize a product, it's always a good starting place to know what you're criticizing.
It was absolutely under version control and there was a full test suite. The guy that wrote it is easily in the top 3 smartest human beings I've ever met and an incredibly talented developer. Unfortunately a lot of his stuff required being at the same level on the IQ bell curve, which meant it was functionally unmaintainable by anyone else. If you're familiar with the Story of Mel, it was kinda like that.
Petty as in 'small and does not really matter' or petty as in 'vindictive'. All administrations do many small things that may not ultimately have much impact, but often those may be for benign reasons. Understanding the reasoning behind the decisions would help in determining what kind of 'petty' this is.
> if a person is visually impaired, why wouldn't they have tools at their disposal to make things readable?
If it's on a screen in a browser, probably. If it's printed, or on a display not under a reader's control, probably not.
FWIW, I'm partially split. I generally prefer sans-serif overall - have for decades. I think I slightly prefer serif for some printed material visually, but... when I actually have to engage and read it, for long periods, I think I tend to opt for sans-serif. Noticed this on my kindle years ago, and kindle reader now - I usually swap to sans-serif options (I think it's been my default for a while).
Can he read? No doubt he can read some. I can't say he's illiterate. But functionally, he's nowhere near the reading and comprehension skills of what we should expect from a national leader.
I didn't read that as you need to be spending $1k/day per engineer. That is an insane number.
EDIT: re-reading... it's ambiguous to me. But perhaps they mean per day, every day. This will only hasten the elimination of human developers, which I presume is the point.
reply