ChatGPT Prompting for Architects and Executives

Introduction

In chapter six of Lewis Carroll’s “Alice’s Adventures in Wonderland,” under a section, titled “Pig and Pepper.”, the following dialogue plays out:

Alice: Would you tell me, please, which way I ought to go from here?
The Cheshire Cat: That depends a good deal on where you want to get to.
Alice: I don’t much care where.
The Cheshire Cat: Then it doesn’t matter which way you go.

There is a lesson here for interacting with emerging machine interfaces of Large Language Models (LLM) and Generative Artificial Intelligence (Gen-AI) like ChatGPT. The way we interact with computers has evolved dramatically in the last decade, to the point where one can begin to conceive of Alice’s conversation with the Cheshire cat. However, much as it was with the Cheshire cat, you still need to know where you want to go in order to benefit from directions.

Let’s imagine that you are looking for information about the topography of Berlin, Germany, and not the whole of Europe. Well, it helps to know that your target lies somewhere between Russia, the North Sea, the Mediterranean and Lebanon (context), since there is another Berlin in Ohio (US). It is useful to understand that the focus is geographical rather than political (role), that the message is in a form suited for delivery at the UN rather than the Republican conference (tone), and the format is as a speech rather than a manifesto (format). These foundations are effective for all ChatGPT interactions, whether you’re an IT architect navigating complex technical issues or a C-Suite executive seeking strategic insights.

There are many comprehensive blogs, articles, books and other materials you can read about writing effective prompts. I find that many are quite technical, and they cover details and scenarios that most folks will never need, in work, or everyday life. What I have done is to simplify things and give you the bare essentials. A simple formula that gives you the maximum revenue-to-investment ratio. The acronym CRAFT spells out: Context, Role, Action/question, Format and Tone. These are the fundamental components of every ChatGPT prompt. By applying these to your prompts, you will get much better results, and useful feedback for improving future prompts.

Context

Context is the backstory to your dialogue; it gives depth to your prompt. It provides the AI with the necessary background information to better understand your query fully. For example, if your question is about technology threats and trends, the prompt could start like this: “In the rapidly evolving tech industry, where startups are disrupting traditional players…”

Role

Here is the best way to think of the role. Think; in real life, who would I prefer to answer this question: a lawyer, plumber, dietician, legislator, soldier? The role instructs the machine on the overall nature and perspective of the response, including any inherent biases. For instance, if you’re a COO architect seeking technical insight, your prompt, continuing from the Context example above, might be of the form: “you are an experienced Cloud infrastructure expert, with several certifications and hands-on experience of Azure …”.

Action/Question

Instructions in a ChatGPT prompt are the most important component. They need to be clear, concise, and unambiguous. Brevity might be an asset here, the clearer your instructions, the more accurate and relevant the AI’s response. A compatible question to the example given in the Context could be: “what are the emerging cybersecurity threats for Azure IaaS in 2023?”

Format

This determines the presentation of the output/response of ChatGPT. It could be a detailed analysis, a concise summary, a table, bullet points, a step-by-step guide, or a combination of things? Use simple language to tell the AI how to deliver the information in a way that suits your purposes. Once again, using our example from the Context, the format could be: “a short summary with bullet points of the 5 most significant concerns”.

Tone

The tone of your prompt sets the mood for the conversation. If you were to advise the role how best to engage with the target audience; would it be technical, formal, humorous, conversational, expert, witness, informative, urgent, casual, professional, legalistic, etc. It could also be a combination, for example professional+humorous. Extending our Context example, the tone could be: “speaking with an informative tone”, since the COO does not intend to mask their unfamiliarity with the subject.

Extra Tips

  • Use simple and precise language; imagine that you are conversing with a 10-year-old Einstein.
  • Evolve the prompt, changing the keywords you use for tone and format, in order to get an output that suits your purpose.
  • Always leave the action/question till last, as it can help reduce verbosity and improve accuracy of the output.

Conclusion and Credits

In the ever-evolving landscape of AI, mastering the art of ChatGPT prompting is a skill that can elevate your interactions with technology. IT architects can it to seek solutions to complex technical challenges, while C-Suite executives can extract strategic insights for decision-making. From general technical information to specific market analysis and research, the applications are limitless. I am convinced that we are entering a new age of man-machine relationship, and those that learn and adapt will reap significant benefits in the future.


PS: I used an approach called “Generative Knowledge” to elicit an outline and the initial draft for this article. I had to refine the prompt a few times to get things right. The final LLM output benefited from some massaging, but all-in, it saved me a lot of time, and I hope that I managed to impart some useful information to you.

Advanced PayPal Checkout Simplified

If you have an eCommerce site that is growing, you may have noticed that some recurring expenditure is also growing. One such is the cost of transactions, in this case, commissions or transaction charges on sales. The costs are very similar, whether you are using PayPal, Stripe, Flutterwave or some other payment gateway.

The bad news is that you cannot (easily) cut out payment gateways, they are a bit like taxes. 🙁 The good news is that you can reduce the amount you shell out per transaction. One option is to integrate with the payment gateway directly, rather than using a third party product.

Third party products are great, especially the free ones. However, as we all know, there is no free lunch. While they get you off the ground quickly, the convenience has a cost attached: higher per-transaction costs. After a while, and as your sales volumes increase, those pennies add up. Furthermore, these products often impose significant constraints on how the products and the shopping cart are displayed on screen.

Sooner or later, you get to the point where you may want to go ‘pro’ for greater artistic freedom, to gain access to premium features, or to reduce the transaction charges. But ‘pro’ versions can be quite pricey for small-holders or those running a side-hustle. Almost all are subscription based, and the fees are paid annually, in advance. In essence, you pay upfront, whether you make money or not.

I had the same challenge, and decided to have a look at what it would take to integrate directly with PayPal. For me, the motivations were costs and design freedom. It took a while, but that was because I started off reading the PayPal docs, which, in my opinion, could have been better written. However, I soon found alternative resources on the web that made the process clear and simple.

Using those sources, I have created a repository with a simple, customisable shopping cart that integrates with PayPal. Why create a shopping cart, aren’t there tons of those already out there? Well, all the ones I saw were integrated with eCommerce platforms such as WooCommerce, EDD, etc., which meant that you need to install at least one other plugin to get the cart working. I wanted something generic, independent and simple, with all the skeleton visible and tweakable. It is now ready, and available to the public, gratis, on GitHub.

With a few minor edits (URLs and PayPal client Id), you can get this solution working in minutes. I have used plain and simple JavaScript, HTML and CSS, making it very easy to customise the functionality or redesign the visuals. Click on the GitHub link below to view the repo, read the description, take a copy and see how quickly and easily you can be up and running. If you would like a WordPress plugin to make things even easier, give me a ping.

https://github.com/LanreOyewole/PayPalIntegration/tree/main