• 1 Post
  • 56 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle
    • weil man erst ein neues schienennetz, bahnhoefe, stellwerke, werkshallen zur reperatur bauen muesste, was in deutschland mindestens 20 jahre bis zur ersten fahrt dauern wuerde, selbst wenn man finanzierungsprobleme, kostenueberlaeufe und anwohnerklagen ignoriert
    • weil es bei preis, verbindungen und geschwindigkeit in direkter konkurenz zu schnellzuegen wie ICE stuende. Wozu zwei systeme bezahlen die den selben zweck erfuellen?
    • die leute wollen lieber billigen, zuverlaessigen und wenn moeglich direkten transport ohne viel umsteigen als eine gadgetbahn die am ende teurer als flugzeug oder schnellzug ist
    • teure schnellzuege lohnen sich fuer den betreiber nur in gegenden mit hoher bevoelkerungsdichte, und wo der zug auch noch schneller als das auto ist wie in Japan und China - da fahren die schnellzuege quer durchs land wirklich alle 10 minuten und sind trotzdem immer voll.
    • viel sinnvoller wäre es, wenn es ein einheitliches Buchungssystem wie bei Flügen gäbe, und man seine Zugfahrt Kiel nach Venedig auf einer Webseite komplett buchen könnte, statt für jedes Land neue Fahrkarten zu kaufen.

    In Deutschland wird das geld lieber in autobahnen gesteckt, es gibt kein templimit und das schienennetz vergammelt.












  • 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.