These are chat archives for learnclang/general

28th
Dec 2014
Marcus Ottosson
@mottosso
Dec 28 2014 10:44
This channel is open to the public, anyone can join and chat. :)
Marcus Ottosson
@mottosso
Dec 28 2014 11:30
@davidmartinezanim Talk here? :)
David Martinez
@davidmartinezanim
Dec 28 2014 11:30
yep
Marcus Ottosson
@mottosso
Dec 28 2014 11:31
Once we're a few more folks, I'd expect this area to be where things goes down.
David Martinez
@davidmartinezanim
Dec 28 2014 11:31
Does markdown formatting work here as well? that is neat
Marcus Ottosson
@mottosso
Dec 28 2014 11:31
And keep the organisation room for non-public topics.
David Martinez
@davidmartinezanim
Dec 28 2014 11:31
absolutely!
Marcus Ottosson
@mottosso
Dec 28 2014 11:31
Yeah, you can do new-lines as well, there's a button the right of the text-area.
David Martinez
@davidmartinezanim
Dec 28 2014 11:32
sweet, thanks
Marcus Ottosson
@mottosso
Dec 28 2014 14:26
Added @instinct-vfx: Hi!
Marcus Ottosson
@mottosso
Dec 28 2014 16:03
Added @tokejepsen!
Let's start by getting all cards on the table - why do you want to learn C and/or C++?
What are you looking to achieve, what is most attractive? Performance? Libraries, like OpenGL or the Maya API? Applying to more programming positions in R&D?
Marcus Ottosson
@mottosso
Dec 28 2014 16:09
Personally, I'm looking to build interactive animation tools (graph editors, signal processing) and geometry manipulation (deformers, point simulation) and think C is a good stepping stone to C++ which is a good stepping stone to OpenGL and from there the sky is the limit!
Toke Jepsen
@tokejepsen
Dec 28 2014 16:14
think my goal is initially to get to grips with Maya api, but long term is to not be scared of hard-core programming
Marcus Ottosson
@mottosso
Dec 28 2014 16:16
True that! Compiled code always eludes me too; would be good to be able to do the dance and get what the fuzz is about.
Marcus Ottosson
@mottosso
Dec 28 2014 17:07

Peer Review

I came to think of probably the most important benefit of learning C this way; Peer Review! Basically, having someone else read your code and follow your progress, it encourages better and more thorough code.
Toke Jepsen
@tokejepsen
Dec 28 2014 17:35
would like to get better at commenting my code, so im in:)
Marcus Ottosson
@mottosso
Dec 28 2014 17:35
:)
Then, about your question @tokejepsen, how we'll complete tasks. Spontaneously, I'd stray from making it too academic and lean more towards practical projects that ideally have a direct usefulness to our goals.
Marcus Ottosson
@mottosso
Dec 28 2014 17:45

This would be an example of an academic project.

"Reverse an array of characters"

I don't think we should do any of that, as there already is plenty available.

Instead, I'd suggest we try projects in which we could help each other and try different routes to find which is better suited to us.

Such as:

"Open a frameless window with a green background"

Toke Jepsen
@tokejepsen
Dec 28 2014 18:46
that sounds good to me:)
Marcus Ottosson
@mottosso
Dec 28 2014 19:14

current repository

I'm considering having a repository on GitHub called current for the currently running project, and rename it once complete, to an incremented number of projects completed in the past. E.g.

  • current
  • 2-helloworld
  • 1-compileandrun

That way, we'd always stay on top of which project is currently running, and we'd be able to refer back to projects by their number, which is assigned as soon as we complete it.

Thoughts?

Toke Jepsen
@tokejepsen
Dec 28 2014 20:37
i like it. anybody coming in later, can run through the repos to get up to date