That's what I want and look forward one day
I hate using voice for anything. I hate getting voice messages, I hate creating them. I get cold sweats just thinking about having to direct 10 AI Agents via voice. Just give me a keyboard and a bunch of screens, thanks.
Brainstorming/whiteboarding, 1:1s or performance feedback, team socialization, working through something very difficult (e.g. pair debugging): in-person or video
Incidents, asking for quick help/pointers, small quick questions, social groups, intra-team updates: IM
Bigger design documents and their feedback, trickier questions or debugging that isn't urgent, sharing cool/interesting things, inter-team updates: Email
It's hard for me to believe that there are psychopaths among us who prefer call on the phone, slack huddle or even organize meetings instead of just calmly writing messages on IM over coffee.
And don’t get me started on video vs text for learning purely non-physical stuff like programming…
sending audio = fast
Though I'll gladly call it various foul names when it's refusing to do what I expected it to do.
Yeah, I think I’d rather click and type than talk, all day.
Some of us who’ve been in this game for a while consider having healthy hands to be a nice break between episodes of RSI, PT, etc. YMMV of course but your muscle stamina won’t be the problem, it’s your tendons and eventually your joints.
I've done more typing than speaking for over 40 years now, and I've never had any carpel tunnel or joint problems with my hands (my feet on the other hand.. hoo boy!) and I've always used a standard layout flat QWERTY keyboard.. but I never bend my hands into that unnatural "home row" position.
I type >60wpm using what 40 years ago was "hunt and peck" and evolved over brute force usage into "my hands know where they keys are, I am right handed so my right hand monopolizes 2/3 of the keyboard, both hands know where every key is so either one can take over the keyboard if the other is unavailable (holding food, holding microphone for when I do do voice work, using mouse, etc)".
But as a result my hands also evolved this bespoke typing strategy which naturally avoids uncomfortable poses and uncomfortable repetition.
1. Superwhisper - https://superwhisper.com
2. Macwhisper - https://goodsnooze.gumroad.com/l/macwhisper
3. Carelesswhisper - https://carelesswhisper.app
I’m very sorry for you if this is literally true. I would urge you to seek medical help, as this is not normal at all.
I think I'm marginally faster using speech to text than using a predictive text touch keyboard.
But it makes enough mistakes that it's only very slightly faster, and I have a very mild accent. I expect for anyone with a strong accent it's a non starter.
On a real keyboard where I can touch type, it's much slower to use voice. The tooling will have to improve massively before it's going to be better to work by speaking to a laptop.
But I can appreciate that sitting down in front of a keyboard and going at it with low typing speed seems unnatural and frustrating for probably the majority of people. To me, in front of a keyboard is a fairly natural state. Somebody growing up 15 years before (got by without PCs in their early years) or after me (got by with a smartphone) probably doesn't find it as natural.
That's exactly what everyone is hoping for. Well, everyone except software engineers, of course
I don't understand the pleasure of putting people out of work and the pain on people's lives and careers but I guess that's just me.
If the cost of writing software goes down, demand for it will presumably go up...
All those skills can be applied to engineering as well. What makes Fabrice Bellard great? Its not just technical skill I think.
I think some of the most successful people will be a subset of engineers but also Steve Jobs types and artists
Having all this in one person is super valuable because you lose a lot of speed and fidelity in information exchange between brains. I wouldn't be surprised if someone could hit like 30-50 kloc/day within a few years. I can hit 5-10kloc/day doing this stuff depending on a lot of factors, and that's driving ~2 agents at a time mostly. Imagine driving 20.
Here is an unwanted advice, it is not going to be the new hotshot developer, rather hotshot technical and solution architects.
The dream of CASE tools is finally here, pump the requirements into the software factory (aks instruction files), and the replicator handles the rest.