We used to boot a computer and even a modem and be actually productive and enjoy life without checking for news, notifications, or email every 15 minutes.
Sans version control conflicture crap due to using Git-ware conflict-friendly patterns?
We used to just work together on code and discuss code, without focusing on the version control tooling.
Sans CI/CD tools to validate your work?
We used to validate our work before committing, in the old days.
Sans markdown?
We used to be able to read and write text without non-sense formatting, HTML was even a thing.
Sans proprietary note taking digital tools (Obsidian, Notion)?
We used to take notes on paper or in our own text editors in the past and format our notes in "raw" HTML.
Sans LLM for coding?
We used to reason about code and go read a programming language book or ask for help from colleagues in case of doubt.
Sans daily upgrades and ads and other modern web crap?
We used to have nice experience with computers.
In a world that used to be simple, what other "sans" would you can think of?
I deal with computers, hence I want things to work the most boring and reliable way possible, with automation, procedures, scripts, not through magic.
Hence, while I love tools such as Atuin, I've a problem with their slogan "Making your shell magical" and generally speaking with any product using such selling argument, especially AILLM-based products.
For this reason, I'm usually against any kind of black box and one-for-everything tools and platforms that want to ease our lives by hiding the complexities. I think that the only result we get out of those abstractions is complexity, pain, and a culture of incompetence and dependability. I mean, if you want to deal with technology, at least you should understand it.
In the end, it's not all magic [1][2], but it can feel magic for sure once we lack understanding. Magic feels shiny and appealing after all, its antonyms say it all.
At work, there exist an onboarding procedure targeted towards new developers in the team, and this procedure relies on scripts which were left untouched for way too long. The bad things : the procedure is broken but nobody dares to fix it, instead the old timers in the team share dirty hacks and workarounds with the newcomers.
Once you face such problem, the only solution is to address the root causes, not the symptoms. I choose to take a look at the procedure, run it again and again after each attempted improvement, cut it piece by piece, shred or rewrite what seems unreliable and suspicious.
Magic exists, but Iβve never seen any in software. Problems are logical. Nothing is impossible. You can solve this problem.1
As a software engineer, please don't fix symptoms. Don't get too used to deal with crap and unsolved problems. Don't be lazy, don't accept the status quo, make the hard work to understand and solve the problems. Set your focus on understanding things deeper. Enhance your and everyone's knowledge. Be a firefighter against ignorance, and help educate your peers to be better at understanding why things work or doesn't.
I've been using a paid subscription to ChatGPT Plus since May 2023 and I'm still happy with the usage. It's one of those tools you have to master to get most of the time spent with it. There are a lot of benefits to use it, of course there are also negative aspects and bugs. Some of them can be mitigated, and that's the purpose of the current post.
Disclaimer / Context of use π§Ύ
I'm ChatGPT mostly for scripts and each conversation is focused on singular topics, i.e single-file codebases if possible.
I don't use Open API Keys and I'm not interested to use OpenAI directly. I've been on a paid plan for OpenAI and was charged way too much for my needs. I advise anyone to use ChatGPT Plus which remain to this day worth it and good enough both for personal and professional.
This article was not written nor reviewed by AI/ChatGPT.
Lessons learned - Do β
Shorten your expectations. Timebox your interactions with ChatGPT. If it takes longer than you expect to reach a solution, stop and do your homework instead, debugging yourself or simplify the problem to solve or take a break...
Test after each change. ChatGPT will make you lose faith by repeating the same mistakes, by removing sensitive code, by providing incomplete solutions, always verify.
Before running or committing anything generated by ChatGPT, always compare with the previous situation you had. Git diff the result of changes. If you have any doubt about a specific change, submit the git diff to ChatGPT for review and ask for explanations while also explaining why you have doubt (failing tests, errors at runtime, weird code removal, ...).
Tell ChatGPT to always decouple code in functions.
Instruct to use minimalist code, and avoid comments in code, respect your specific style (if you provide examples), instruct to write the code that takes the least amount of lines and space and to avoid long functions.
Divide to conquer: Keep one conversation per problem. Once done with the problem, validate the solution (test!), commit locally, and delete or archive the conversation to keep your Chat history clean from everything you don't need.
Take steps: Try to limit ChatGPT's attention to one single file or one single function at a time.
If you have lot of work you expect ChatGPT to perform for you, be patient and request one change at a time, then review the code diff and then the outcome, and only if it's validated, commit and move to the next step. ChatGPT sucks at multitasking. Keep the rest of your TODO list somewhere else to keep track of what remains to be requested from ChatGPT.
You will have a cleaner Chat if you take this habit:
Ask something from ChatGPT.
ChatGPT will answer you something, whatever it is, you will likely want to correct ChatGPT. Refrain yourself and do this instead: cancel what ChatGPT is doing, edit your last input to be more precise and re-submit it, ChatGPT will replace its unhelpful response with something more clever. And you will improve the overall quality of the discussion.
You will be given better results on popular topics than on niche topics / technologies.
Ask to only output the code that require change, e.g add this at the end of your prompt : just output the function(s) needing change
Ask to not change the existing comments, login logic, variables values in the code that is not impacted by the change.
If you really want to multitask, open multiple ChatGPT sessions (browser tabs) in parallel, each focused on distinct changes, so you can multitask while ChatGPT stays focused on single tasks π
One change at a time. If ChatGPT keeps making error, step back, restart from to the latest stable version of your code, and ask to make minimal changes, step by step, while you validate each increment.
When happy with your changes, ask ChatGPT to improve its performance or clean the code or keep it minimal.
When debugging your code with ChatGPT, provide stack traces, inputs, outputs and even the copy of the code that seems buggy (based on the stack trace).
Be suspicious if ChatGPT changes your code way too much or introduce weird changes to dependencies. Always review, check, investigate.
ChatGPT will likely be interesting to use only for writing very small and boring scripts to batch automate some tasks. But you are responsible for the whole, do not forget that. And test. And understand the code. Make it easy to understand and debug. If you can't explain it, rewrite.
ChatGPT could be good at documenting tasks or at writing tests, but for working on complex code it will mostly get 70% of the results then will suck your time and patience.
Lessons learned - Avoid β
Don't trust ChatGPT outputs. OpenAI is known for dreaming and also tends to complexify solutions to simple problems.
Don't run nor commit anything generated by ChatGPT that you don't understand and always compare ChatGPT's solution with what you had before.
Don't ask too many improvements or bug fixes at once or be prepared to deal with many new errors and regressions.
Don't keep conversations for too long, as all the initial context will likely be forgotten about by ChatGPT and you will suffer, also it will cause a lot of scrolling and augment the size of the web page which will be slower to load and will likely crash your browser tab at some point.
Don't switch context / files / problems in the same conversation. It's a waste of time and you will suffer later when trying to source specific content or make sense of anything.
Don't share secrets/passwords with ChatGPT.
Don't waste your time when the LLM seems confused or unable to solve your problem. Either reshape your problem statement or restart from the latest known stable state, ideally in a new conversation. Be confident in your own abilities. Don't be too dependent on any LLM. I once wasted a whole evening and night trying to get ChatGPT to write the solution for me then trying to use it to fix the problems it caused, I was too lazy to code something by myself from the start.
Don't expect ChatGPT to be as efficient on big codebases and complex problems as it is on small scripts and simple problems. So use it more often for the latter and keep the fun of solving the big problems yourself.
Don't expect ChatGPT to understand a single thing you do nor why he generates his code. it's a dumb machine without creativity built in. It has to be treated as such and with caution.
When trying to help you fixing problems caused by its previous solutions, ChatGPT may enter and endless loop of replacing one solution with another, without understanding the context. Before copy pasting anything from ChatGPT, make your own investigation and check the logs of the apps that do not behave as expected, before touching the code. If you find interesting logs, then provide those to ChatGPT or make your own investigation. Do not depend on ChatGPT for too much grunt and research work. You are better than that.
Don't expect ChatGPT to run well and fast on huge bloated scripts. That should encourage you to decouple your code into functions and modules and specialized files/modules/components/...
ChatGPT could be used to address the fact that solving some problems is costly in term of engineering. This XKCD meme below should be likely made obsolete if LLMs are used to provide the programs to automate the tasks. For instance when faced with some painful work, I rather use LLM to write me a script to tackle the task. It will be faster than me on some occasions, which itself help removing the need for manual work for tedious tasks, also help removing the need to prompt LLM in the future for that same task, since the script is already provided.
If you lose focus on the ChatGPT session in your browser, it's likely the calculation process will interrupt.
ChatGPT seems stuck at generating the output ? Refreshing the page might be enough, in other cases ChatGPT might automatically continue the generation or will show a button you can hit to force this action.
I recommend trying ollama so you can work offline and without feeding all your sensitive data into OpenAI.
The π’ engineer has good guts but often seems slow compared to the π° engineer.
The π° engineer is quick at decision and gives impression of progress to the product owner often disappointed with the slow pace of change of the π’.
The π’ is busy battle testing the draft he's about to integrate in the product, suddenly he finds out the new bugs were introduced recently by the π°, and decides to postpone his work while focusing on debugging the shit.
In the meantime, the customer complains because of the new bugs introduced in latest release by the π° engineer.
The product owner is worried and decides fixing this bug is a priority.
The π’ engineer was already investigating the bug and proposes a fix.
The π° engineer cannot wait for the π’ to fix the bug and already merges new changes in the stable branch so the new release will not only be bug free but also deliver new quality shit.
The π’ is busy integrating and retesting all the new changes made by the π° as it seems those changes includes critical changes of the core authentication layer and library updates that had nothing to do with the features the π° was working on.
The π’ suggests to focus on quality and teamwork and slow down but the π° and the product owner look at him suspiciously.
The product owner suggests the π’ to consider leaving the team if he's not happy with the way things are. Because in the end, speed and working long hours are important even if results are not perfect.
π€¦ "fuck this shit". A few weeks later, π’ has left.
The π’ is working in a good team nowadays π€², where testing is a thing β , quality is under control π, documentation matters βοΈ, and collaboration is a foundation π€²πͺ.
Related
How the situation should be managed instead by the PO / Lead.
In 2022 I was going freelance after 12 years of employment. Why ? Because I had been so disappointed by many years of employment, bad managers or politics, I needed to feel like I gave the credit myself deserves. I now feel after one year I would like to help and mentor other people to go freelance.
My toddler (2.5 years old) is going to school and I drive him at school by bike. The more I invest time with him that I don't spend at other crap, the deeper we connect. But crap is everywhere and trying to steal time from us. Seeing him growing so much reminds me of the time passing and the need for me to lead by example.
I learned from hundred of hours spent crafting my LinkedIn profile, sending/receiving tens of thousands of LinkedIn messages, crafting my resume, interviewing for hundred of jobs. No matter how long we play this game of finding the ideal job and finding the exact rates, conditions, etc we deserve and want, those variables keep changing a lot and are difficult to correlate with ideal job. In the end it's not about the job but about who we are, what we need from life, what we really want to do on a day to day, what kind of problems we like to solve, what kind of people we want to work with, what kind of team we want to shape. The ideal job is a rare combination of hidden variables and is a constantly changing problem that requires gut feeling and experience, like finding the perfect taste in coffee / espresso / beer is a never ending game.
As part of this I've removed a lot of my previous job criteria at to recruiters to keep things simple.
Outside of work, I also made a lot of sacrifices, at least choices that I regretted. For the sake of trying to please or do the right thing, I got in trouble a few times. In the future I have to stand for what is worth to me, and trust my gut feeling. I'm always willing to make compromises as I'm a Belgian and we excel in this ! but I also have to set boundaries and speak the truth and take distance at need. Before this post, I struggled to start writing. Speaking of which, I even thought of using ChatGPT to help with the task. ChatGPT has clearly influenced radically the way I interact with the web and the universe of problems, including code but not only. It drastically revived my interest into technology. But it also obvious there is a long way before AI can supersed us. A good tool is nothing without a creative mind and some persistence. And a good mind needs to express, otherwise it's best to just play sudoku alone.
And that motivates me to write. And I make no promises, but to write for myself π and share things.
