Telling Rocks What To Think

Telling Rocks What To Think


First post on this new blog format.  I'm establishing this medium for recoding my professional (coding) experiences, impressions, problems, plans, and solutions.


Erin Spiceland said "Coding is the art of telling rocks what to think."  It's metaphorical, but not by much.  Digital computing mostly relies on silicon working its logic and magic.  You talk to it in painfully specific code.  You need all the material, semantic, and verbal components just right.  If you get it right, then it talks back.  Get it wrong, and you have just found a "bug".


I named my blog "Debug and Rebug" to indicate two key principles of my approach to coding.  First, "debug": When you write your code, it will never work perfectly, as you envision it.  Perfect running never happens; it's an inevitable consequence of entropy, human lateral thinking, and logic's inexorable conflict with our wants.  Those are some fancy words, all right, and it means that a large part of coding is fixing errors.  Finding bugs and correcting them into working code.


Second, "rebug": The debugging process is never done.  Always the world will give you requests to change some aspect of the code; always there will be some new development out in the world, that will break the code's work.  Whether it's requests or not, the code still needs to be continually updated.  And this maintenance brings its own share of all-new bugs.




So here it is: my first blog post, my own version of "Hello, World!" in Blogger format.  I have been studying software development now for eight (8) months.  Python, Go and Kotlin, IDEs (VS Code is my go-to), GitHub, backend development, and, absolutely of course, the tectonic quaking of LLMs on all of this.  I am developing opinions about things.  So I thought I should note them down.


I mentioned GitHub.  It's my repository for code, just as this Blogger is my repository for my journaling.


https://github.com/mjteegarden



Comments

Popular posts from this blog

WWHD?