• 0 Posts
  • 104 Comments
Joined 2 years ago
cake
Cake day: February 5th, 2025

help-circle

  • MangoCats@feddit.ittoProgrammer Humor@lemmy.mlWelp
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    Back in the day it was CompSci, or Electrical Engineering. I don’t know if they’ve really started teaching actual software engineering yet or not, back in the day it was a bunch of theory that’s mostly just foundational stuff that you don’t really interact with day to day anymore. In other words: academia was 10+ years behind industry, which is pretty typical, but not such a problem in a field like Irish Literature as it is in software engineering.



  • I forget what the latest I ran the numbers on was, but $100K up front and $20K per year running costs seemed like it had a decent chance of being useful to our department of 10 software engineers, which isn’t bad, but it’s an LLM on par with 6 months ago’s frontier models.

    If I could get those prices for a local instance of Fable 5, I’d be pushing the paperwork to make it happen.





  • I had this for about 6 years running, eventually we marked the bottom 90% of the heap “won’t do.”

    This was in the early 90s, I kept track of the items on “sticky note” software on my Windows 3.1.1 desktop. At the top of the sticky note I placed a gothic font “The Creeping Feature Creature” label. Two or three times a week my boss would stop in on his jog (he lived a mile away) with a new idea, and we’d prioritize it into the stack - most new ideas went just below whatever I was still working on. Every few months we’d reshuffle the list. It was a workable arrangement because I was the only programmer and he was the company owner.

    When we started working on bigger contracts for outside customers, he shut the hell up and let me get the contracted work done.


  • Regardless of how effective it is at managing expectations, my reality is:

    Mgt: We need A within Y days.

    Stf: A will take X (>>Y) days, A/2 can be ready in Y days.

    Mgt: O.K., give us A/2 in Y days.

    Y/2 days elapses.

    Mgt: In addition to A/2, please add B, C and D to the deliverable.

    Stf: You realize, that’s going to take an extra 2X days to deliver.

    Mgt: yes, but we absolutely need B. C and D, whatever it takes, as soon as possible, don’t waste time releasing A/2, bundle them all together for efficiency.

    Stf: Coming up.

    3X/2 days elapse.

    Mgt: you know B, C, and D that we asked for? Actually, what we need are D, E and F.

    Stf: well, we’ve finished A/2, B and half of C. When do you need D, E and F.

    Mgt: ASAP, put C on the shelf.

    X more days elapse.

    Stf: here’s A/2, B and D, how do they look?

    Mgt: You know, the full A would be better… but E and G are our absolute top priorities…


  • Not silent, the passwordless sudo calls are logged and available for review. I do trust that after several months in a sandbox without calling sudo, it’s unlikely that a sleeper agent will awaken and call sudo out of the blue - more likely that my apps that have been calling sudo will do something nefarious on the 1000th access…

    Somebody (possibly an AI agent…) could/should automate the process of transcribing the sudo logs to the NOPASSWD setup, just leave sudo unlocked for those things that show up as needing it during validation test runs and turn the sudo lock back on for everything else.



  • MangoCats@feddit.ittoProgrammer Humor@lemmy.mlCode Quality
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    Do you know the cost to change the color on a box? Just the color, not the text, not the information, just the color?

    Estimate:

    $470,000

    No scrap cost, old color boxes used until stock depleted.

    Vendor didn’t charge us anything to change the color on the next and subsequent lots.

    All that was engineering hours for the document revisions, meetings to support document changes, training, recording of documents, first article inspections, etc.


  • MangoCats@feddit.ittoProgrammer Humor@lemmy.mlCode Quality
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    Not just in implantables, though implantables have that whole additional surgical risk aspect, but all medical devices have painful piles of paperwork required for each revision. They’re trying to lighten the load for “security patches” but so far it’s still a major pain. I suspect it’s the much the same in avionics and any other industry that requires documented validation against traceable requirements and all that jazz.



  • MangoCats@feddit.ittoProgrammer Humor@lemmy.mlCode Quality
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 months ago

    Every time I look back at old stuff, I have to remind myself of the relative importance of getting it done, vs getting it perfect, at the time.

    Inevitably, there were no clear requirements at the outset, or if there were they were vastly outnumbered by additional requirements that scope-crept their way into the project. The project was “due” before I was asked to help / landed with the whole thing to do myself. The project was under-estimated and is now “on the critical path” for a larger initiative. Other interested parties are too busy to meet during definition time, but all too willing to point out missing scope after a “finished solution” is presented.

    Yeah, me from the past… not a fair reflection.