Tips for programmers to stay ahead of generative AI
11–20 of 319 posts
Re: Tips for programmers to stay ahead of generative AI
#12How to survive in an AI world? Shift your mindset from “I write code” to “I deliver value”. Now instead of AI replacing you, it’s helping you get more done (in theory). Everyone wins. Staking your career on being a pair of hired hands that executes somebody else’s exacting specifications was always a long-term losing proposition. And we are very very far away from AI being able to ask the right questions to help busi…
I also find it bizarre that so many people feel precious about the code. They have too much ego attached to what they type in and the AI kind of make them feel insecure. I couldn't care less if I write the code, the AI or someone I told to write it. What matters is the value it provides.
Would you find it bizarre that a joiner feels precious about not just the cabinet they made (value), but how they made it? The joints they used, the process they went through, the wood (i.e., the code)?
A plumber, electrician, architect, designer, programmer -- we take pride in our skills.
Craftmanship is a virtue, not a vice.
Re: Tips for programmers to stay ahead of generative AI
#13How to survive in an AI world? Shift your mindset from “I write code” to “I deliver value”. Now instead of AI replacing you, it’s helping you get more done (in theory). Everyone wins. Staking your career on being a pair of hired hands that executes somebody else’s exacting specifications was always a long-term losing proposition. And we are very very far away from AI being able to ask the right questions to help busi…
I also find it bizarre that so many people feel precious about the code. They have too much ego attached to what they type in and the AI kind of make them feel insecure. I couldn't care less if I write the code, the AI or someone I told to write it. What matters is the value it provides.
Re: Tips for programmers to stay ahead of generative AI
#14Re: Tips for programmers to stay ahead of generative AI
#15I would say it improves my productivity by maybe 5%, which is an incredible achievement. I’m already getting to where coding without it feels very tedious.
Re: Tips for programmers to stay ahead of generative AI
#16Re: Tips for programmers to stay ahead of generative AI
#17> Software engineers should be critical of the outputs of large language models, as they tend to hallucinate and produce inaccurate or incorrect code. This seems to be the case more than not for certain tasks, anything assembler or C I have ever asked it has turned out to be at least somewhat wrong. Mixing styles and syntax all over the place. I am not afraid that some generative AI will take my job anytime soon.
These things are a matter of writing a correct prompt. Like "use this and that naming convention for variables and keep this and that style". You can also ask it to write tests for the code so you can verify it is working or add your own additional tests. Even if the produced code is wrong, it usually takes a few steps to correct it and still saves time. It is an amazing tool and time saver if you know what you are d…
I have this friend who gets obsessed with things very easily and ChatGPT got to him quite a bit. He spent about two months perfecting his AI persona and starts every chat with several hundred words of directions before asking any questions. I find that this also produces the wrong answers many times.
Re: Tips for programmers to stay ahead of generative AI
#18How to survive in an AI world? Shift your mindset from “I write code” to “I deliver value”. Now instead of AI replacing you, it’s helping you get more done (in theory). Everyone wins. Staking your career on being a pair of hired hands that executes somebody else’s exacting specifications was always a long-term losing proposition. And we are very very far away from AI being able to ask the right questions to help busi…
I also find it bizarre that so many people feel precious about the code. They have too much ego attached to what they type in and the AI kind of make them feel insecure. I couldn't care less if I write the code, the AI or someone I told to write it. What matters is the value it provides.
They meant it, too. Noticing that the "or" instruction differed only by one bit from the "subtract" instruction told you something about the probable inner workings of the CPU. It just turned out that it didn't matter - knowing that level of detail didn't help you write code nearly as much as it helped to be able to say "OR" instead of "032".