The First Time I Swore at GPT (#3)


๐Ÿ˜‡ The Elegant Intellectual… Not Quite


For 30-something years, I’ve prided myself on being a graceful, intelligent person.
And even though ChatGPT isn’t a human, I thought of it as my development partner—so I tried to speak politely.


Well… that didn’t last long.


๐Ÿฅ‡ First Test of Patience – The Vanishing Scorecard Data


I’d save my scores, ball flights, and putts with care… only to open the “Previous Rounds” screen and find them all gone.
Only the total score survived.


GPT: “Maybe you didn’t enter the values?”
Me: “If I didn’t, why are the score and course name showing on the main screen?”


GPT promised to fix it.
After the “fix,” I saved multiple rounds—only the last round’s data appeared.


Complaint. Another “fix.” Still broken. Another "fix". No.. still not working.

I complain again, Why do you keep insisting it works when it doesn’t?”


…Then suddenly, it worked.

Two hours for the first crisis.


๐Ÿฅˆ Second Test of Patience – The Basic Scorecard


I had a simple PPT mock-up for a scorecard (cute, if I may say so—as it was just for my own use).
When I entered a score, the value was supposed to appear in the right spot.


Instead, it was way down at the bottom of the page.


GPT swore the position was correct. I disagreed.
So I entered → previewed → entered → previewed,
moving the value’s position 1 pixel at a time in every direction like some unpaid intern.


“Wasn’t the whole point of using you to make life easier? Why am I doing all the grunt work?”


Eventually, I got it right. (At the cost of another two hours.)




๐Ÿฅ‰ Third Test of Patience – The Detailed Scorecard


All I wanted was to add two more lines to show driver flight and putts.
Instead… the app started crashing. Red error screens everywhere.


Turns out I had stuffed too many features into a single file:

  • Score checking
  • Sorting by date/score
  • Saving detailed or basic scorecards to PDF
  • Exporting multiple PDFs at once
  • Deleting rounds

Everything was tangled. Fixing one part broke another. GPT would patch one problem only for errors to pop up somewhere else.
I started worrying I’d lose all my previous work.

That’s when I hit my limit… and swore at GPT for the first time.


“You absolute dumbass GPT!!!!!!!”


GPT promptly flagged it as “offensive language.” I felt unfairly accused.


It flagged my conversation as "offensive" 

So objected. If I don’t understand something, I’ll question it—whether it’s alive or not.


๐Ÿ™ƒ They say “three acts of patience can spare you from murder.”


But GPT isn’t human—so maybe that’s why it tested my limits this way.


In the end, it did work.
But This was just the preview version in Expo, mind you—when I actually tried to build the app again, all hell broke loose.


But for that moment, seeing my tiny, modest scorecard with numbers neatly in place…
I was genuinely satisfied.


My modest, wholesome scorecard


If the story ended here, it would’ve been a small, wholesome happy ending.


It didn’t.



Comments

Popular posts from this blog

์•ฑ ๊ฐœ์ธ์ •๋ณด ์ฒ˜๋ฆฌ๋ฐฉ์นจ / App Privacy Policy

Building an App – How a Saipan Golf Trip Started It All (#1)

Why K-Caddies are Bad for You ⛳