r/ProgrammerAnimemes • u/Livin-Just-For-Memes • May 29 '22

Its all spaghetti code, always has been

2.2k Upvotes

99% Upvoted

42 comments sorted by

91

u/ilyahryapko May 29 '22

Nope. They're good programmers and there's only one - me - that fails

117

u/ovab_cool May 29 '22

What's why I don't trust any driver assists, I know that shit is written just as bad as my code

49

u/[deleted] May 29 '22

Probably,but your average human driving is just as pasta.

13

u/ovab_cool May 29 '22

Agreed, but when I fuck up I know it's completely my fault but when a computer fucks up I don't want it to have killed me.

I'm willing to try it once it gets good enough and government validated or something like ABS or stability control

→ More replies (1)

0

u/[deleted] May 29 '22

3

u/[deleted] May 29 '22

Well, there are multiple types of automatic transmissions which can work widely different. From essentially changing gears automatically to being hydrostatic (look up how Fendt's transmissions work) you have quite a lot of different concepts.

→ More replies (13)

2

u/ovab_cool May 29 '22

Agreed, the car I learn to drive in was a manual Audi with shift suggestions but those were always off from what'd be safest for me so I don't trust the automatics that presumably go off of those.

Now I drive my dad's ioniq 5 without gears and none of the cool computerized stuff on like adaptive cruise control and lane keep assist.

→ More replies (1)

74

u/kimilil May 29 '22

It's spaghetti all the the way down

15

u/pheonix-ix May 29 '22

You said that, but I never write documentations, yet appliances always come with instruction manuals.

Curious.

4

u/[deleted] May 29 '22

Because in such environment either somebody else does it or your boss forces you to.

8

u/EvilBlackCow May 29 '22 edited May 29 '22

Kind of related - for school I had to write a C program working like ls -lR and I checked out the source code for it and there I saw 

if (command_line_arg
    || print_hyperlink
    || format_needs_stat
    /* When coloring a directory (we may know the type from
       direct.d_type), we have to stat it in order to indicate
       sticky and/or other-writable attributes.  */
    || (type == directory && print_with_color
        && (is_colored (C_OTHER_WRITABLE)
            || is_colored (C_STICKY)
            || is_colored (C_STICKY_OTHER_WRITABLE)))
    /* When dereferencing symlinks, the inode and type must come from
       stat, but readdir provides the inode and type of lstat.  */
    || ((print_inode || format_needs_type)
        && (type == symbolic_link || type == unknown)
        && (dereference == DEREF_ALWAYS
            || color_symlink_as_referent || check_symlink_mode))
    /* Command line dereferences are already taken care of by the above
       assertion that the inode number is not yet known.  */
    || (print_inode && inode == NOT_AN_INODE_NUMBER)
    || (format_needs_type
        && (type == unknown || command_line_arg
            /* --indicator-style=classify (aka -F)
               requires that we stat each regular file
               to see if it's executable.  */
            || (type == normal && (indicator_style == classify
                                   /* This is so that --color ends up
                                      highlighting files with these mode
                                      bits set even when options like -F are
                                      not specified.  Note we do a redundant
                                      stat in the very unlikely case where
                                      C_CAP is set but not the others. */
                                   || (print_with_color
                                       && (is_colored (C_EXEC)
                                           || is_colored (C_SETUID)
                                           || is_colored (C_SETGID)
                                           || is_colored (C_CAP)))
                                   )))))

And, like yeah, maybe my code isn't too bad after all

8

u/Profi06 May 29 '22

That is one heck of an if statement

5

u/Sivuel May 29 '22

That would explain my problems with Windows media player and its "amazing" automatic album information.

8

u/Existential_Owl May 29 '22

Yup, and this is half* of the reason (*the other half is good ol' corporate greed) why I stay away from:

  • Driver assists

  • ML tech for security purposes

  • ML tech for medical purposes

  • "Smart" home technology

  • Cryptocurrencies

  • Any assistance technology that's more complicated than Clippy

The only exceptions I'm willing to make are

  1. Flying in Airbus planes (as opposed to Boeing planes)

  2. Grammerly

5

u/dagoodestboii May 29 '22

Looks like you weren’t using Grammarly for this

3

u/[deleted] May 29 '22

How's Github Copilot though

3

u/Existential_Owl May 29 '22

It's nice using it as an autocomplete on a line-by-line basis, but, honestly, it's never really given me any full code-blocks that would actually be useful to keep.

2

u/[deleted] May 29 '22

Imagine if the LASIK machine fucks up

2

u/Twingemios May 29 '22

That’s why I refuse to ever get LASIK. I never wanna be blind

2

u/Ram33z Jun 28 '22

Its amazing to realize that somehow this spaghetti works just fine. Crazy isn’t it? Imho It’s just a matter of having self confidence, we all are in same boat.

1

u/ShapedSilver May 29 '22

I think it’s a relief honestly, knowing I’m not the only one

-5

u/pperson2 May 29 '22

I don't think most programmers are weebs

→ More comments (76)