Message from @DanielKO

Discord ID: 428962898879184897


2018-03-28 15:31:27 UTC  

Whoever curated this "best book" content clearly hasn't read many books on a given subject.

2018-03-29 03:17:26 UTC  

it won't help me ``learn all of c++ in 24 hours``??

2018-03-29 03:18:45 UTC  

I'm learning programming via the internet and I can definitely say it would be better to learn in school

2018-03-29 07:25:07 UTC  

The most important thing when learning a new language is how you should use it. That takes time.

2018-03-29 07:27:26 UTC  

For C++, the best source is Stroustrup's book.

2018-03-29 07:29:34 UTC  

Also, figure out what kind of programming student you are. Do you need somebody to tell you what to do next? Or do you feel like trying to do things on your own?

2018-03-29 07:31:19 UTC  

The former tends to turn out to be mediocre programmers, while the latter tends to become cowboy programmers with no common sense about code quality.

2018-03-29 07:35:37 UTC  

```cpp
if(former){
return shit;
}
else{
return shit;
}
```

2018-03-29 16:27:41 UTC  

What I meant was, if you just sit down and start coding nonstop, it's too easy to become oblivious about how bad your code is.

2018-03-29 16:36:09 UTC  

Probably why my college nailed the "It's all in the design" point in with a sledgehammer into our brains

2018-03-29 16:40:32 UTC  

Yep, bad design is usually what ruins everything.

2018-03-29 16:40:50 UTC  

Programmers that never looked at any library, any API, don't know what the usual names of things are.

2018-03-29 16:41:10 UTC  

Then they shove a bunch of generic names everywhere with no meaning.

2018-03-29 16:41:52 UTC  

It's interesting to see, after you go through a lot of bad code, how important having a shared vocabulary is.

2018-03-29 16:42:33 UTC  

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.

2018-03-29 16:43:20 UTC  

And the class that would usually be called a `Connection`, with methods analogous to `send()` and `receive()` was called `Interaction`.

2018-03-29 16:44:25 UTC  

Of course, the methods weren't called that, they were called `push()` and `process()`.

2018-03-29 17:02:19 UTC  

push()

2018-03-29 17:04:44 UTC  

It was almost as if every name of class and method was created to mislead anyone else working with the code.

2018-03-29 17:05:24 UTC  

So yeah, don't be "that guy" that doesn't know the name of things that everyone else knows.

2018-03-29 17:06:29 UTC  

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.

2018-03-29 17:48:47 UTC  

How did you mark up the text?

2018-03-29 17:56:45 UTC  

Google "Discord markdown".

2018-03-30 19:47:11 UTC  

That took all too long

https://cdn.discordapp.com/attachments/423219052849397773/429366000173973525/Capture_2018-03-30-15-46-38.png

2018-03-30 19:50:07 UTC  

Covered out the `http://localhost`?

2018-03-30 19:50:24 UTC  

Its my public ip

2018-03-30 20:41:33 UTC  

Share it

2018-03-30 20:42:03 UTC  

Also, chrome? Really?
Might as well just use JS

2018-03-30 21:48:16 UTC  

What do you use? Safari?

2018-03-31 00:06:41 UTC  

One has to wonder, how much energy we're wasting worldwide because so many websites now offset computation and rendering to the client side.

2018-03-31 00:12:54 UTC  

@Durtle02 Use firefox

2018-03-31 01:43:59 UTC  

@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}

```

2018-03-31 01:45:29 UTC  

@meratrix nigger is that assembly code

2018-03-31 01:45:37 UTC  

arm assembly my dude

2018-03-31 01:45:41 UTC  

why the fuck are you showing me that cancer

2018-03-31 01:45:48 UTC  

cause it's my cancer

2018-03-31 01:46:39 UTC  

two can play it that way nigger

2018-03-31 01:49:19 UTC  
2018-03-31 02:25:47 UTC  

``bl printf /* calls printf */`` comments could use more redundancy

2018-03-31 02:27:54 UTC  

I guess it's useful for people not familiar with the mnemonics.