Archive

The Dulin Report

Browsable archive from the WordPress export.

2022

In most cases, there is no need for NoSQL Apr 18, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 Best practices for building a microservice architecture Apr 25, 2022 Good idea fairy strikes when you least expect it May 2, 2022 If you haven’t done it already, get yourself a Raspberry Pi and install Linux on it May 9, 2022 Most terrifying professional artifact May 14, 2022 Peloton could monetize these ideas if they only listen May 15, 2022 Am I getting old or is it really ok now to trash your employer on social media? May 25, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Automation and coding tools for pet projects on the Apple hardware May 28, 2022 Java is no longer relevant May 29, 2022 Good developers can pick up new programming languages Jun 3, 2022 Scripting languages are tools for tying APIs together, not building complex systems Jun 8, 2022 Keep your caching simple and inexpensive Jun 12, 2022 All developers should know UNIX Jun 30, 2022 Monolithic repository vs a monolith Aug 23, 2022 Why don’t they tell you that in the instructions? Aug 31, 2022 Using GNU Make with JavaScript and Node.js to build AWS Lambda functions Sep 4, 2022 Stop Shakespearizing Sep 16, 2022 The Toxic Clique Sep 28, 2022 Book review: Clojure for the Brave and True Oct 2, 2022 Why you should question the “database per service” pattern Oct 5, 2022 Why I am a poll worker since 2020 Nov 11, 2022 If we stop feeding the monster, the monster will die Nov 20, 2022 Things to be Thankful for Nov 24, 2022 Working from home works as well as any distributed team Nov 25, 2022 Should today’s developers worry about AI code generators taking their jobs? Dec 11, 2022

Should today’s developers worry about AI code generators taking their jobs?

December 11, 2022

At a high level, the answer is no.



Today’s COBOL developers maintain 60-year-old COBOL systems that capture the business domain knowledge accumulated over decades.



Today’s Java developers work on 20-year-old enterprise Java projects using libraries that have been around for 30 years and implementing business processes ironed out to the point of near perfection.



Today’s JavaScript developers will maintain 20-year-old Angular and React apps written in a transpiler language piled on top of another transpiler language piled on top of an interpreted language built upon another interpreted language and using 7673 abandoned npm modules 20 years from today. Mark my words.



While AI code generators are maturing, you are sitting there getting work done, writing lines of code. You, or someone like you, will maintain those lines of code for the next 20 years. 



Until AI can take a complex running system that integrates thousands of libraries, APIs, business rules, and domains, work with thousands of users and understand their needs, I think your job is safe.



On the other hand, you should be worried if your skills don’t extend beyond passing a simple code interview. You should be concerned if you lack personality and friendliness, can’t function in a team, and have no imagination. If large complex projects like I described in the above paragraph confuse and baffle you, you should also be worried.