Comments by "Christopher Bruns" (@user-td4pf6rr2t) on "LaurieWired" channel.

  1. 25:19 79 spaces per line was the best practice for C, and 1024 in total since allocating memory anyways being almost exactly 13 lines I think per chunk.
    2
  2. 9:02 If you think about it though to demo s best practice tutorial having prints before return 0 would not make sense iterating through the process unless you exit successfully since the printf WOULD technically error but being beings of habit just assume the exit success will be included in the end of the guide. Also doesn't Hello World chronologically not make sense since it was the one of the pair who wrote C to first use Hello World in the meme setting. If this true I would assume assembly predates C since Compiler. These are all just assumptions.
    1
  3. If pan were a gender would AI consider this video malicious. Is what I want to know 4:30 is this for dynamic allocation of memory and logging for debug?
    1
  4. 10:38 Woah woah woah, I think the one post frame should be disqualified, due to no ideas. #include <stdio.h> #define peace return #define out 0 #define mind ; int hope() { if (peace out) { printf("World\n"); return out; } } int main(){ char music[] = "Hello "; char *lyrics = "Obfuscated C!"; printf("%s", music); printf("%s\n", lyrics); hope() mind return out mind }
    1
  5. 14:00 man 1 is for user command while man 8 is primarily for root account. each section is specific and is part of the underline document regarding to the object orientation and understanding the man page. So an example would be if it you are reading from man 1 it is assumed the user assumes standard user privileges while pages from section 8 the literature would not include the permissions while assuming root during the explanation/documentation... Cheers!
    1
  6. If only somebody would tell this to ChatGPT. By definition they should be the only professional were sucky code should be expected. Since most other IT paths the ethical solution to the why their code shouldn't stink compared to devopts is that they shouldn't of been poking about the signal handlering and processes id's to start with. Duh... secuirty professional by definition specializes in reading in-between the lines ('or string literal depending if you happen to be discussing this with a compiler , but anyways...'), what i am saying is i think security technician both responsible for understanding best practice and at scale but not in production. if there code was kemp would just be the right answer is the short answer. Everyone else would be unethical or illegal tearing apart what ever the scope is/was in this hypothetical - right [[ ... ,?]] But it is a language barrier and nothing to do with the individual or there code. 98.9% of time while at the same time the other end of spectrum is fringe science and not electively volunteered association in a professional ecosystem. Final answer. 15:31 or adversarial with positive reward mechanisms sounds fun too. Within good taste of coarse.
    1
  7. Recurse. This is ironic function name?
    1
  8. man -k, so I read the documentation about this for linux. Not i know less. Cheers.
    1
  9. Ill donate for a dissect of /bin/false or any other non-login shell binary/ 4:17 So like boilerplate for 8 bit byte for 7bit ascii and standard error handling and debug flag pretty much is this? 4:43 What do you mean. Computers Read and Write to Files. Nothing less and nothing more. What is this "something more you say",mean? 7:06 and zero division errors.
    1
  10. 5:43 This is snuff tube all of a sudden. 7:37 Or Hello world at scale would make for fun video. I jeard the algorithm thunk.
    1
  11. dang back-end developers,..
    1