A husband. A father. A senior software engineer. A video gamer. A board gamer.

  • 1 Post
  • 188 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle




  • That “just changing a word” is easy and quick. A codebase is an iceberg. Management only really typically understands the surface, but there is a disproportionate amount of ice under the water.

    I had to change all instances of a label from a word to an abbreviation. Because we don’t have i18n set up in the app, it ended up affecting 55 different files. I did my best to consolidate into everything calling a common function, but it’s far from perfect. 55 files changed because management said “oh this word here should be shorter”.





  • I’m less worried and disturbed by the current thing people are calling AI than I am of the fact that every company seems to be jumping on the bandwagon and have zero idea how it can and should be applied to their business.

    Companies are going to waste money on it, drive up costs, and make the consumer pay for it, causing even more unnecessary inflation.

    As for your points on job security — your trepidation is valid, but premature, by numerous decades, in my opinion. The moment companies start relying on these LLMs to do their programming for them is the moment they will inevitably end up with countless bugs and no one smart enough to fix them, including the so-called AI. LLMs seem interesting and useful on the surface, and a person can show many examples of this, but at the end of the day, it’s regurgitating fed content based on rules and measures with knob-tuning — I do not yet see objective strong evidence that it can effectively replace a senior developer.


  • If I may ask for my curiosity…

    Can you describe how the hosting is set up?

    Is it a single VM? Or are you running 2 or more VMs and utilizing a load balancer? If not, do you not yet see a need to do so?

    I will say the uptime these past couple months has been amazing. I know with the influx last summer and the updates to Lemmy, things were a bit rocky at times, but I appreciate the work you all have done to stabilize the site.

    Thank you all for working to make a stable, safe, and inclusive space!



  • That’s the beauty of science, I don’t have to experience something to believe it to be factual, and if I experience something that I don’t understand, I can work to find out without having to immediately believe something is objectively factual or not. I’m okay with not knowing until I find out. That’s the problem with religionists, they require answers but substitute superstition and “faith” in place of actual provable fact. The point of science is the endless pursuit of objective discovery and fact.

    All this to say, I do not buy into the premise that I must make a belief in something just because I experience it.


  • I live my life by facts and evidence and I am not reliant solely on my own experiential evidence.

    If I come across something that seems to contradict what I believe to be a fact, I research it (to the best of my ability) to see if it’s just me who is wrong.

    Of course, I am human, and fallable, and my emotions certainly can get in the way. But I try to be aware of them so I can put them into perspective.

    Beyond that, I would need specific examples to address, as I’ve never had any experience that I can recall which contradicted anything already explained by science.





  • Of course! I have numerous various systems at my disposal: Savage Worlds, Fate, Fudge, Mork Borg, etc.

    But that doesn’t mean I can’t have a soft spot for D&D. I played it back in the early 90s when it was still AD&D 2nd edition. I remember having a love/hate relationship with THAC0. So I’d like to see D&D get owned by a company that understands what they have is something to be nurtured, not exploited. So if Hasbro sells it, my hope is it will go to a company that will do that. I’m sure I’ll be disappointed, but I’m still going to leave room for that hope.



  • The moment you push your changes to origin, other developers can then pull them. If you intend to squash or fixup commits, then you should do so after committing to your local git, but before you push to origin.

    Once you push to origin, the commit hashes from your local branch become what origin has, and then those commit hashes are now possibly on another developer computer after they pull.

    If you do a squash or a fixup, the existing commits are effectively rewritten into a new commit with a new hash so the developers who happened to pull what you previously pushed now have their HEAD pointing to a hash that no longer exists — thus orphaning.