it’s like adding an extra layer of user error. why would you want to do that? as a dev myself it’s like the bullshit middle managers/project managers and CTOs introduced a few years ago with “pair programming” or whatever it’s called. the intention was to speed up development time but in long run it just slowed you down. it was such a god damn dumb idea but was all the rave on the bullshit linkedin and tech bro blogs.
i’ve been in this industry long enough now to know the majority of tools and processes are created by people who don’t use said tools or processes.
An extra level of user error that you can’t audit.
I work as an officer manager, an import part of my job is auditing all the contacts and payments to make sure they are being done properly. Then my work also gets audited on a regular basis.
And lot of time and money is spent making sure things are completed properly with the appropriate paperwork so that at any point someone can say “why did X happen?” and find all the related paperwork. AI can’t do that, it’s a black box.
Pair programming is kind of a weird thing to rail against. Sure, it would be terrible if it was mandated for everything, but there are many times it is a useful tool, especially for complex tasks where it is useful to talk through options as you go. Also invaluable for mentorship. I have regular sessions with juniors where we pair program on work tasks as a teaching tool.
it’s like adding an extra layer of user error. why would you want to do that? as a dev myself it’s like the bullshit middle managers/project managers and CTOs introduced a few years ago with “pair programming” or whatever it’s called. the intention was to speed up development time but in long run it just slowed you down. it was such a god damn dumb idea but was all the rave on the bullshit linkedin and tech bro blogs.
i’ve been in this industry long enough now to know the majority of tools and processes are created by people who don’t use said tools or processes.
It is like pair programming isn’t it, if your partner randomly hallucinated and couldn’t explain what they’d done after the fact.
An extra level of user error that you can’t audit.
I work as an officer manager, an import part of my job is auditing all the contacts and payments to make sure they are being done properly. Then my work also gets audited on a regular basis.
And lot of time and money is spent making sure things are completed properly with the appropriate paperwork so that at any point someone can say “why did X happen?” and find all the related paperwork. AI can’t do that, it’s a black box.
Middle managers entire reason for existence seems to be to slow things down and introduce mistakes.
Pair programming is kind of a weird thing to rail against. Sure, it would be terrible if it was mandated for everything, but there are many times it is a useful tool, especially for complex tasks where it is useful to talk through options as you go. Also invaluable for mentorship. I have regular sessions with juniors where we pair program on work tasks as a teaching tool.