• 1 Post
  • 41 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle



  • vrek@programming.devtoaww@lemmy.worldNew game!
    link
    fedilink
    English
    arrow-up
    43
    arrow-down
    1
    ·
    21 days ago

    If your dog is ever running and you can’t catch them act hurt. Pretend to fall and hurt your knee. Most likely it will come back and check on you and you grab it, unless it’s playing with something else then good luck


  • I had that experience last week. I half blame the language though cause the way it works is you don’t initialize a variable, first time you use it the language automatically makes the variable and default value is 0.

    I had a variable countoot that I had a formula calculate. Then a simple if countoot > 0 do this else do that. The program kept doing that. I knew countoot should be 2. I manually did the formula … The answer was two.

    I did the same formula in 3 other programs and it worked correctly. I spent between 1.5 to 2 hours a day for like 3 days banging my head on the desk trying to figure out why it would work. Fourth day me and 2 other guys were trying to figure it out when I finally really looked closely. I realized the formula result was stored in ccountoot(notice 2 c) and the if statement was based on countoot(notice 1 c)…yeah I felt so stupid when correcting the typo fixed the problem.



  • The difference is in exact wording Agile: the software shall properly authticate a user within our active directory.

    Documention : user authentication will be provided by functions ”valisate username” as described in section 14,7 subsection 4, ”validate password” as described in section 16.2 and validate the correct pasword as described in section 23.4.Proper authication to the correct use group shall comply with the requirements in document 654689 section 64.7 subsection 17

    Yes there is a difference and one is better…








  • I work for a medical device manufacturer and you are missing a important reason for that exception. Yes human lives are on the line. In addition WE (meaning my company) are responsible for finding out why it broke and how we will prevent other devices we make from breaking.

    We make a device and say it will last 10 years, 2 years later it stops. We have to replace it, We have to investigate to the best of our ability, We have to report our findings to the government, if several cases happen We need to come up with a prevention for the future dailures(or prevention if severe enough). We have entire departments for this. It is our burden not the consumer and it’s our burden so we have enough evidence to determine root cause and final solution so we can prevent further failures.








  • In this case I do partially agree with it. They are for medical implants and since the expected lifetime of the device is 10 years we need to be able to support them for 10 years after the last surgery.

    If the dog eats your controller which allows you to turn on and off your device we need to be able to sell you a new controller and NOT tell you “sorry, you need to spend several hundreds of thousands of dollars in medical bills to replace the device and go through a traumatic surgery to install it”

    Now optimally my company would make a modern program that duplicates the technology but is compatible with modern computers but since are no longer making money on these old devices they don’t want to invest the time and money. So yeah…