Do As I Say, Not As I Do

  • Comments posted to this topic are about the item Do As I Say, Not As I Do

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • No, I never... 😉

    I found an external drive full of code a couple of months ago, and I hadn't the slightest clue what those are. According to the dates, I wrote them around the early 2000s late 90s, when I taught programming and database design/admin. I did not have the heart to throw them out, though they were inadequate for today's use. It is probably similar to most of our father's issues when they collected the slightest bits of "junk", claiming, "It will be good for something". My ex's father was an electrician. After he died, we removed a few cubic meters of broken motors and similar valuable things from his shed. At least my kids' situation will be much easier with those junks, in my case, with only one external drive to throw into the rubbish.

     

  • This was removed by the editor as SPAM

  • My ears are burning! Yep, right of passage mistake.

    One thing I have learned over time is that cookie cutter projects, Docker images or templates are extremely useful, even for personal projects.

    Somethings are set it and forget it, which is great... until you need to set it again which is why the discipline of using templates and Docker images is so important.  It is no different from a joiner cleaning and organising their tools at the end of the day.

    I've found that as I've got older my personal projects are to teach me so I can teach others.  That makes it far easier to adopt the disciplines of filling in README.md files, diagramming etc.

    I inherited a tin of random screws, hooks and dowels from my father.  He'd inherited it from his father.  Over time I've been very grateful for that tin.  A sign of growing old is that point in your life where you start putting INTO the tin rather than rummaging for something to take out.

  • WOW, Grant, great topic. I've been using GitHub for 6 or 7 years. At the beginning I hadn't a clue what the README.md file was for, so I ignored it. Those early repos are a mystery to me. And after 6 or 7 years, I've begun wondering if I shouldn't just get rid of some of my repos. I've got a few of Advent of Code repos that I thought would be good to keep around, but honestly, I never look at those. I have gotten better at Markdown, so my README files, which I always create, have something in them about what the repo is about. Occasionally, I'll even create a Wiki for a repo. I don't tend to create Discussions, but I do know what they're for. I have also begun to create a Docs folder at the root level and put in Markdown files specific to that branch, etc.

    But I'm still working on trying to decide which repos are destined for the recycle folder.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • Clean up was pretty severe. I dropped a bunch of repos, including one empty one. Don't ask. But yeah, I really let that slip.

    And when my mother-in-law passed, we went through their house (my father-in-law had passed a couple of decades ago) and the drawers filled with loose bits of rubber, let alone random screw collections, were disconcerting, baffling, and frankly, hilarious. Cause yeah, keeping stuff, just in case, leads to an interesting place.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • It's funny how we end up holding onto so many random things from the past, whether it's old code, tools, or even random screws. I've definitely had moments where I’ve gone through old files and thought, What was I thinking? But in a way, it’s nice to realize that all these "random bits" are part of the process of learning, and we often find a use for them later. Like you said, taking the time to organize and clean up—whether it’s your code or physical stuff—can really help bring some much-needed clarity.

  • This was removed by the editor as SPAM

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply