Winstep

Software Technologies


 Winstep Forums


Print view
Board index : Winstep Forums : Articles  [ 3 posts ]
Author Message
 Post subject: Using AI Without Losing your Soul: A Developer’s Perspective
PostPosted: Sun Jul 19, 2026 7:58 am 
Offline
Site Admin
Site Admin
User avatar

Joined: Thu Feb 26, 2004 8:30 pm
Posts: 13188
AI has a terrible reputation right now - and honestly, it earned most of it.

“AI slop” is everywhere: lazy content, soulless graphics, and half-baked text churned out by people who think a machine can replace actual work.

But that is not what AI is, and certainly not how I use it.

In the Winstep workflow, AI is the idiot-savant junior assistant I never had: brilliant at grunt work, hopeless at originality, frequently wrong, but absolutely transformative when properly directed.

Used the wrong way, AI produces garbage. Used the right way, it multiplies human productivity in ways that were simply impossible a few years ago.

I have never been this productive before.

AI has helped me with everything from gathering and verifying latitude and longitude coordinates for more than 70,000 cities, to modifying PHP code for the Winstep forums, revising the User Guide, researching unfamiliar technical issues, catching mistakes in new code, and producing graphics I could never have created myself.

These are all tasks I would previously have dreaded, postponed indefinitely, or never attempted at all. Now they simply get done.

The actual creative decisions, design, logic, implementation, and vision still come from me. AI cannot do those things for me. It can only help me reach the result faster.

In my case, and given the way I use it, the benefits of AI far outweigh the costs and the privacy concerns I may have. And, frankly, if one has privacy concerns, we already sold our soul to the devil - Microsoft - just by running Windows.

I use AI like any other tool, but perhaps more accurately as the junior assistant I never had.

Pretty much in the same way we have been using Google and other search engines for years to search for the information we want and filter out the rest. This is where the AI truly excels, and is a thousand times better than any search engine.

It cannot do what I do, but it can often point me in the right direction. Like a human assistant, I can also burden it with tedious jobs that would otherwise take me ages - assuming I ever found the motivation to begin them.

Take the latitude and longitude coordinates added in version 26.6. How long would it have taken me to gather coordinates for more than 70,000 cities, match them, and verify that they were correct, even with a script to help automate the process?

Realistically, I probably would never even have started. My time is valuable and better spent on work that requires my direct attention.

The User Guide is another example. Revising it is already a tedious and mammoth task, even after AI produced a starting point. It took around twenty supervised revisions before I had something I could properly begin reviewing myself. Without that initial assistance, I would probably have given up before getting anywhere near that stage.

With the AI I am no longer afraid to tackle issues I know nothing or very little about - I know it will help me "zero in" on the stuff that really matters, and on how to get the job done. Adding Dark Mode to the forums is another example - not only do I not know PHP, as I probably would have been too afraid to break the forums to even attempt to tackle it on my own.

Graphics are another obvious case. “AI slop” or not, the results still beat anything I could have produced on my own. I am a developer, not a graphic artist. More importantly, graphics work is something I would have absolutely dreaded doing, assuming I could have done it at all.

AI does not turn me into an artist, but it allows me to direct the creation of something useful, reject what does not work, refine what does, and reach a result that would otherwise have been beyond me.

Properly directed, AI lets me offload grunt work, brainstorm ideas, perform research, generate graphics, compare approaches, and inspect code.

In much the same way computers increased the speed of calculations by several orders of magnitude, AI can dramatically increase productivity in certain kinds of work. The important distinction is that the final judgment must remain human.

The absolutely wrong way to use AI in software development is to let it generate code you do not understand.

I have a friend, who shall remain unnamed, who does exactly that. If something goes wrong with the code, without AI he will not even know where to begin fixing it. What he does not understand is that even with AI, there is no magic potion that instantly identifies and repairs every bug.

Where AI often excels is in catching obvious mistakes that are easy for a human developer to overlook: a variable name that was not changed after copying and pasting a block of code, an incorrect condition, an unhandled edge case, or a mismatch between two related sections. For this kind of work, AI can be fantastic.

But when I have used it to help track down particularly difficult issues, its suggestions have often amounted to educated trial and error. Many times, after a long debugging session, I was the one who eventually pointed the AI toward the actual problem. No joke. No exaggeration.

Most importantly, you must understand that AI can and will sometimes lie to you when it does not know the answer, rather than simply admitting that it does not know jack about the subject - with the confidence and absolute certainty of a pathological liar. My solution to this is run the code or reasoning through different AIs - ChatGPT, CoPilot, Gemini - and let them battle it out when they disagree.

My approach is therefore very different from blindly accepting generated code. I use AI to help me determine what is needed to tackle a specific job and to point me toward relevant techniques, APIs, documentation, or possible causes.

That is not fundamentally different from digging through the web for information and then applying what you find. It is simply much faster and more interactive.

The second part is the most important: I make sure I understand how the suggested approach works and what it actually does. AI provides the scaffolding. The structure, logic, decisions, implementation, testing, and final responsibility remain entirely mine.

Ironically, AI has also indirectly made the latest Winstep releases a little less stable than usual.

Not because I am inserting sloppy AI-generated code into the applications - I am not - but because AI has allowed me to make a truly massive number of additions, changes, and improvements in a very short period of time.

A good example is the complete overhaul of the weather system, replacing the old weather.com location codes with latitude and longitude coordinates. This required enormous changes to the underlying logic, but it was worth doing because it allowed me to vastly improve how the whole system works and to add two backup weather feeds..

Previously, if the MSN weather feed failed for any reason, the weather module would have simply stopped working.

These changes also prepare the applications for much larger features that were never part of the original plan but should greatly improve what they can do.

The problem is that changing old code is often much riskier than writing new code.

Mature code contains invisible assumptions that even the original developer may no longer remember. Over time, it accumulates side effects, workarounds, dependencies, and historical quirks. A small change in one module can unexpectedly affect something elsewhere in the application - this happens all the time.

You may only discover the problem days later, when a user reports a bizarre issue that appears completely unrelated to the original change. That issue may never have appeared during testing because the user has a different configuration, monitor layout, Windows version, language, theme, or combination of settings. It is simply impossible to retest every possible configuration after every release.

New code has its own bugs, of course, but changes to old, heavily interconnected code can produce especially unpredictable regressions because so much existing behavior already depends on it.

So yes, the faster pace of development enabled by AI has had a cost. On the other hand, the ends justify the means. I am actually running out of things on my long-standing to-do list.

It is just that, as Patrick Swayze said in Road House, “it will get worse before it gets better.”

There are, of course, very real concerns surrounding AI beyond the obvious privacy issues. Humans may become so dependent on it that they stop learning, stop questioning, or stop making decisions for themselves. Used carelessly, AI can weaken judgment rather than strengthen it, turning people into the perfect slave so many tyrants can only dream of.

But that is a much larger discussion for another time. Like any powerful tool, AI can be used intelligently or irresponsibly. It can amplify laziness, incompetence, and dishonesty, or it can amplify skill, curiosity, and productivity.

The way I use it is benefiting both me and every Winstep user in ways that would have been simply impossible only a handful of years ago.

AI does not replace what I do. It allows me to do far more of it.

_________________
Jorge Coelho
Winstep Xtreme - Xtreme Power!
https://www.winstep.net - Winstep Software Technologies


Back to top
 Profile WWW 
 
 Post subject: Re: Using AI Without Losing your Soul: A Developer’s Perspec
PostPosted: Mon Jul 20, 2026 3:00 am 
Offline
Global Moderator
Global Moderator

Joined: Sat Apr 07, 2018 7:19 pm
Posts: 3316
Location: Nowhere Land
winstep wrote:
AI has a terrible reputation right now - and honestly, it earned most of it.

“AI slop” is everywhere: lazy content, soulless graphics, and half-baked text churned out by people who think a machine can replace actual work.

But that is not what AI is, and certainly not how I use it.

In the Winstep workflow, AI is the idiot-savant junior assistant I never had: brilliant at grunt work, hopeless at originality, frequently wrong, but absolutely transformative when properly directed.

Used the wrong way, AI produces garbage. Used the right way, it multiplies human productivity in ways that were simply impossible a few years ago.

I have never been this productive before.

AI has helped me with everything from gathering and verifying latitude and longitude coordinates for more than 70,000 cities, to modifying PHP code for the Winstep forums, revising the User Guide, researching unfamiliar technical issues, catching mistakes in new code, and producing graphics I could never have created myself.

These are all tasks I would previously have dreaded, postponed indefinitely, or never attempted at all. Now they simply get done.

The actual creative decisions, design, logic, implementation, and vision still come from me. AI cannot do those things for me. It can only help me reach the result faster.

In my case, and given the way I use it, the benefits of AI far outweigh the costs and the privacy concerns I may have. And, frankly, if one has privacy concerns, we already sold our soul to the devil - Microsoft - just by running Windows.

I use AI like any other tool, but perhaps more accurately as the junior assistant I never had.

Pretty much in the same way we have been using Google and other search engines for years to search for the information we want and filter out the rest. This is where the AI truly excels, and is a thousand times better than any search engine.

It cannot do what I do, but it can often point me in the right direction. Like a human assistant, I can also burden it with tedious jobs that would otherwise take me ages - assuming I ever found the motivation to begin them.

Take the latitude and longitude coordinates added in version 26.6. How long would it have taken me to gather coordinates for more than 70,000 cities, match them, and verify that they were correct, even with a script to help automate the process?

Realistically, I probably would never even have started. My time is valuable and better spent on work that requires my direct attention.

The User Guide is another example. Revising it is already a tedious and mammoth task, even after AI produced a starting point. It took around twenty supervised revisions before I had something I could properly begin reviewing myself. Without that initial assistance, I would probably have given up before getting anywhere near that stage.

With the AI I am no longer afraid to tackle issues I know nothing or very little about - I know it will help me "zero in" on the stuff that really matters, and on how to get the job done. Adding Dark Mode to the forums is another example - not only do I not know PHP, as I probably would have been too afraid to break the forums to even attempt to tackle it on my own.

Graphics are another obvious case. “AI slop” or not, the results still beat anything I could have produced on my own. I am a developer, not a graphic artist. More importantly, graphics work is something I would have absolutely dreaded doing, assuming I could have done it at all.

AI does not turn me into an artist, but it allows me to direct the creation of something useful, reject what does not work, refine what does, and reach a result that would otherwise have been beyond me.

Properly directed, AI lets me offload grunt work, brainstorm ideas, perform research, generate graphics, compare approaches, and inspect code.

In much the same way computers increased the speed of calculations by several orders of magnitude, AI can dramatically increase productivity in certain kinds of work. The important distinction is that the final judgment must remain human.

The absolutely wrong way to use AI in software development is to let it generate code you do not understand.

I have a friend, who shall remain unnamed, who does exactly that. If something goes wrong with the code, without AI he will not even know where to begin fixing it. What he does not understand is that even with AI, there is no magic potion that instantly identifies and repairs every bug.

Where AI often excels is in catching obvious mistakes that are easy for a human developer to overlook: a variable name that was not changed after copying and pasting a block of code, an incorrect condition, an unhandled edge case, or a mismatch between two related sections. For this kind of work, AI can be fantastic.

But when I have used it to help track down particularly difficult issues, its suggestions have often amounted to educated trial and error. Many times, after a long debugging session, I was the one who eventually pointed the AI toward the actual problem. No joke. No exaggeration.

Most importantly, you must understand that AI can and will sometimes lie to you when it does not know the answer, rather than simply admitting that it does not know jack about the subject - with the confidence and absolute certainty of a pathological liar. My solution to this is run the code or reasoning through different AIs - ChatGPT, CoPilot, Gemini - and let them battle it out when they disagree.

My approach is therefore very different from blindly accepting generated code. I use AI to help me determine what is needed to tackle a specific job and to point me toward relevant techniques, APIs, documentation, or possible causes.

That is not fundamentally different from digging through the web for information and then applying what you find. It is simply much faster and more interactive.

The second part is the most important: I make sure I understand how the suggested approach works and what it actually does. AI provides the scaffolding. The structure, logic, decisions, implementation, testing, and final responsibility remain entirely mine.

Ironically, AI has also indirectly made the latest Winstep releases a little less stable than usual.

Not because I am inserting sloppy AI-generated code into the applications - I am not - but because AI has allowed me to make a truly massive number of additions, changes, and improvements in a very short period of time.

A good example is the complete overhaul of the weather system, replacing the old weather.com location codes with latitude and longitude coordinates. This required enormous changes to the underlying logic, but it was worth doing because it allowed me to vastly improve how the whole system works and to add two backup weather feeds..

Previously, if the MSN weather feed failed for any reason, the weather module would have simply stopped working.

These changes also prepare the applications for much larger features that were never part of the original plan but should greatly improve what they can do.

The problem is that changing old code is often much riskier than writing new code.

Mature code contains invisible assumptions that even the original developer may no longer remember. Over time, it accumulates side effects, workarounds, dependencies, and historical quirks. A small change in one module can unexpectedly affect something elsewhere in the application - this happens all the time.

You may only discover the problem days later, when a user reports a bizarre issue that appears completely unrelated to the original change. That issue may never have appeared during testing because the user has a different configuration, monitor layout, Windows version, language, theme, or combination of settings. It is simply impossible to retest every possible configuration after every release.

New code has its own bugs, of course, but changes to old, heavily interconnected code can produce especially unpredictable regressions because so much existing behavior already depends on it.

So yes, the faster pace of development enabled by AI has had a cost. On the other hand, the ends justify the means. I am actually running out of things on my long-standing to-do list.

It is just that, as Patrick Swayze said in Road House, “it will get worse before it gets better.”

There are, of course, very real concerns surrounding AI beyond the obvious privacy issues. Humans may become so dependent on it that they stop learning, stop questioning, or stop making decisions for themselves. Used carelessly, AI can weaken judgment rather than strengthen it, turning people into the perfect slave so many tyrants can only dream of.

But that is a much larger discussion for another time. Like any powerful tool, AI can be used intelligently or irresponsibly. It can amplify laziness, incompetence, and dishonesty, or it can amplify skill, curiosity, and productivity.

The way I use it is benefiting both me and every Winstep user in ways that would have been simply impossible only a handful of years ago.

AI does not replace what I do. It allows me to do far more of it.

Nobody with half a functional brain would dispute your various points above in respect of productivity etc. Jorge. I use AI - or, as I prefer to call it, AS, Artificial Stupidity - extensively myself, albeit none of the Big Tech ones but rather, an excellent 100% private and secure one that does not rob my data in any kind of way, which is Proton's Lumo AI Assistant. Being open source, everything is independently audited so I know there's no nonsense going on.

And there's the rub - privacy and security. If you think you gave it all away just by using Windows, think again. Windows can fairly easily made secure and privacy-obedient - I've been doing that ever since XP days! MS only ever got minimal data out of me, and none that would have been personally identifiable. With Win 10 all that became a lot easier of course, and the range of security and privacy software has expanded enormously over the last decade or so. Also, it's never too late to start to protect one's online privacy and security. Once the data harvest is stopped, the previous data becomes old hat and no longer of any great use "out there".

By not protecting one's privacy and security, one makes the Big Tech multi-billionaires richer still and undermines freedom and democracy. Giving away one's data is in effect making oneself a serf. Because make no mistake, these lunatics really are evil. With money comes power, with infinite money comes infinite power, absolute power. And as per the old adage, power corrupts and absolute power corrupts absolutely. We are just a hair's width away from a totalitarian society in which people without vast fortunes don't count for anything, literally. And giving away one's data, one's privacy and security is making it all possible. Data are the new oil - a financial goldmine, a mint even. The average individual internet user's data were worth app. US$600 per year a couple of years ago, today that figure most likely well exceeds US$1000, given the vastly increased data available for harvesting. Thus, the typical user freely gives away US$1000 or more - for no return, other than endangering freedom and democracy and enriching Big Tech oligarchs. You're giving money to the hyper-rich! You're no so much losing your soul as giving it away.

_________________
nexter - so, what's next?


"Quomodo finietur?" "In igne, glacie, fame, et morte."

"How will it end?" "In fire, ice, famine, and death!"


Back to top
 Profile  
 
 Post subject: Re: Using AI Without Losing your Soul: A Developer’s Perspec
PostPosted: Mon Jul 20, 2026 2:40 pm 
Offline
User avatar

Joined: Wed Jun 24, 2026 7:47 pm
Posts: 10
There is a saying: it is better to be rich and healthy than poor and sick! Unfortunately, this is relevant at all times!


Back to top
 Profile  
 
Post new topic Reply to topic Board index : Winstep Forums : Articles  [ 3 posts ]
Display posts from previous:  Sort by  

Who is online

Users browsing this forum: No registered users and 24 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: