Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (43)

Strategic activity mapping for software architects May 25, 2025 The future is bright Mar 30, 2025 Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers Feb 11, 2023 Should today’s developers worry about AI code generators taking their jobs? Dec 11, 2022 Scripting languages are tools for tying APIs together, not building complex systems Jun 8, 2022 Java is no longer relevant May 29, 2022 Best practices for building a microservice architecture Apr 25, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 In most cases, there is no need for NoSQL Apr 18, 2022 A year of COVID taught us all how to work remotely Feb 10, 2021 What programming language to use for a brand new project? Feb 18, 2020 Microsoft acquires Citus Data Jan 26, 2019 The religion of JavaScript Nov 26, 2018 Teleportation can corrupt your data Sep 29, 2018 Let’s talk cloud neutrality Sep 17, 2018 What does a Chief Software Architect do? Jun 23, 2018 TypeScript starts where JavaScript leaves off Aug 2, 2017 Node.js is a perfect enterprise application platform Jul 30, 2017 Design patterns in TypeScript: Chain of Responsibility Jul 22, 2017 Rather than innovating Walmart bullies their tech vendors to leave AWS Jun 27, 2017 TDWI 2017, Chicago, IL: Architecting Modern Big Data API Ecosystems May 30, 2017 Copyright in the 21st century or how "IT Gurus of Atlanta" plagiarized my and other's articles Mar 21, 2017 Online grocers have an additional burden to be reliable Jan 5, 2017 Don't trust your cloud service until you've read the terms Sep 27, 2016 In search for the mythical neutrality among top-tier public cloud providers Jun 18, 2016 What can we learn from the last week's salesforce.com outage ? May 15, 2016 JEE in the cloud era: building application servers Apr 22, 2016 Managed IT is not the future of the cloud Apr 9, 2016 JavaScript as the language of the cloud Feb 20, 2016 Our civilization has a single point of failure Dec 16, 2015 IT departments must transform in the face of the cloud revolution Nov 9, 2015 We Live in a Mobile Device Notification Hell Aug 22, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 Attracting STEM Graduates to Traditional Enterprise IT Jul 4, 2015 Your IT Department's Kodak Moment Jun 17, 2015 Big Data is not all about Hadoop May 30, 2015 Smart IT Departments Own Their Business API and Take Ownership of Data Governance May 13, 2015 What can Evernote Teach Us About Enterprise App Architecture Apr 2, 2015 Microsoft and Apple Have Everything to Lose if Chromebooks Succeed Mar 31, 2015 On apprenticeship Feb 13, 2015 Wall St. wakes up to underinvestment in OMS Aug 21, 2014 Cassandra: Lessons Learned Jun 6, 2014

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.