• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle


  • Of-the-shelf SSDs are optimized for speed and price.

    Flight recorders are typically specified to withstand an impact of 3400 g and temperatures of over 1,000 °C (1,830 °F), exposure to salt water, and high pressure if it sinks to the bottom of the sea as required by EUROCAE ED-112.

    Maybe you could design a flight recorder that uses SSDs, but then you must get it certified again for the new hardware, which will cost a lot of money nobody wants to spend. The next step in flight recorders is to also send a live feed of telemetric data back to some ground station so the last position of the plane is known - with a flight recorder you only get this data after you found the wreck. Currently submitting this signal is optional and can be turned of by the pilot, which is the reason why Malaysia Airlines Flight 370 is still missing.






  • I think the money is not that important at this stage. As an important figure you will get a lot of favours and freebies from people and companies, so you dont pass regulations that would hurt their bottom line. You also have a lot more opportunities later by being spokesperson for other organisations, can write books because everyone knows your name or get hired by a big company, because you already know half the politicians they deal with.


  • AnAngryAlpaca@feddit.detoProgrammer Humor@programming.devInfinite Loop
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    7 months ago

    No wonder COBOL programmers are paid a lot, because what would be a 1-liner for “hello world” in other languages looks like this in Cobol:

    IDENTIFICATION DIVISION.
    PROGRAM-ID. IDSAMPLE.
    ENVIRONMENT DIVISION.
    PROCEDURE DIVISION.
        DISPLAY 'HELLO WORLD'.
        STOP RUN.
    

    This is already $6000 worth of code right there!


  • The Lead Dev/team Lead was quite arrogant and in his own mind the worlds best developer who had all the answers. If some technology or software was not written by him or already existed in the 90s it was “useless” and not fit for the company (without him having looked at it or the docs). If asked why we would not use X which was out for years, well maintained, had no critical bugs would solve problem Z we where having, he would reply “because i said so” and insist in writing out own variant - which ended up having 10% of the features, 10 times the bugs, terrible UI and would take months to develop.

    When support repeatetly told him that users had issues with feature X because the only error message on a 10 fields forms page was “Error”, he would respond that this is a user problem, the end user is clearly stupid (despide used in a field where you need to study for years) and that support must hold training sessions so the users can “learn” how to use his product.

    As such, the company would reject git and instead email each other files and changes.

    Each meeting felt like living inside a Dilbert cartoon.


  • You only hurt yourself down the line. My last job had not improved their own product, processes, tools or frameworks, so everything was still stuck in the 90s. Their product was build on an discontinued an proprietary database and server system you never heard about, jQuery UI from 10 years ago and other BS.

    However if you don’t upskill yourself in this situation you will be unemployable in the future, because all other employers demand modern technologies, git, docker, unit testing etc., which I was yelled at in meetings for suggesting it.