• 4 Posts
  • 58 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle




  • It might be a side effect of my work environment. I make the equipment that tests electronic medical implants. Theoretically if a unit put 1A of charge out instead of 1ma that could kill a person. Now on a practical level that’s not possible with our devices and even if it was we should be able to identify and prevent that unit from reaching the field.

    Yes you are right, you want 99.99% uptime you need this stuff. In the field I’m in a single case escaping test can be months of engineering time to investigate, root cause analysis to determine the actual cause, expensive fixes for the short term and even more expensive fixes in long term to upgrade everything so it never happens again.

    Boss being unhappy that you missed something is minor. Their boss’s boss’s boss is the real issue. That said we get regularly audited both in-house and external agencies so it’s unlikely. Multiple lines of defense, have a computer check it, have a person check that the computer actually checked it, have a computer verify that the person actually verified it. Have each of those systems regularly audited and verified to be effective.

    It’s expensive but it is what is needed to be in this field.


  • Ok,this maybe too nerdy of a topic for here but that’s why I love unit tests.

    Basically I write a piece of code that gets this input and generated that output. I also make a test to verify that I get a certain output given a certain input.

    Now if I spend all day futzing within that code , changing variable names, refactor and extract a large function to 10 small ones, decide to re-write all the SQL queries to linq arguments…I can fuck up and tests may fail. I fix the failing code to still pass the test. I know I delivered code that met the requirements, hopefully improved it, but I know I didn’t fuck it up enough to not do what it’s expected to do.

    Plus source control…I mess around with code, my tests all pass…I commit it…I mess around more, can’t get the tests to pass, oh well quitting time roll back to previous working commit. Boss may be mad I didn’t improve it but at least I didn’t break it. Zero gain day is better than negative gain…




  • vrek@programming.devto196@lemmy.blahaj.zonejob rule
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    This a actually worked out for a co-worker. He interviewed for a position and the interview went of like 6 hours. He waited 6 months and never heard anything. He applied for another position at my company. Different team, lower pay and not in his specialized field. He got that job. Another 3 months and the boss for the first job called him and said their initial hire didn’t work out and asked if he was still interested.

    He laughed and said he was already working but would be interested. The boss asked where he was working. He replied “I’m actually down stairs”.

    He got the job, more money then the initial offer and he was happy in the new position. Probably an unlikely event and I wouldn’t recommend trying to duplicate it.






  • Long story short… Most of the money the company earned was from the credit union. I went through a depression phase and tried to kill myself (I’m doing better now) so I was inpatient in a mental ward for about a month.

    The credit union got a computer security audit from the ncua(similar to fdic but for credit unions). My boss could not access any system. No servers, no firewalls, no intrusion detection systems, nothing. I had the passwords but was unable to be contacted and “documentation was a waste of time”.

    They failed the audit. Credit union basically asked “we pay you for computer security, we failed an audit for computer security, so why do we pay you?”

    Contract was lost and company went under shortly afterwards.


  • Ok, I’ll give my experience. I was hired as basically a paid intern. I was in high school, I “knew” computers like a nerdy teenager knows computers… Not real knowledge of their workings but I played with some programming(I got hello world to work using perl) , I could install linux(in the early 2000s, I bought copy of Debian Linux on 7 cds). I was basically told I would be an assistant to the other computer technician.

    A week after I got hired, he got fired. For the next several months people got hired and fired after a 2-3 weeks. The company was 3 people, myself, the owner, his wife did the accounting. I didn’t know what I was doing, googling what I could to figure stuff out(i now know that’s normal but also now know how to Google correctly). I leaned on the owner to figure out things. I don’t know if your job is in computers but these are things I learned later were absolutely idiotic.

    1. If a computer came in with a suspected virus, standard protocol was no research or investigation… Format and reinstall.

    2. We had corporate clients (main client was a credit union), we gave the windows CD and license code to each teller with no record of what they were. He sold the license at the price he bought then for from staples.

    3. All servers had local admin accounts. All local admin accounts had similar passwords. I was the only person who knew what those passwords were.

    4. My boss thought time spent documenting was time wasted.

    Anyways I stayed there for 4 years. It was not perfect and I learned so much wrong stuff. It was a decent job, my boss had really weird rules(why so many people got fired), and my time would of been spent better learning correct information.

    That said I ended up causing the company to go bankrupt and the owner and his wife are now Christian consulers…