Message from @DanielKO
Discord ID: 429431306011541509
Probably why my college nailed the "It's all in the design" point in with a sledgehammer into our brains
Yep, bad design is usually what ruins everything.
Programmers that never looked at any library, any API, don't know what the usual names of things are.
Then they shove a bunch of generic names everywhere with no meaning.
It's interesting to see, after you go through a lot of bad code, how important having a shared vocabulary is.
I worked on a project where a `Connection` object was actually a tuple, and had one method, named `cleanup()` that manipulated data in another class.
And the class that would usually be called a `Connection`, with methods analogous to `send()` and `receive()` was called `Interaction`.
Of course, the methods weren't called that, they were called `push()` and `process()`.
push()
It was almost as if every name of class and method was created to mislead anyone else working with the code.
So yeah, don't be "that guy" that doesn't know the name of things that everyone else knows.
You should be curious to do things on your own without needing somebody to hold your hand, but also you should constantly check what other people created, to make sure you're not doing things completely wrong.
How did you mark up the text?
Google "Discord markdown".
That took all too long
Covered out the `http://localhost`?
Its my public ip
Share it
Also, chrome? Really?
Might as well just use JS
What do you use? Safari?
One has to wonder, how much energy we're wasting worldwide because so many websites now offset computation and rendering to the client side.
@Durtle02 Use firefox
@Deleted User This is my life tonight.
```
.data
print: .asciz "%d\n\000"
scan: .asciz "%d\000"
.comm A, 32, 32
.comm B, 32, 32
.text
addr_A: .word A
addr_B: .word B
addr_scan: .word scan
addr_print: .word print
.global main
main:
stmfd sp!, {r0-r1, lr}
ldr r0, addr_scan /* r0 <- &addr_scan */
ldr r1, addr_A /* r1 <- addr_A */
bl scanf /* calls scanf */
ldr r0, addr_scan /* r0 <- &addr_scan */
ldr r1, addr_B /* r1 <- addr_B */
bl scanf /* calls scanf */
ldr r0, addr_A /* r0 <- addr_A */
ldr r0, [r0] /* r0 <- *r0 */
ldr r1, addr_B /* r1 <- addr_B */
ldr r1, [r1] /* r1 <- *r1 */
cmp r0, r1 /* compare r0 and r1 */
movgt r1, r0 /* move greater to r1 */
ldr r0, addr_print /* */
bl printf /* calls printf */
ldmfd sp!, {r0-r1, pc}
```
@meratrix nigger is that assembly code
arm assembly my dude
why the fuck are you showing me that cancer
cause it's my cancer
two can play it that way nigger
``bl printf /* calls printf */`` comments could use more redundancy
I guess it's useful for people not familiar with the mnemonics.
But then, `cmp r0, r1 /* compare r0 and r1 */` ? That's just retarded.
Gotta comment every line otherwise TA's give me shit
they should be more worried the students know what their code means
Back when I did assembly homework, I had to normalize a single-precision floating point number on a toy computer, that had only 256 bytes of RAM. And we had to write our own assembler.
i'm learning 68k but im gonna learn ARM after that
And whoever used the least instructions got bragging rights.
which computer
Oh, one that my professors used, I think it was created by a student a few years prior. Don't even remember the name.
It was your typical two operand instructions, 4-bit instructions.
interesting strategy. too obscure to cheat?