Being a Chief Technology Officer is no longer the job. We now need an end-to-end AI orchestrator for the corporation in the Chief Agentic Officer role. Dana Lawson is now obsolete and must be let go.
It sure is convenient AI isn't capable of doing the c-suite's job
Human C-suites will continue to keep their jobs as long as other humans in similar positions continue to buy into their airy-fairy "strategy" stuff. ;)
But what do you think about her opinion? Is writing code still a job of developers going forward? and why?
If a CTO said something in the woods, and no one re-posted it, are they still a CTO or just a crazy person screaming in the woods? By amplifying his message you are justifying his job, position, and standing.<p>This got me thinking on a new way to improve the news: Instead of reporting on the empty words people say, only report on what they have done, example:<p>a) Elon Musks says SpaceX is the best thing ever worth the most money ever because he is greatest person ever.<p>as opposed to:<p>b) SpaceX, run by Elon Musk, is currently Making $X per quarter, they do this by ......
They're only called CTO if they're from CTO region of France.<p>Otherwise it's just sparkling AI-Cheerleader.
Wow, you got agitated. Writing code was never a job. Software engineer is a job where part of the responsibility is to create code. If all you do is “write code”, don’t complain.
Netlify CTO in 6-18 months: that vibe project that caused me to say writing code is no longer the job got so unmaintainable that I hired a team of 3 to take it over. They're rewriting it by hand because tokens are too expensive now. Nobody could have seen this coming
> I hired a team of 3 to take it over<p>There are large areas of software where the quality of code is measured by the mental model of its human maintainers. For these areas, LLMs are a net negative because their use degrades the mental model of the human maintainers.
Dana needed to repeat the lie <i>before</i> companies started blowing past their annual AI budget and began to panic.
[dead]
It was never the job as long as the profession was called "software engineer" and not "coder".
> a billion new applications written by 2029<p>So we will have a billion new hello world, stock checker, Calendar, Todo apps, and ...? Just because you have a way to write code fast, doesn't mean you are going to come up with billions of new ideas of what to do with that code, and to be mean about it, most people don't think they are creative enough to come up with ideas and are just fine watching sports all day on tv.<p>The apple app store currently has 2,362,917 (<a href="https://42matters.com/ios-apple-app-store-statistics-and-trends#available-apps-count" rel="nofollow">https://42matters.com/ios-apple-app-store-statistics-and-tre...</a>) apps in the app store, and a lot of those are the same thing, so 0.236% of a billion.<p>but to be fair, with Cluade I've written at least 10 apps I use every day. If everyone in the world (8.3 billion people) would do this, then we might get close to that billion new apps.
A CTO who doesn't understand what "the job" was. Classic.
I wonder if code quality goes up if you include “as a rockstar ninja” in your prompt
just last week we moved away from netlify to our own solution on AWS.
Services like netlify who are a layer on top of AWS are no longer needed.
Writing code was never the job. Writing code was always a means to the job. This is why people hire "software engineers", not merely "programmers".
I'm not even sure if I disagree with the conclusion, but I feel pretty safe disregarding the words spoken in front of a slide profoundly declaring "UX + DX = AX"
Little late to the thought leadership circus. What's next, limp LinkedIn posts only her sycophants like?
Looking at Dana Lawson's career on linked in, it looks like they never spent time being an actual developer. Seems fitting that a completely out of touch elite in the US would make such statements.
Petty personal attack. A technical manager who manages developers should know very well the job of their reports.<p>"Out of touch elite"? a MAGA-like populism view in a place where MAGA is (rightly) looked down on.
I wonder how many people saying similar things have the same background, but having said that she was VP of Engineering at GitHub, and VP of Engineering at Heptio.
Dont use the word 'elite' when describing people like this, it implies they are the best at something, which in my experience has never been the case, unless you count bullshitting and gaslighting.
When I was younger I used to assume that CTO was like the ultimate experienced engineer, and most every CTO I've dealt with in 25 years has been a needle scratch for that assumption.
There are competent CTOs who are not above <i>getting their hands dirty</i>, and there are <i>career politician</i> type CTOs who have no discernible skills beyond projecting an illusion of technical brilliance.<p>I've seen plenty of both, and I'm sure everything in between exists too.
> career politician type CTOs<p>Good description; that's been the my majority of companies unfortunately.
How about product only CTOs who quietly hate engineers because they don't know what they do, and they constantly feel threatened
A CTO once asked me: Why do we have a test and staging environment? Could we propose removing them as cost savings initiative? During a time when cost savings where the number 1 priority.<p>What a tiring world.
I've known one semi-decent one in a circa 100 people business. Used to be the head of engineering. But he was fully transactional, sell stuff mode most of the time as CTO. CEO actually said one time that he wondered if he'd "ruined" the guy a little by making him CTO.<p>He tried to bail me out of some very deep trouble i got myself in. Didn't end up working out, but he was good folk for sticking his neck out for someone on the engineering team when customers were screaming at him over the phone because of my screw up.<p>Rest of the time, they've been a networking contact of the CEO who has "some tech stuff" on their resume. Last one screwed me over and fucked three years worth of work in one fell swoop (and he admitted he did this for his own gains over slack when challenged on one of my last days at that job). still not over that one.
Was it ever "the job" at a place like Netlify? Who cares?