Comment by iugtmkbdfil834
12 hours ago
I am saying, having seen stuff implemented that simply does not make sense to anyone with an understanding of the actual situation on the ground, yes. And the funny thing is, it is not even an llm issue. This is a very, very human issue.
So is the actual work of programming is mostly just sitting in meetings where business people and programmers slowly muddle through requirements?
The actual work happens in the head. I suspect you know this. Now, there is a clear benefit to being able to flatten some of the issues related to coding, but do you really think, any of it can be done without those meetings and muddling through those requirements? At the very least, there needs to be one person that understands what is actually needed.
I mean.. I am ok with you saying saying yes. In a sense, I half expect it. I will be very subtle, I don't believe the issue lies with the tooling ( AI or not ).
I spend an unusually small proportion of my life in meetings, probably an idiosyncratic feature of my job.
My impression is that the main reason most people have so many meetings is because meetings are equated to work. If you are in a meeting, you are at work and you need to work. This is because, in a meeting, everyone is looking at everyone else with the expectation that they are working. But if you are not in a meeting, this expectation doesn't exist, so you are basically not at work and you don't need to work.
In particular, thinking only occurs during meetings. And if it didn't happen during a meeting, it didn't happen.
Call me cynical, but it explains immediately why the vast majority of companies don't tolerate remote work unless they're forced to by a pandemic. Office work means someone could be watching you outside meetings, which causes some work to happen outside of meetings and raises productivity.