# AI & Software Engineering: Time for optimism

DevFeed: [AI & Software Engineering: Time for optimism](<https://devfeed.tech/articles/ai-software-engineering-time-for-optimism-25213.md>)

Original publisher: [Read original article](<https://kau.sh/blog/ai-learning/>)

Author: Kaushik Gopal

Published: 2025-03-09T22:22:02Z

Content type: opinion

Language: en

Sources: [Kaushik Gopal's Site](<https://devfeed.tech/sources/kaushik-gopal-s-site.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-for-code](<https://devfeed.tech/tags/ai-for-code.md>), [code](<https://devfeed.tech/tags/code.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experience](<https://devfeed.tech/tags/experience.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

## AI overview

This opinion article argues that software engineers should view AI as a tool for learning and increasing their value, rather than focusing primarily on fears of job replacement. It emphasizes human judgment about what and how to build, while describing AI as useful for code generation and accelerated learning. The author gives an example of using Google's Notebook LM with an article and official Kotlin documentation to clarify Coroutine Dispatcher concepts in about 30 minutes instead of an estimated 2-3 hours.

## Source excerpt

Many software engineers (myself included, not long ago) have been anxious about AI replacing our jobs. It's a natural concern. But I've been diving deep into using AI for software engineering. I've had a realization: We should stop worrying about job losses. Start seeing AI as a tool to make us more valuable. The key? Use AI for learning, not just code generation. Relying solely on AI for code generation is the trap. The truly valuable skill is judgment.1 The judgment to decide what to build and how to build it.2 AI excels at the actual building (code generation). Embrace this. It's inevitable. Most future code will be written|generated with AI. The good news? AI is amazing for learning. Some examples ### I think back to my undergraduate days. A concept didn't click? It meant a bike ride to the library. I'd search for textbooks, pull references, and try to piece it all together. Assuming the books were even available. Guess what I often did? I didn't bother. Today, I'd just pull up my phone and look it up. The internet was a game-changer for students. AI is the next game-changer for all of us willing to learn. A more recent example: I'm doing an upcoming Fragmented episode on an article that my friend Colin3 wrote on Coroutine Dispatcher use. I understood about 75% on the first pass. But a few gaps remained, especially around how they related to Coroutine fundamentals. I needed to brush up. Without AI, my process would have been: Open a bunch of articles and docs. Read each one thoroughly. Synthesize the information mentally. Connect the dots with the article. Time: 2-3 hours, plus significant mental bandwidth. With AI: Uploaded Colin's article and official Kotlin docs to Google's Notebook LM. Asked targeted questions, addressing my knowledge gaps directly. Time: 30 minutes to reach a firm understanding. What would have taken 2-3 hours took about 30 minutes.4 And I understood the concepts better. AI is your opportunity to level up. Learn faster. Position yourself to