We\u2019re talking a whole whopping 180 lines of code here, including newlines and comments. ChatGPT is all the hype, so surely it must be able to write this very very simple app, right?<\/p>\n
Let\u2019s dumb it down a bit, forgetting about Docker, the static file server and the Hello there ChatGPT. Could you create a program for me that, every friday at 16 hours selects a random image from a directory and sends it to a Slack channel?<\/p>\n<\/blockquote>\n It created a small Python script with inline configuration for Slack API token and meme directory. And then suggested using Anyway, let\u2019s try it out!<\/p>\n Well, that didn\u2019t quite work:<\/p>\n Uhoh, still using Python 2.7 in 2023, let\u2019s quickly update my The full script:<\/p>\n The main reason I used the WebHook in the first place because, well getting an API to work\u2026<\/p>\n At this point I was a bit at a loss, the channel most surely exists and I added the bot to it. So\u2026 Let\u2019s ask ChatGPT?<\/p>\n What Slack OAuth scopes do I need to upload a file to a channel using the API?<\/p>\n<\/blockquote>\n It gave me some additional scopes but they seemed irrelevant and I indeed got the same error after.<\/p>\n Let\u2019s go back to the WebHook then..<\/p>\n Could you generate code using a Slack Webhook instead?<\/p>\n<\/blockquote>\n Which resulted in code that can actually send a message to Slack. But not with a picture\u2026 It used The program:<\/p>\n It did manage to fix this with an additional prompt!<\/p>\n Could you generate a Slack Webhook payload with text and an image?<\/p>\n<\/blockquote>\n Which generated a working payload:<\/p>\n Progress!! \ud83c\udf89<\/p>\n Can you create a docker-compose with a service that executes a Python script with a cron job and a static file server service?<\/p>\n<\/blockquote>\n This created<\/p>\n It was time to integrate the two solutions. Some manual fixes and additional prompts later, it had generated something that seemed like it would work.<\/p>\n Could you replace the python-script.py with the one you generated earlier?<\/p>\n<\/blockquote>\n Can we bring this all together? You didn\u2019t include the Python script\u2026 However it did not actually run the cron job\u2026 No logs to be found, it just sat there.<\/p>\n Here it seemed I either ran against the limits of ChatGPT or against the limitations of my \u201cAI Prompt Engineering\u201d-skillz.<\/p>\n I then tried for over an hour to get ChatGPT to create a docker-compose that prints \u201cHello World\u201d.<\/p>\n Let\u2019s try again: Can you create a docker-compose that schedules a cron job to print \u201cHello World\u201d every minute?<\/p>\n<\/blockquote>\n Some of the things it tried:<\/p>\n At this point I was just copy pasting the code and nothing worked.<\/p>\n Do you think that if I keep asking changes that at some point it will actually work?<\/p>\n<\/blockquote>\n \u2026 While I do my best to understand and assist with your requests, troubleshooting specific technical issues can be challenging without having direct access to your environment. \u2026<\/em><\/p>\n And here is me, thinking that the entire philosophy of Docker is to not be dependent on the developer environment. Oh and I\u2019m also asking for a freaking \u201cHello World\u201d app here\u2026<\/p>\n ChatGPT pretty much gave up after a while and shifted into troubleshooting mode.<\/p>\n It came up with some interesting suggestions, most of which I had already tried at that point.<\/p>\n It is a gadget, nothing more.<\/p>\n I felt like I was asking questions to a junior developer who copy pasted code from somewhere and handed it over without any testing. Everything it does needs to be reviewed thoroughly. To me, it doesn\u2019t seem like it can be used for much more than generating some skeleton code, saving you a few keystrokes.<\/p>\n During technical interviews, I sometimes come across what I call a \u201cTrial & Error\u201d-programmer: They try something and then run the code, check if the result is correct and if it is not, they try something different. Rinse and repeat.<\/p>\n I hope that ChatGPT and the like are not raising a generation of Trial & Error programmers because that is exactly how I am feeling after copy pasting code for a few hours and making small adjustments here and there.<\/p>\n I quit this exercise the moment it spewed out the following:<\/p>\n Is it a good idea to do that?<\/p>\n<\/blockquote>\n You raise a valid concern. Using an infinite loop with a sleep statement in the main script might not be the most efficient approach, as it can consume unnecessary resources.<\/em><\/p>\n After which it generated code without scheduling \ud83d\ude03<\/p>\n \u201cIndeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. \u2026[Therefore,] making it easy to read makes it easier to write.\u201d \u2015 Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship<\/p>\n<\/blockquote>\n Or how about this one:<\/p>\n \u201cDebugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.\u201d – Brian W<\/p>\n<\/blockquote>\n ChatGPT is not helping you by generating code you do not understand, it is just making debugging and future feature development that much harder, if it succeeded in producing something that works.<\/p>\n If you already know how to code and want to have 80% of your code generated for you, you may want to have a look at using ChatGPT. Just remember that:<\/p>\n One thing that did impress me was that after I told it a few times \u201cNope, also doesn\u2019t work\u201d, it gave some pretty good recommendations on how to debug and troubleshoot its (broken) solutions.<\/p>\n It seems to be quite good at solving really small very well known problems. I always forget the exact syntax for From ChatGPT itself:<\/p>\n Programming requires creativity, problem-solving skills, and a deep understanding of various technologies. While I can offer guidance, suggestions, and code examples, it\u2019s important to remember that human programmers bring their unique expertise, experience, and insights to the table. The human element is crucial in the programming process, and no AI can replicate the entirety of human skills and knowledge.<\/em><\/p>\n Please consider me as a tool that can assist you in your programming journey, providing information, ideas, and helping with specific tasks.<\/strong>However, the ingenuity and skill of human programmers remain essential for developing robust and innovative solutions.<\/em><\/p>\n If you have any further questions or need assistance with any programming topic, feel free to ask. I\u2019m here to help in any way I can!<\/em><\/p>\n It was unable to tell me if that response was hardcoded or not.<\/p>\n I\u2019m disappointed, for sure. It created a working Python script quite fast which got my hopes up, but then it failed at what is typically the hardest part anyway: integration.<\/p>\n I will be using this to generate small things on the side. Like my Bash skills are below par, I\u2019m sure ChatGPT can give me something that already mostly works.<\/p>\n Oh man, I feel old, bitter and out of touch now.<\/p>\nalready-sent<\/code> folder for now.<\/p>\n\n
cron<\/code> or Task Scheduler<\/code> for the friday 16h part. That\u2019s actually a good idea, I should add Windows instructions to the installation blog post for non-Docker usage \ud83d\ude03<\/p>\npip install slack-sdk\npython 1-InitialPrompt.py\n<\/code><\/pre>\n File \".1-InitialPrompt.py\", line 26\n print(f\"Image sent to Slack channel '{channel}' successfully!\")\n ^\nSyntaxError: invalid syntax\n<\/code><\/pre>\n$env:PATH<\/code>.<\/p>\nimport os\nimport random\nimport glob\nfrom slack_sdk import WebClient\nfrom slack_sdk.errors import SlackApiError\n\nSLACK_API_TOKEN = \"<your-slack-api-token>\"\nIMAGE_DIRECTORY = \"\/path\/to\/your\/image\/directory\"\nslack_channel = \"#your-channel-name\"\n\nslack_client = WebClient(token=SLACK_API_TOKEN)\n\ndef send_image_to_slack(channel, file_path):\n try:\n response = slack_client.files_upload(\n channels=channel,\n file=file_path,\n title=\"Random Image\",\n )\n print(f\"Image sent to Slack channel '{channel}' successfully!\")\n except SlackApiError as e:\n print(f\"Failed to send image to Slack channel '{channel}': {e.response['error']}\")\n\n\nimage_files = glob.glob(os.path.join(IMAGE_DIRECTORY, \"*.jpg\"))\nrandom_image = random.choice(image_files)\nsend_image_to_slack(slack_channel, random_image)\n<\/code><\/pre>\n\n
slack_client.files_upload<\/code> to _v2<\/code> with single channel<\/li>\n\n
xapp<\/code> tokens vs xoxp<\/code> and xoxb<\/code> etc<\/li>\nfiles:write<\/code>, \u2026<\/li>\n\/invite @MemeBot<\/code> did not solve this nor did chat:write.public<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n
WebHook Prompt<\/h1>\n
\n
attachments: []<\/code> but that doesn\u2019t actually work. Even if it did, you would still need something to serve the files\u2026<\/p>\nimport os\nimport random\nimport glob\nimport requests\n\nSLACK_WEBHOOK_URL = \"https:\/\/hooks.slack.com\/services\/...\"\nIMAGE_DIRECTORY = \".\/memes\"\n\ndef send_image_to_slack(webhook_url, file_path):\n try:\n payload = {\n \"text\": \"Random Image\",\n \"attachments\": [\n {\n \"image_url\": file_path\n }\n ]\n }\n response = requests.post(webhook_url, json=payload)\n response.raise_for_status()\n print(f\"Image sent to Slack successfully!\")\n except requests.exceptions.RequestException as e:\n print(f\"Failed to send image to Slack: {str(e)}\")\n\nimage_files = glob.glob(os.path.join(IMAGE_DIRECTORY, \"*.jpg\"))\nrandom_image = random.choice(image_files)\n\nsend_image_to_slack(SLACK_WEBHOOK_URL, random_image)\n<\/code><\/pre>\n\n
payload = {\n \"text\": \"Random Image\",\n \"attachments\": [\n {\n \"fallback\": \"Image\",\n \"image_url\": file_path\n }\n ]\n}\n<\/code><\/pre>\nFile Server<\/h1>\n
\n
\n
docker-compose.yml<\/code>: Used nginx to create a working static file server<\/li>\nDockerfile<\/code>: Took a different approach to what I ended up with<\/li>\ncronjob<\/code>: It even remembered I wanted to run this on fridays at 16h!<\/li>\n<\/ul>\n\n
\n
A docker-compose that schedules a cron job that selects a random image from a mounted volume and sends the url as served by an nginx service to Slack using a webhook?<\/p>\n<\/blockquote>\n\n
This does not use the docker-compose variables you used in your earlier answer
The dockerfile should do a pip install of requests<\/p>\n<\/blockquote>\nBacktrack: Hello World<\/h2>\n
\n
\n
crontab<\/code> file with echo<\/code><\/li>\ndocker-compose<\/code> with Command<\/code><\/li>\nstartup.sh<\/code> to print Hello World instead<\/li>\nvixiecron<\/code> package<\/li>\n<\/ul>\nBeing Sassy<\/h2>\n
\n
Troubleshooting<\/h1>\n
docker logs <container_id_or_name>\n\ndocker exec -it <container_id_or_name> sh\npython \/app\/python-script.py\ncat \/etc\/cron.d\/cronjob\nservice cron status\ncat \/var\/log\/syslog\n<\/code><\/pre>\nConclusion<\/h1>\n
The Horror<\/h2>\n
while True:\n schedule.run_pending()\n time.sleep(1)\n<\/code><\/pre>\n\n
Reading vs Writing<\/h3>\n
\n
\n
The Good<\/h2>\n
\n
docker exec<\/code>. A simple prompt gave me a correct copy-pastable answer! That is to be expected considering how it works beneath the hood I guess.<\/p>\nIntrospection<\/h2>\n
Final Thoughts<\/h2>\n
Also in this series<\/h1>\n