| ▲ | Corrado 21 hours ago | |
The general problem I have with this is that I think those C-level executive should be doing C-level stuff and not programmer stuff. If you're using AI to help with your main job, great! If you're using AI to do someone else's work, then I think maybe you should change jobs. If you want to be a programmer, go for it! But not at the expense of your "real" job. I'm pretty sure the C-level people don't want us programmers faffing around with their roles. Why are they encroaching into ours? Don't they already have enough to do; setting the direction of the company, making sure it's profitable, selling things to people, etc.? | ||
| ▲ | simonh 17 hours ago | parent [-] | |
It very much depends what projects they are coding. One thing agentic coding is really good for is developing highly specific custom applications specifically for your own use case. This can include the kinds of decision support and analytics tasks a C-level relies on to understand how their organisation is functioning, what's actually going on, and where the gaps are. My team is using coding agents to develop analytics and reporting applications, and an engineering automation application, specific to our needs, that simply would not exist otherwise. The cost and time would be far too great. I can easily imagine there are plenty of cases like this, for all sorts of roles, including managerial ones, where only the person doing the job understands the job well enough to specify a requirement and guide an agent to code exactly what they need. | ||