• 0 posts
  • 41 comments
Joined 2 years ago
Cake day: December 7th, 2024
  • “Sometimes the best way to fix a bug is to introduce an unstable new feature that will later have many bug reports. But the code will now work. And was only written after email chain that har management involved.”

    “This is a temporary fix only, and the feature flag it’s under should be turned off after pull request 203. Under no circumstances should bug reports 1923 and 2045 use this new feature to fix issues, even if hours of work can be saved using this ”

    “I am blameless for any future issues caused by using this new feature. Here be dragons.”

  • I think nobody understands exactly how anything works, but enough of us understand our own little corner of tech to make new things and keep the older things going. I’ve been coding for decades, and proudly state I understand about 1% of what I do. This is higher than most

    AI will make these little gardens of knowledge smaller for most, and yet again we, as the human species, will forever rely on another layer of tech.

  • Ignoring your rudeness now. It’s more like I’ve seen the same wheel invented a lot of times and can recognize most tech are basically equally functional.

    I used to make fun of cobol because it has no stack; I often wondered why such a language was ever popular, why it had so many lines of code. Now, I know there was a reason it worked, why it still is used, and can appreciate how people work with it.

    I’ve made a couple of my own languages nobody uses; so new and different languages do not overawe me as much.

    Any popular language, new or old, works well enough with it having strengths and weaknesses. Some have superiority in their libraries or ecosystems and not the core. It’s ok to choose a language based on this or that. It’s ok to mix and match languages together in one project because it’s how they talk together which makes it work, and in the larger scope of things it really does not matter which is used.

    I personally have nothing against any language, including rust.

    It’s a general trend to try to fit a specific language everywhere that irritates me, I tend to see that as a software nerd’s religion or politics instead of how much better that language is.

    And so, based on the above, is why proponents of their holy language irritate the crap out of me. And rust is certainly not the first to do that

  • In some situations with some people yes. It’s really hard to separate the project and team.

    Usually, projects I have seen start with the best plans and methods, or at least vague good intentions, but later pretend they never met them. Like a cheap date.

    There are some projects that naturally lend themselves to one approach or other, and they last longer following the original guidelines ; but if a project lives long enough these guidelines become the enemy.

    I think the only projects that follow any set of guidelines for longer than a few years; they have a narrow purpose for being. Straightforward evolution or needs