DEV Community: kiran

🤖 AI Can Write My Code. But Apparently, I Still Need to Know How to Press Enter.

kiran — Mon, 05 Oct 2026 10:30:51 +0000

AI coding tools are getting crazy good.

They can read your project, understand multiple files, write code, modify existing code, run commands, inspect the database, and even make changes to your application.

So naturally, I started wondering:

Are developers becoming less important?

Then Antigravity gave me a very small reminder that maybe the answer isn't that simple.

The normal experience

This is what the AI coding environment normally looks like while I'm working:

You have the editor on the left and the AI panel on the right.

You can ask the AI to do something like:

"Add Razorpay payment integration and create a demo account fallback."

The AI starts working.

It explores the project.

It reads files.

It runs commands.

It thinks about the implementation.

It modifies the application.

Honestly, it's impressive.

It feels less like autocomplete and more like having another developer sitting next to you.

Then something funny happened

At some point, the AI needed permission to perform an action.

And the UI changed to something like this:

The AI was waiting for me.

There were approval options.

But for a moment, I was just looking at the screen thinking:

"Okay... what exactly am I supposed to do here?"

😂

The funny part is that we're using an AI development tool capable of navigating a project and working with our application...

but the human developer is suddenly confused about how to interact with the AI.

And then I discovered the easiest solution

Press Enter.

That's it.

I didn't need to write code.

I didn't need to debug anything.

I didn't need to ask the AI another question.

I just needed to press:

Enter

And the AI continued.

😂

But this tiny thing made me think about something bigger

At first, this was just funny.

But then I started thinking about how we talk about AI replacing developers.

We often imagine the future like this:

AI writes the code → application is built → developer is no longer needed.

But real software development isn't that clean.

There are always little things happening around the code.

Someone has to understand the environment.

Someone has to understand what the AI is doing.

Someone has to decide whether an action should be allowed.

Someone has to notice when something doesn't make sense.

And sometimes...

someone has to figure out that pressing Enter will continue the process.

AI can write code. Developers solve problems.

This is where I think the role of a developer is changing.

Previously, a lot of our time was spent writing code manually.

Now I can ask AI to generate a component.

I can ask it to create an API.

I can ask it to modify a database query.

I can ask it to investigate an error.

I can ask it to explore an unfamiliar part of the project.

That doesn't make my job disappear.

It changes what I spend my time doing.

Instead of only asking:

"How do I write this code?"

I'm increasingly asking:

"What should actually happen here?"

"Is this implementation correct?"

"What could this break?"

"Why did the AI choose this approach?"

"Is this safe to run?"

"What happens in production?"

Those questions are much more difficult to automate.

And then there is UX

There was another thing I noticed from this experience.

AI tools can be incredibly sophisticated internally.

But that doesn't mean every part of their user experience is perfect.

For example, if an AI is asking me to approve something, I want the interaction to be immediately obvious.

Give me:

a clear approval button
a clear decline button
a visible keyboard shortcut
a comfortable scrollable area
an obvious indication that the AI is waiting for me

Because developers shouldn't have to guess how to operate the tool that is supposed to help them develop faster.

And that's not really an AI problem.

It's a developer experience problem.

This is where humans still matter

I don't think the future is going to be:

Humans vs AI

I think it's going to be:

Humans + AI

But there will be a difference between someone who simply accepts whatever AI generates and someone who actually understands what is happening.

Imagine two developers looking at the same AI-generated code.

Developer A:

"AI generated it, so it must be correct."

Developer B:

"Why did it do this? Is this compatible with our architecture? What happens if this API fails? What happens with existing users?"

The second developer gets much more value from AI.

Because AI becomes a multiplier for their knowledge, rather than a replacement for it.

Maybe AI won't replace developers. Maybe it will change what "developer" means.

I don't think we should ignore how powerful AI has become.

It absolutely will replace some repetitive development work.

It will change workflows.

It will reduce the amount of code humans manually write.

And developers who refuse to learn these tools may eventually find themselves slower than developers who use them effectively.

But there's something AI still doesn't magically give you:

judgment.

Knowing what should happen.

Knowing what shouldn't happen.

Knowing when the generated code is wrong.

Knowing what to investigate.

Knowing what question to ask next.

Knowing when the problem isn't the code at all.

And sometimes...

knowing that the solution is simply:

"Press Enter." 😂

The irony

We're building tools where AI can:

read our code

understand our project

modify files

run commands

interact with our development environment

and help build applications

And yet, sometimes the most important developer contribution is:

"Wait... where is the button?"

😂

And honestly, I think that's okay.

Because software development has never been only about typing code.

It's about understanding problems and figuring things out.

AI is getting much better at the first part of implementation.

Developers still need to own the outcome.

Final thought

Maybe the wrong question is:

"Will AI replace developers?"

Maybe the better question is:

"When AI can write the code, what makes someone a good developer?"

For me, I'm starting to think the answer is:

Not just knowing how to write code.

It's knowing how to think, question, debug, evaluate, and figure things out when things don't go exactly as expected.

Even if the unexpected problem is just...

an AI tool waiting for you to press Enter. 🤖😂

A Fly’s Brain Is Running in a Computer… Human Brain Is Next? 💀

kiran — Wed, 16 Sep 2026 09:20:20 +0000

Scientists have mapped a fruit fly's brain in incredible detail and are using that information to build computational models of its neural network.

And honestly…

I have only one question:

When is it our turn? 😂

Because if this technology keeps moving forward, maybe students won't need to spend years studying anymore.

Imagine the future:

👨‍🏫 Teacher:
"Have you studied AI?"

🧑‍🎓 Student:
"No."

👨‍🏫:
"Have you studied mathematics?"

🧑‍🎓:
"No."

👨‍🏫:
"Programming?"

🧑‍🎓:
"No."

👨‍🏫:
"Then what HAVE you studied?"

🧑‍🎓:

"Nothing. AI trained my brain." 😎

The future learning process:

Old way:

School
↓
College
↓
Study
↓
Study more
↓
Study again
↓
Exam
↓
Forget everything 😭

Future:

AI
↓
Train Brain 🧠
↓
Download Knowledge
↓
Done ✅

No exams.

No assignments.

No "please explain this in your own words." 😂

You just wake up and suddenly:

"Congratulations! You now know calculus, Python, quantum physics and how to fix production bugs."

But jokes aside, the fly-brain research is actually fascinating.

Scientists are getting much better at mapping biological brains and creating computational models based on those neural connections.

A fruit fly is obviously very far from a human brain, and we are nowhere near uploading human knowledge or consciousness.

But it does make you wonder…

What happens when we understand the human brain well enough to simulate parts of it?

Maybe one day the biggest competition won't be:

"Who studied the most?"

It'll be:

"Who has the best brain model?" 😂

Until then…

Back to studying. 😭📚

Because unfortunately,

AI train my brain is still not available in Settings.

ng update: Because Peace Was Never an Option 😂

kiran — Wed, 09 Sep 2026 11:43:14 +0000

Angular Version Update Every Year Be Like 😭

Every year

Angular:

“A new version is available! 🚀 Upgrade now.”

Developer:

Nice! Should be easy. Just ng update.”

5 minutes later…

ERESOLVE unable to resolve dependency tree

😐

Developer:

“Okay… let's check the dependencies.”

Then you discover:

Angular needs Node 20
Your project uses Node 18
One package needs Angular 17
Another package only supports Angular 16
Angular Material wants something else
Some random library hasn't been updated since 2022 💀

So you start upgrading one version at a time:

Angular 17 → 18

🔥 23 errors

Angular 18 → 19

🔥 47 errors

Angular 19 → 20

🔥 89 errors

At this point you're not upgrading the project anymore.

You're negotiating with npm.

Then comes the classic:

npm install --legacy-peer-deps — My Emotional Support Command 😂

Developer:

“Problem solved.” 😎

Angular:

“Are you sure about that?”

😂

And after 6 hours of debugging...

ng serve

Finally:

✔ Application bundle generation complete
✔ Local: http://localhost:4200/

Developer:

“YESSSSS! 🎉”

Then the browser opens:

ERROR RuntimeError: NG0203
ERROR NG0955
ERROR NG04002

💀💀💀

And the funniest part?

The application was working perfectly yesterday.

The Angular Developer Annual Cycle 🔄

January:
“I'll keep dependencies updated.”

March:
“It's fine, we'll update later.”

June:
“Don't touch package.json.”

September:
“Angular released a new version.”

October:
“Why did I do this to myself?”

November:
“Everything works again.”

December:
“Next year I'll update regularly.”

Next year:
🔁 Same story.

Angular version update isn't an upgrade.
It's a yearly boss fight. 😂

Angular 22 is here… You already know my first command. 😎

Solstice Protocol: A Puzzle Adventure to Save the Longest Day

kiran — Tue, 23 Jun 2026 10:46:32 +0000

This is a submission for the June Solstice Game Jam

Solstice Protocol is a sci-fi puzzle adventure where players pilot a repair drone through the ancient Helios Solar Facility. A catastrophic system failure is causing daylight to disappear, and unless the facility is repaired before sunset, the world will be plunged into permanent darkness.

Players must explore multiple sectors of the facility and repair corrupted solar nodes while a global Daylight Protocol meter continuously drains. Every puzzle solved restores daylight and brings the system closer to stabilization.

The game combines exploration, problem-solving, cryptography, binary logic, and programming concepts into a single mission inspired by the June Solstice theme of light, darkness, time, and transformation.

Core Features

Real-time daylight countdown system
Multi-sector facility exploration
Logic sequence puzzles
Binary accumulator challenges
Programming debugging puzzles
Turing-inspired cipher decryption challenges
Gemini Oracle hint system
Dynamic victory and failure states
Sci-fi atmosphere and world-building

** Video Demo**

https://youtu.be/4edt1JkrK6E

The video demonstrates:

Drone movement and exploration
Daylight countdown system
Puzzle solving
Gemini Oracle interactions
Sector progression
Solar Core restoration sequence
Final victory sequence

Code

GitHub Repository:

https://github.com/kiranbasnal9876/solstice-protocol-game

Playable Version:

https://kiranbasnal9876.github.io/solstice-protocol-game/

How I Built It

The game was built as a browser-based JavaScript project using a modular scene architecture.

Puzzle Design

The facility contains four different puzzle systems:
Solar Alignment Sequence
Players identify number patterns and predict the next value.
Binary Solar Coupler
Players activate binary switches to match a target decimal value.
Solar Kernel Debugger
Players inspect code snippets and identify logical programming errors.

Turing Enigma Decryptor

Players decrypt encoded words using Caesar-shift cryptography inspired by Alan Turing's work in codebreaking.

Daylight System

A central gameplay mechanic is the Daylight Protocol meter. Daylight continuously drains as the player explores the facility. Successfully repairing nodes restores daylight, creating constant tension and urgency.

Gemini Oracle

The Gemini Oracle acts as the facility's AI assistant. Players can interact with it to receive contextual hints, learn about the facility, and access information about Alan Turing and the Solstice Protocol.

Theme Inspiration

The June Solstice marks the longest day of the year in the Northern Hemisphere. I wanted to transform that concept into gameplay by making daylight itself the resource players must protect.

As the facility fails, daylight fades. Every repaired node becomes a fight to preserve the longest day.

Prize Category

Best Ode to Alan Turing

Alan Turing's influence is woven directly into the gameplay.

The game includes:

Cipher decryption challenges
Binary conversion puzzles
Debugging exercises
Turing Archive lore entries

These mechanics celebrate the foundations of computer science, cryptography, and logical reasoning pioneered by Turing.

Best Google AI Usage

The Gemini Oracle serves as the Helios Facility's onboard AI assistant.

Players can interact with the Oracle to:

Request hints
Learn about facility systems
Explore lore
Discover information about Alan Turing
Receive gameplay assistance

The Oracle was designed as both a gameplay feature and an immersive narrative component.

Final Thoughts

First, I'd like to apologize for submitting close to the deadline. I spent most of my available time polishing the gameplay, puzzles, atmosphere, and overall experience of Solstice Protocol, and I wanted to share the best version I could create.

This project was built with a lot of enthusiasm around the June Solstice theme, combining daylight preservation, puzzle-solving, cryptography, programming concepts, and sci-fi storytelling into a single experience.

I would be very grateful if the judges and community could take a look at the project and provide feedback. As a developer, this challenge was a great opportunity to learn, experiment, and push myself to build something creative from scratch.

If there are any issues with the submission or if I missed any requirement, please let me know. I appreciate your time and consideration, and I hope you enjoy exploring the Helios Solar Facility and helping save the longest day.

Thank you for reviewing Solstice Protocol.