People with this view seem to forget that writing code by hand is fun. Most of the experienced programmers I know only use AI to skip the actual boring parts (some boilerplate, the occasional "duplicate this module and change some details", stuff like that) and some of them don't use AI at all. One of them is required to use AI by his job and he says most of his co-workers don't like it.
The opposing viewpoints are there and I'm sure NYT knows it.
For 1: as a software company, they have a vested interest in ensuring that software engineers are as capable as possible. I don't know if anthropic as a company uses this as a guiding principle, but certainly some companies do (ex Jane Street). So they might see this as more important than investment cycles.
The quality of software engineers and computer scientists I've seen coming out of undergraduate programs in the last year has been astonishingly poor compared to 2-3 years ago. I think it's almost guaranteed that the larger companies have also noticed this.
In terms of "computational complexity" we mean the following:
Consider the following generalization of Sudoku. There is a number, N, and a grid of squares with N^2^ squares per side. (So the grid in total has N^4^ squares.) Each row and column of the grid has N^2^ squares. The grid therefore contains an N^2^ number of NxN subgrids (this corresponds to the 3x3 boxes in regular sudoku, called Houses). The puzzle is to fill each row, column, and house with the numbers from 1 to N^2^ with no duplicates.
The complexity is then a measure of how much harder the puzzles get when N is increased. Sudoku is a classic example of a so-called "NP-Hard" problem. Most puzzles that people think of as difficult are NP-hard. The ELI5 is that given a claimed solution to a sudoku puzzle, you can check if it really is the solution quickly (where again "quickly" is in terms of N). This is not true for the hardest types of puzzles in the witness.
This is only a proxy for how difficult humans will find the smaller puzzles but it's remarkably accurate. The hardest puzzles using every mechanic from the witness (realistically, only using two of them including the last one) are going to be much harder for a human than the hardest sudokus.
People underestimate how hard the puzzles are. In computational complexity terms, the hardest puzzles in the witness are harder than sudoku.
That's national. A source on Québec-specific cost inflation would be better, if it refutes the number in the article.
Of course as far as the CAD itself goes, inflation being lower than 3.1% already makes it suspicious to approve such a significantly larger increase. :/
I don't mean this in a bad way; did an AI write this comment?
For those unaware, HP recently secured one of the most idiotic deals I have ever seen a state-level government agree to: all laptops in Quebec purchased with public funds must be HP laptops. They said this will "encourage competition in the laptop market."
I can't wait to see this new decision blow up in HP's face.
Yeah it depends what you're doing. I do a lot of circuit modeling where different subsystems need to talk to each other. The solutions are either Rcs (and a bunch of custom drop logic) or a parent struct holding all the others. Both are awkward. But in other programming domains I've found rust pleasant.
Eh rust still has issues in some domains, e.g., when cyclic data is appropriate. You can do it, but it's annoying. To me, Haskell is really peak programming, but I know that's opinionated and most won't agree.
Vscode can do cross-file renames in pretty much any language. An LSP that doesn't support this is not doing its job.
Obra Dinn and outer wilds are two of my top 3 games ever made. If you liked outer wilds I'm pretty sure you'll like Obra Dinn.
Blue prince is great until you "win" the first time. After that, imo, it starts falling off. Slowly at first, then harder. I have completionist friends to whom I have given it negative reviews. But if you just want to win and explore the space for a while, even potentially hundreds of hours if you don't use guides, it's fun. Don't start a game day aiming to work on something specific. Work on what comes your way, and it is easily possible to make substantial progress every single game day.
In my personal experience, "coding" has been used as long as I can remember, but took over as the dominating term maybe 8-12 years ago.
I also prefer to say programming still. Coding sounds weird to me because it has its own separate (though certainly related) meanings.