Skip Navigation

Posts
1
Comments
1,867
Joined
2 yr. ago

  • Then flush everyone from director up, and investigate middle management, and put people in that actually have some fucking ethics. Jesus H Christ.

  • Well, I for one think some rogue at Boeing is behind the Epsteining of this guy. The company is definitely run by psychopathic crooks and has been for a while and I hope these fuckers all go to jail and the company fixed before more people die.

    Idk about these accounts you blocked... but I am always going to advocate for at least being self-aware of being loosey-goosey with one's reasoning. Maybe it is compulsion, maybe it is the decades wasted being religious that have led me to detest careless epistemology that leads to specious conclusions. Then again ... if COVID taught me nothing, it should have taught me that efforts in this area are probably pointless. I must like swimming upstream. I seem to do it all the time.

  • My pet theory: Some extra dirty psycho at Boeing probably had him killed. Probably to cover up specifics about themselves. It seems pretty clear Boeing is rotting at the head and has been for decades. All these issues that have come up since MAX are the result of deeply systemic problems, stemming from crooked, greedy psychopaths at the top.

    But in the interests of being as rational and honest about this as possible, let's also not forget that this article is based on her claim, and she's the only one (so far) to make it. People have been known to seek attention with bullshit. It's evidence, yeah, is it really unimpeachable? Well.....

    Think about it like this: if there was a dated and notarized statement in his handwriting saying the same thing that she claims he told her, that would be more trustworthy.

    But again, pet theory, some Boeing sicko was covering their own ass by having him Epsteined. Totally plausible.

    I don't think this is the last we will be hearing about this.

  • Same. But mine still says not to laminate.

  • Idk. Maybe because there's only a few pieces of info on it. Someone would say "why do you need to use a whole sheet of paper for just this?"

  • You probably want to look for books on reverse engineering. And a book on assembly for your CPU.

    I learned assembly language for VAX-11 (this was like 30+ years ago) in a CS class. We also learned 6502 assembly in a computer engineering class. Neither book would help you. You want a book specific to whatever CPU you're using.

    Now, I never took it, but friends in college took a CS Compilers course where they learned the basics of writing a compiler. But that's not what you're talking about though it might help.

    Trying to understand what a program does is reverse engineering. And a tool like IDA Pro would help you understand subroutines, variables, flow, library calls, and so on.

    A debugger will be invaluable for seeing a program execute one instruction at a time.

    You would need to know the assembly language for your CPU. And it would help to become familiar with certain patterns. I haven't done much assembly (but I have done assembly on a few different CPUs) nor much reverse engineering so I'm not sure I can lend a whole lot of insight there.

    As you learn assembly instructions, you will start to understand how loops, subroutines, if/then/else, and other things are accomplished for your CPU.

    For example, if/then/else and loops are often accomplished with conditional branching. The conditions are based on CPU flags (bits in the Status Register) that are set by a comparison instruction. You'll start to recognize how if/then/else and loops and other things are commonly implemented in assembly (without necessarily having to study the compiler; it will be obvious without knowing anything but assembly).

    Another example might be how C structs are implemented. Some CPUs provide convenient memory addressing modes for structs, some don't. Nearly all I am familiar with provide a convenient way to reference arrays with a simple index.

    Subroutines are jumps to a set location and at the end of that code is a return instruction. Usually registers have to be saved when jumping and restored when returning. Arguments to the subroutines are pushed on to the stack either by value or by reference. Return value is provided through some convention (machines with lots of registers might always use one particular one for return).

    I guess bottom line, learn assembly for your particular CPU, then take a crack at using a debugger and disassembler / reverse engineering tool.

    I'm not entirely sure I follow why that is needed to learn how to do branching in forth but I only vaguely remember that language. Maybe if I did it would be more clear.

    Anyway I hope this helps at least a little.

  • As the other commenter said, you want to learn about programming principles. Like, low coupling or don't repeat yourself.

    How long is your longest program? What would you say is a typical length?

    You say your code is "bad" -- in what ways? For example:

    • Readability (e.g. going back to it months later so you go "oh I remember" or "wtf does this do?!"
    • Maintainability (go back to update and you have to totally rework a bunch of stuff for a change that seems like it should be simple)
    • Reliability (mistakes, haphazard "testing", can't trust output)
    • Maybe something else?
  • I guess if you are unlikely to go back and change it, or understand how it works, then sure. And yeah that happens.

    I write scripts and utilities like that. Modularity is overkill although I do toss in a comment or two to give a hint to future me, just in case.

    Although tbf, I took plenty of CS classes and some of the instructors beat best practices into our heads... So writing sloppy, arcane, spaghetti code causes me to flinch...

  • Exactly. Systemic issues. That's my expert (fan of Air Disasters) opinion.

  • It's on my list to do this at some point.

    Speaking of radio.... Any ham people on here?

  • Anyone play "the longing" ? It looks like it ought to be really chill. I guess I will have to find out.

  • Not just you at all. I read the Top 6-Hour usually, so I have been blocking communities and filtering out keywords left and right to try and reduce the constant deluge of doom. (Yes it is working)

    It's like, yeah I know we are totally hosed, I don't need reminders every 10 milliseconds. All it leads to is learned helplessness and depression.

  • I was a sysadmin, once....Not for long.

  • No I'm sure most of the people are ok. Just throw Orban in the lake. Metaphorically of course. With a metaphorical boat anchor tied on.

  • Did...did you sit on your cat?? Wtf am I seeing here?

  • Because garbage people who abuse power and exploit people and are sociopaths hang together?

    Really it's a reflection of our society at large, like it or not.

    Otherwise President Orange "grab them by the pussy" Rapist would have bombed in 2016.

    Remember the reactions of some Trumper women? It's normal, it's locker room talk. Boys will be boys or whatever the fuck? Yeah rape is normalized, expected for many. Idk if it is accepted or if these people are resigned to it.

    But that's got to change. Me too movement was a catalyst for more change. It will take a long time. But we gotta keep pushing.