Which code? BASIC? Commodore Vic-20 or AppleSoft BASIC? 6502 machine code? IBM 3081 Assembly code? FORTRAN? COBOL? Pascal? C? Prolog? dBase IV? VisiCalc? Excel? Python? Ruby? Puppet? Chef? Ansible?
I’ve programmed in all of these languages, and probably some more that I have forgotten. None of them are a second mother tongue to me, even though I’ve been programming in one form or another since the summer of 1982. So, I’m curious to know how you got to that stage?
Oh, yeah. I forgot about the Bourne, Bash, C-shell and various other shell languages I’ve written in. And the HTML I’ve written.
There is one point that I recently made to another developer on a Discord server. Code itself really only defines the “how” of what you are doing. And maybe some of the “what”. But code never really defines the “why” of why you are doing it this way. What lessons you’ve learned along the way of the bad things you want to avoid, or the ignorance you still have about the lessons you have not yet learned the hard way.
For code, I submit that the single most important thing you can capture, is the “why”. The “what” and the “how” fall out naturally from there.
I think that’s why Amazon has this “Five Whys” method that they hammer into the brains of everyone who works there. Once you understand the “why”, and you work backwards from the customer, everything else just falls into place. Well, maybe it’s not that easy, but it’s certainly a lot easier than if you had not done that process.
So, document your “why”. Document that in everything, not just your code. Future you will thank past you for that documentation.
Which code? BASIC? Commodore Vic-20 or AppleSoft BASIC? 6502 machine code? IBM 3081 Assembly code? FORTRAN? COBOL? Pascal? C? Prolog? dBase IV? VisiCalc? Excel? Python? Ruby? Puppet? Chef? Ansible?
I’ve programmed in all of these languages, and probably some more that I have forgotten. None of them are a second mother tongue to me, even though I’ve been programming in one form or another since the summer of 1982. So, I’m curious to know how you got to that stage?
Oh, yeah. I forgot about the Bourne, Bash, C-shell and various other shell languages I’ve written in. And the HTML I’ve written.
There is one point that I recently made to another developer on a Discord server. Code itself really only defines the “how” of what you are doing. And maybe some of the “what”. But code never really defines the “why” of why you are doing it this way. What lessons you’ve learned along the way of the bad things you want to avoid, or the ignorance you still have about the lessons you have not yet learned the hard way.
For code, I submit that the single most important thing you can capture, is the “why”. The “what” and the “how” fall out naturally from there.
I think that’s why Amazon has this “Five Whys” method that they hammer into the brains of everyone who works there. Once you understand the “why”, and you work backwards from the customer, everything else just falls into place. Well, maybe it’s not that easy, but it’s certainly a lot easier than if you had not done that process.
So, document your “why”. Document that in everything, not just your code. Future you will thank past you for that documentation.