ai, prompts

I’ve been using ChatGPT for a while now, and I want to share my honest perspective on what it is, what it isn’t, and how I think about prompt engineering.

What ChatGPT actually is

ChatGPT is a large language model trained on vast amounts of internet text data using the Transformer architecture. It can generate human-like responses to natural language queries, making conversations feel surprisingly natural. But here’s the thing: it’s not generating new knowledge. It’s reorganizing and presenting what already exists in its training data in a more digestible form.

Each model version has a knowledge cutoff date - the point beyond which it hasn’t seen new information. The specific cutoff varies depending on which model you’re using and when it was trained. This means ChatGPT might not know about recent events, current trends, or information published after its training period. The model also sometimes generates false information or repeats itself. You need to know what accurate and inaccurate information looks like before trusting any generated content.

How I approach prompting

I’ve learned that how you ask matters. A lot.

Instead of treating it like Google with simple queries, I build context through conversation. I might start broad, then narrow down, asking follow-up questions to refine the output. But I’ve also discovered that being specific and directive in a single prompt often works better.

For example, when I need technical writing, I specify the tone, structure, and style I want. I tell it to use evidence, ask transitional questions, write in an academic context, or mimic a particular writing style. I can limit word counts, require specific keywords, or ask it to transition between contexts.

The key is being deliberate about what you want. Prompt engineering is a skill that develops over time through experimentation.

My honest assessment

ChatGPT is a helpful research sidekick, not a replacement for critical thinking. I use it to:

  • Quickly understand unfamiliar topics
  • Generate initial drafts that I heavily edit
  • Explore different perspectives on a subject
  • Save time on routine writing tasks

But I never blindly trust its output. I verify facts, check sources when possible, and apply my own judgment. The convenience is real, but so are the limitations.

At the end of the day, nothing beats human critical thinking. ChatGPT is a tool, and like any tool, its value depends on how skillfully you use it. I focus on what I’m trying to learn and let the tool assist, not replace, my thinking process.

Worth exploring

If you want to dive deeper into prompt engineering, check out this Twitter thread by Rob Lennon. He shares clever techniques for creating prompts that generate more cohesive outputs.

You can start experimenting at chat.openai.com with the free tier.

Well, now what?

You can navigate to more writings from here. Connect with me on LinkedIn for a chat.

  1. 2026

    1. We Might All Be AI Engineers Now
      March 05

      ai, engineering, tools, agents

    2. The Hardest Bug I Ever Fixed Wasn't in Code
      February 07

      engineering, career

    3. Why I Switched to Podman (and Why You Might Too)
      February 02

      docker, tools, linux

  2. 2024

    1. The World is Stochastic
      October 18

      career, philosophy

    2. Debugging a running Java app in Docker
      May 29

      java, docker, debugging

    3. Why is it UTC and not CUT?
      February 21

      time, history

  3. 2023

    1. Deep prop drilling in ReactJS
      December 26

      react, javascript, frontend

    2. Eigenvectors
      October 24

      math, linear-algebra

    3. Java's fork/join framework
      October 21

      java, concurrency

    4. TypeScript's omit and pick
      August 10

      typescript, frontend

    5. JavaScript's new immutable array methods
      June 28

      javascript, frontend

    6. Integrating JUnit 5 in Maven projects
      May 25

      java, testing

    7. My take on ChatGPT and prompt engineering
      March 11

      ai, prompts

    8. Declarative events in ReactJS
      March 09

      react, javascript, frontend

    9. Positive Lookaheads
      March 07

      regex, tools

    10. Functors
      March 06

      functional-programming, math

    11. Fast forward videos with ffmpeg
      January 18

      ffmpeg, tools

    12. Rotate y-axis of a 2D vector
      January 05

      math, vectors

  4. 2022

    1. Synchronizing time
      December 31

      distributed-systems, time

    2. Vector rotation
      November 20

      math, vectors

    3. Sed find and replace
      November 14

      sed, tools, linux

    4. Asgardeo try it application
      September 06

      identity, iam, asgardeo

    5. Flatten error constraints
      August 11

      java, algorithms

    6. Good Git commit messages
      July 24

      git, engineering

    7. Asgardeo JIT user provisioning
      March 09

      identity, iam, asgardeo

    8. Monotonic Arrays
      February 25

      algorithms, javascript

    9. How GOROOT and GOPATH works
      February 01

      go, tooling

  5. 2021

    1. Two summation
      November 21

      algorithms