🧠 I No Longer See Software as “Just Software”

Source: Dev.to

Changing perspective

I used to measure good software by how fast it runs, how clean the UI looks, and how many users it serves.
After working on topics like GNSS‑based traffic modeling and green software engineering, my focus shifted. I started asking different questions:

• How much energy does this system consume?
• What invisible resources are being wasted?
• Who is affected by the decisions we make in code?

That’s when software stopped being “just software” to me.

Impact of software

• Traffic modeling – you’re not just optimizing routes; you’re influencing pollution, travel time, safety, and city behavior.
• Energy‑focused analysis – you’re not just profiling code; you’re touching sustainability, infrastructure load, and environmental impact.

Code doesn’t stay on the screen. Every design choice has a cost:

• One inefficient loop multiplied by millions of users
• One always‑on service running 24/7
• One poorly planned system scaled too fast

Software engineers are now part of global systems, not isolated applications. Whether we notice it or not, we are shaping:

• Energy consumption
• Digital behavior
• Economic decisions
• Environmental outcomes

What changed for me

Previously I focused on:

• “Does it work?”
• “Is it fast?”

Now I also consider:

• “Is it responsible?”
• “Is it efficient beyond performance?”
• “Is it solving the right problem?”

Software engineering is no longer just about building products; it’s about designing systems that live inside the real world. Once you truly see that, you can’t unsee it.

Closing thoughts

What questions do you have about responsible software? Drop a thought below — I’d love to hear your take.

You can find me on GitHub:

Original article published on CoderLegion: