Making my living as CTO at a Swedish tech scale-up.
Opinions expressed here are my own.
1. You can realise more of them with a given capital.
2. More of them will be profitable and therefore worthwhile.
Hence no reduction.
1) Scale down # of humans -> keep same throughput
2) Keep same # of humans -> increase throughput
3) Increase # of humans -> significantly increase throughput
Most people think it's 1, but it's nearly always 2 or 3
“AI is not only not replacing (radiologists), but it’s actually increasing the amount of work they can do and increasing demand for their services,” www.ctvnews.ca/sci-tech/art... @ctvnews-mirror.bsky.social
1. You can realise more of them with a given capital.
2. More of them will be profitable and therefore worthwhile.
Hence no reduction.
Luddites: AI is obviously still as bad as it was that one time I used free ChatGPT in 2023
Reality: steady, moderately fast progress in a way that will disrupt a lot of industries
Luddites: AI is obviously still as bad as it was that one time I used free ChatGPT in 2023
Reality: steady, moderately fast progress in a way that will disrupt a lot of industries
If I were this person’s employer I’d be deeply worried about their aptitude, since apparently they can’t do their job without AI
The screenshotted tweet is correct. Like it's increasingly just part of working in the software industry now. I've struggled a lot despite working in a lucrative field because of discrimination. I can't deliberately put myself at a disadvantage.
The exact same advice that helps Alice penetration test her software can be used by Eve to attack Alice. Only one of them should get it.
How to implement that is not obvious, though.
The exact same advice that helps Alice penetration test her software can be used by Eve to attack Alice. Only one of them should get it.
How to implement that is not obvious, though.
A trivial example: just the other day, I got the idea to have Claude Code do my time reports, letting it control the software through Chrome devtools. Not what it's designed for, but it one-shotted it.
A trivial example: just the other day, I got the idea to have Claude Code do my time reports, letting it control the software through Chrome devtools. Not what it's designed for, but it one-shotted it.
this is how you combat the forces that want to make you fail
this is how you combat the forces that want to make you fail
"Millions of citizens today find truth itself oppressive. They feel it oppresses their political agency. [...] Stop trying to lecture people back into truth. Instead, help them recover a sense of political agency."
"Millions of citizens today find truth itself oppressive. They feel it oppresses their political agency. [...] Stop trying to lecture people back into truth. Instead, help them recover a sense of political agency."
2. Wait for Earth to heat up.
3. Grow olives on mount.
4. Lobby Christ to change venues.
5. Be new Israel.
6. Profit.
2. Wait for Earth to heat up.
3. Grow olives on mount.
4. Lobby Christ to change venues.
5. Be new Israel.
6. Profit.
The composition and detail are exquisite with the band of white snow/ice creating a perfect frame around the two people and the ship in the distance
Iconic imo
The composition and detail are exquisite with the band of white snow/ice creating a perfect frame around the two people and the ship in the distance
Iconic imo
But I agree soft personality traits are as important as technical skill. Toxic "superstars" are a net negative.
To me, software development is first and foremost a social activity performed by humans, with all the baggage that comes with being human. Technical competence is nice, but it is not the core of who we are.
1/10
But I agree soft personality traits are as important as technical skill. Toxic "superstars" are a net negative.