home.social

Search

5 results for “glloyd”

  1. I view my career as a system engineer.

    Software, digitisation, and automation happen to have been part of that career. I'm not sure if they are defining attributes.

    Yet resource optimisation (reduction of effort or waste), and problem solving (working out what the problem is, and finding solutions) both resonate with me.

    What do you think your career is about?
    (This is for an upcoming meetup conversation)

  2. I think I'll be attending. Does anyone have some good questions that I should get their responses on the record?

  3. Inertia resists change. It takes effort to make a change.
    Some systems, by design, try to make themselves sticky, adding resistance, perpetuating your inertia.
    Vendor lock-in, incompatible apis, notice periods, exit fees, etc.
    So, even when you are let down, you might change anything.
    "It wasn't that bad", "we survived it this time", "what's the chance we'll hit that again"

    Strive for better, demand improvements, or break the inertia.

  4. Need some help from the fediverse.

    In December, I'm running a meetup. It will not be a talk, but a group conversation.

    What does it mean to be a programmer?

    I'm looking for a wide range of views to start our conversations. Please reply with your takes, or even play Devils advocate and share a view you don't hold be understand others might.

    Even better, if you are near York UK on 2nd December, come along

    meetu.ps/e/Qn3rp/HjpZG/i

  5. If you fully outsource your work so that none of your team fully understand the codebase, it's a production risk.
    You need to have an internal up to date knowledge to handle outages and production incidents.
    Or, at minimum, you should ring fence the outsourced code so that its blast radius is a known minimised risk.

    Yes, by outsourcing, I include AI code generation.

Share on Mastodon

Enter the server where you have an account.