71–80 of 388 posts
Earlier quoted context omitted.
> If I … generate fairly exhaustive unit tests of a trivial function … then you are not a senior software engineer
Neither are you if that's your understanding of a senior engineer
> survey of 791 developers We have got to stop. In a universe of well over 25 million programmers a sample of 791 is not significant enough to justify such headlines. We’ve got to do better than this, whatever this is.
> survey of 791 developers We have got to stop. In a universe of well over 25 million programmers a sample of 791 is not significant enough to justify such headlines. We’ve got to do better than this, whatever this is.
From another perspective: we've deduced a lot of things about how atoms work without any given experiment inspecting more than an insignificant fraction of all atoms.
TL;DR: The population size (25e6 total devs, 1e80 atoms in observable universe) is almost entirely irrelevant to hypothesis testing.
Also, green coding? That's new to me. I guess we'll see optional carbon offset purchasing in our subs soon.
Earlier quoted context omitted.
Neither are you if that's your understanding of a senior engineer
I think the parent commentors point was that it is nearly trivial to generate variations on unit tests in most (if not all) unit test frameworks. For example: Java: https://docs.parasoft.com/display/JTEST20232/Creating+a+Para... C# (nunit, but xunit has this too): https://docs.nunit.org/articles/nunit/technical-notes/usage/... Python: https://docs.pytest.org/en/stable/example/parametrize.html cpp: https://google.gith…
So how many developers in that survey are those? They surveyed 791 developers (:D) and "a third of senior developers" do that. That's... generiously, what... 20 people? It's amazing how everyone can massage numbers when they're trying to sell something.
And of course, its an article based on a source article based on a survey (of a single company), with the source article written by a "content marketing manager", and the raw data of the survey isn't released/published, only some marketing summary of what the results (supposedly) were. Very trustworthy.
This article goes completely against my experience so far. I teach at an internship program and the main problem with interns since 2023 has been their over reliance on AI tools. I feel like I have to teach them to stop using AI for everything and think through the problem so that they don't get stuck. Meanwhile many of the seniors around me are stuck in their ways, refusing to adopt interactive debuggers to replace…
> Meanwhile many of the seniors around me are stuck in their ways, refusing to adopt interactive debuggers to replace their printf() debug habits, let alone AI tooling... When I was new to the business, I used interactive debugging a lot. The more experienced I got, the less I used it. printf() is surprisingly useful, especially if you upgrade it a little bit to a log-level aware framework. Then you can leave your de…
Seems about right for me (older developer at a big tech company). But we need to define what it means that the code is AI-generated. In my case, I typically know how I want the code to look like, and I'm writing a prompt to tell the agent to do it. The AI doesn't solve any problem, it just does the typing and helps with syntax. I'm not even sure I'm ultimately more productive.
But your approach sounds familiar to me. I find sometimes it may be slower and lower quality to use AI, but it requires less mental bandwidth from me, which is sometimes a worthwhile trade off.
Seems about right for me (older developer at a big tech company). But we need to define what it means that the code is AI-generated. In my case, I typically know how I want the code to look like, and I'm writing a prompt to tell the agent to do it. The AI doesn't solve any problem, it just does the typing and helps with syntax. I'm not even sure I'm ultimately more productive.
Earlier quoted context omitted.
Claude is making $72k a year for a consistent $300/day spend.
Bear in mind those are revenue figures, they're costing claude hundreds a day. One imagines Leadership won't be so pleased after the inevitably price hike (which, given the margins software uses, is going to be in the 1-3 thousands a day) and the hype wears off enough for them to realize they're spending a full salary automating a partial FTE.