Hacker News Reader

You can become more specialised; but that will only take you so far. Coding will soon become no more than a means to an end. Which it always was. The only way out for developers is through expanding their vision beyond that of the tools made available to them. Why does something need to be coded? What does the end customer expect? Did they vocalise their need properly? Contextual knowledge can hardly be reproduced and is the best way to beat a ChatGPT-like tool.

This is the content I clicked for and I feel like it's pretty vague and poorly-articulated, but there's a seed of truth here. Coding is a highly-technical profession and Chat-GPT does seem to trivialize it somewhat. With Chat-GPT automating out some of the developers, you will still need some developers around to understand and review the AI's output. The developers who remain will be the ones who are high-functioning: the ones who can communicate with both technical and non-technical staff, understand the business logic, and fill-in the blanks of what the customer needs.

In this future, Chat-GPT replaces some technical staff positions. So how does that work? In my experience with the tool, getting it to write anything multidimensional--like a board game--requires hours of back-and-forth articulating and re-articulating the interface, the business rules, and how those things interact. In this sense, it's like those developers who throw up their hands and complain about the requirements documentation while other developers stay in constant contact with the stakeholders during the development process to deliver the business needs. I don't think the later need to worry about job security.

View on HN