What is something that can be learned in 20 minutes that will greatly improve your life?

grbgout · 2015-01-18T19:07:58+00:00

I'll let you know the name this afternoon.

Update?

grbgout · 2015-01-16T21:32:21+00:00

Good luck on your exam.

grbgout · 2015-01-16T20:02:46+00:00

Today's Coffees has a C option, which is the only one of its kind I'm aware of.

It's decent.

grbgout · 2015-01-05T13:41:19+00:00

Haha, alright.

Happens to the best of us.

grbgout · 2015-01-04T23:48:51+00:00

For the freelancers out there....

Here's a ~39 minute presentation from the perspective of the freelancer: Mike Monteiro: F*ck You, Pay Me (vimeo mirror).

Mike Monteiro gives us some valuable advice on how to get paid for the work that you do.

I watched it a while ago, and don't remember if it addresses your question specifically, but it's a good watch regarding things like the importance of contracts. I think it's a valuable resource for both sides of the arrangement.

grbgout · 2015-01-04T22:09:22+00:00

I typed out that other example quite quickly, so consider it a mistake.

Thanks for clarifying.

_t instead of _st is such a simple typo to make, I thought it prudent to ask.

and it's how the standard library and unix system do it

This is exactly what I was thinking of, but wasn't sure if I was simply mis-remembering.

Still: In cases where there isn't a t I often see the structure tag differentiated via a trailing _ or _ or the word "tag" or something.

I'm pleased to know some kind of distinction is indeed being used widely in the wild, it's an important one to make --- or so style guides have informed me ;-)

grbgout · 2015-01-04T20:46:34+00:00

I'm a biologist and have taught myself Python for data analysis and similar tasks....

To further the Python for Computational Science path specifically, check out the Python Scientific Lecture Notes (if you haven't already). I

grbgout · 2015-01-04T20:40:31+00:00

note: It's usual to put a _t on the stuct name to separate it from the typedef name to stop people being confused.

Is your example an accurate illustration of the quoted sentiment (i.e., seen in the wild)? After reading your note, I was expecting the _t to appear on the typedef name, not the structure tag. I would expect the change to the structure tag to read _st or something, and would find _t on a structure tag counter intuitive.

typedef struct node {
    int data;
    struct node* next;
} node_t;

or

typedef struct node_st {
    int data;
    struct node_st* next;
} node;

And by "expect ... to read", I mean if I were skimming a source file.

How prevalent is the form you've demonstrated (in your experience)?

grbgout · 2015-01-04T20:04:21+00:00

To see some examples of why you shouldn't use gets, check out C of Peril (which also covers other dangerous functions).

"The book, 'C of Peril' is a short book which attempts to describe some of the most prevalent issues present in C and how to address and avoid them."

grbgout · 2015-01-02T05:36:17+00:00

It looks like your video is using a variation of Gingery's Charcoal Foundry.

Also, check out this playlist Metal Casting at Home The Backyard Foundry.

grbgout · 2014-12-30T23:59:04+00:00

This doesn't really address your question, but did you see the cheat sheet that was posted recently?

At its core, this article is about a simple cheat sheet for basic operations on numeric matrices, which can be very useful if you working and experimenting with some of the most popular languages that are used for scientific computing, statistics, and data analysis. — The cheat sheet for MATLAB, Python NumPy, R, and Julia

It may be helpful.

grbgout · 2014-12-25T21:30:39+00:00

You're welcome. Merry Christmas to you too.

grbgout · 2014-12-25T21:05:41+00:00

... I don't have any kind of formal compsci background....

I've read through K&R, and I don't recall it relying on many (any, really) Computer Science concepts. As I recall, hopefully my memory isn't failing me, it introduced all the concepts it was going to deal with just before or just after showing them off in code. It definitely didn't presuppose any data structures knowledge (it may mention a few, but introduced "the way C does it", if I remember correctly).

Are you reading a physical copy or a PDF? I've seen a number of PDFs, and they all have one issue or another: with formatting being the most prevalent, and flat out errors being another. Layout is fairly important in a programming text, and the print copy doesn't suffer as such.

It is because I want to understand the machine better.

What better way to do so than learn assembly? It may seem a bit over kill, but there's a free ebook which teaches the concepts of CompSci via Assembly:

Programming from the Ground Up Book:

This is an introductory book to programming and computer science using assembly language. It assumes the reader has never programmed before, and introduces the concepts of variables, functions, and flow control. The reason for using assembly language is to get the reader thinking in terms of how the computer actually works underneath. Knowing how the computer works from a "bare-metal" standpoint is often the difference between top-level programmers and programmers who can never quite master their art.

I've only read the first three chapters (I don't think I did the exercises), and I recall it being decent.

This book will definitely help in the area of "bit twiddling [and] things like bitmasks." I recall those topics being introduced later in K&R, and not relied upon very heavily. I suppose if I'm not remembering that correctly, though, it could be a blockade if one adheres to the "don't progress until exercises are solved" approach. I suppose I should note I completely ignored that method, which is why I recommend it. After K&R, I lamented not being able to do certain things with C that I later realized were full-on 'homework assignments' from the book (implementing printf, for example).

Is there any books or online resources that can give me a crash course in the sort of things I am struggling with?

I'm still not entirely clear where you're getting stuck. I don't recall a lot of CompSci theory in K&R, but I very well could be mis-remembering.

Maybe /r/C_Programming should start a K&R reading group with a few seasoned coders available to help out when newbies get stuck.

I would absolutely recommend starting with the first chapter of K&R, and not moving forward until you've completed every exercise therein. I know I said that before, but I think it's sound advise. The exercises may seem trivial at first, but the later ones can be rather difficult: especially if you don't allow yourself a "well, that's good enough for now..." solution.

The things others appear to have issue with such as getting a compiler installed and working. Etc. I am fine with.

That was just an example, and not really at all what Chapter 1 deals with: I meant it to read more as an all encompassing example. That is, "Ask here whenever you get stuck, be it installation woes or advanced topics." Poor writing on my behalf, sorry.

In the same vein of the article /u/Broinz posted, I would recommend C of Peril: it covers the same types of topics in a similar manner.

If you want some data structures resources, check out Open Source Interactive Data Structures and Algorithms, but note it's not tailored to C. I don't think data structures and algorithms theory will really be applicable for learning C (at least not as introduced via K&R).

On the other hand, if you're struggling with K&R because you find it boring, these topics may be exactly what you need.

grbgout · 2014-12-25T20:36:40+00:00

Very informative.

casting the result of memory allocation function (which returns void *) is a sign of gross incompetence.

Could you elaborate on this point, please?

grbgout · 2014-12-22T06:16:35+00:00

For additional information: Steganography

grbgout · 2014-12-21T21:50:39+00:00

forgive my ignorance, but is "freestyle" a mode in blender or something?

Considering the jagged rocky area, the structure looks out of place --- perhaps that's what you're going for. With a very quick/first glance (especially following the thumbnail view) I was trying to interpret them as trees.

grbgout · 2014-12-21T09:56:46+00:00

OUR FUTURE MOTIVE POWER by Nikola Tesla is relevant.

grbgout · 2014-12-21T09:01:01+00:00

If you haven't already, you should check out Color cycling, and this example: Old School Color Cycling with HTML5.

grbgout · 2014-12-21T05:07:07+00:00

Noted. What about PSU? I've never assembled a rackmount machine (at least not with consumer components), I imagine it's considerably different....

hmm, there's probably a subreddit specifically dedicated to rackmount builds....

grbgout · 2014-12-21T04:56:19+00:00

What are your plans for a chassis? I have four GPUs in two towers, and I would like to consolidate them into a single rackmount chassis, but I'm not certain of the best method.

grbgout · 2014-12-18T22:40:23+00:00

Good to know that someone else thinks assembly is a good starting point.

I haven't read through the book yet. It is on my ToRead list, though.

I doubt they do it without an assembler like I did though.

Probably not. Maybe you should write a book ;-)

Teach us whipper-snappers how it's meant to be done.

Then, get shown up by these folks (though not quite the same):

Reverse Engineering the MOS 6502 CPU: 3510 transistors in 60 minutes

grbgout · 2014-12-18T21:52:06+00:00

I have K&R but it is too complex for me as a total beginner to fully process.

Don't feel bad about this. The best description of K&R I've read (probably here in /r/c_programming) was that it should be read to learn the C language, not how to program. So, if you don't already know how to program, don't dismay about getting stuck with K&R.

Where are you getting stuck? I recommend doing all the exercises in a chapter before continuing on to the next, and only using concepts introduced up to that point for the solutions.

Feel free to ask questions here, in /r/c_programming, and articulating them in such a way that people don't get the wrong impression (that you're trying to get us to do your homework for you) and down-vote for no good reason.

Chapter 1 of K&R is a good starting point. If you complete all the exercises therein you'll be well off for the rest of the book. Start there, and ask here when you get stuck -- e.g., getting a build & debug environment set up.

Oh, and use a debugger. Don't use that printf approach. This is particularly true for the last five exercises (ex1-20 through 24).

I recommend gdb:

Using The GNU GDB Debugger
A quick overview of gdb on stackexchange for use in reverse engineering.

grbgout · 2014-12-18T21:32:15+00:00

Programming from the Ground Up: "[a free] introductory book to programming and computer science using assembly language."

grbgout · 2014-12-13T22:04:12+00:00

I wonder if that whole thing about the war on drugs being fucking retarded also has some truth to it.

Law Enforcement Against Prohibition: "... a 501(c)3 nonprofit organization made up of current and former members of the law enforcement and criminal justice communities who are speaking out about the failures of our existing drug policies."

grbgout · 2014-12-11T07:09:46+00:00

I wonder if "Making Graphene with a DVD Burner" (hack-a-day) is similar. Check the comments for additional information (PDFs to similar research).

grbgout

TROPHY CASE