Training fresher in c

[_AK_]

I don't have much idea in it but what you can do is to get a small application (small but where all the concepts can be programmed basic plus advanced)and divide the tasks or modules to them. Ask them to develop that adhering to the normal coding practices.

Apurva Kaushal

[CPallini]

Oh, C is that simple! Without frills like ++ or funny musical accidentals. :-D

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]

[Roger Wright]

There are still some C articles here in the C/C++ Forum, though you'll have to search for them the hard way. Use them as guides to develop projects, and as examples for the students to use for reference. Since C is commonly used for hardware control, you might implement a software simulator for some hypothetical hardware device, then set up a series of challenges for them to implement which interact with the "hardware." This would require them, typically, to use bitwise operations, direct I/O control, basic data types, console operations, file I/O, and other basic concepts. Another approach would be to select concepts you want to teach, then design small problems for them to implement. Some tasks might include bulding a console interface to collect, sort, and store user input, perform a FFT or CRC32 on file data, display a line graph, etc. Each task should build on previous lessons and add new concepts; students tend to forget prior lessons if each assignment is standalone. Just a few thoughts; I've never used C for a project, as there were always easier ways to do the task, or customer requirements that specified another choice. But training techniques apply to a broad range of subjects, and I've done a lot of training. Tell them what you expect them to learn, teach them the material, give them a challenge to apply what they've learned, review what they've done right and wrong, repeat until they get it mostly right, then move on to the next topic. The most important part is the doing; lots of practice is key to learning.

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[Henry Minute]

Swathee wrote:

They are not billed to the customer

Of course they are billed to the customer! If you pay them, that is. Every cost to your company gets billed to your customers, they are not all itemised is all. It's like BOGOF offers, of course you aren't getting one free, you're just paying for it somewhere else, or they got it dirt cheap. Incidentally why is my 'H' key not working today, I keep typing te and tey. End of rant! :)

Henry Minute If you open a can of worms, any viable solution *MUST* involve a larger can.

[Dan Neely]

Or creative's audio driver division. Everyone rips on HP (for good reason) but Creative's drivers were bad enough to trigger an OS architecture change. Vista yanked the sound system out of the kernel so that creative bugs wouldn't BSOD windows any longer.

Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall

[Single Step Debugger]

Go for some cryptography – this is a reserved C area; DES and 3DES are not so complicated but implementing them will cover most of the important concepts in C language.

The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.

[El Corazon]

Anna-Jayne Metcalfe wrote:

The ones who come back with suggested improvements a week later are the ones you would do well to train...the rest will probably have run away by then.

So THAT is how I managed to be different.... hmmmm.... my boss always wanted a test to find another "me". That is exactly what I did adding Trig functions to RPG II, creating AI interface in Cobol for a Chess game. :) And then the first thing I did with C was create a QwikDisplay library for fast text/ModeX graphics that was thread-safe and had an interruptable multi-threading interface under DOS. Now the only problem is... is still how to find such a person.... :laugh:

_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."

[Roger Wright]

El Corazon wrote:

how to find such a person.

Have you checked with the lab that created Dolly? [insert forgotten sheep smiley here]

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[El Corazon]

but can the world suffer having two or more of me? :)

_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."

[Anna Jayne Metcalfe]

El Corazon wrote:

So THAT is how I managed to be different....

I know the feeling. :rolleyes: Within a month of gaining access to a CP/M machine for the first time I was happily writing system software in assembler and dogfooding public domain compilers... :-\ The only difference from the scenario I described in my original post was that I didn't use any significant reference books to do it. ;)

Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"

[Roger Wright]

I don't remember there being any reference books for CP/M. :-D I do remember fondly my first computer, but alas there were no tools. The O/S I wrote myself, using the Intel 8080 spec sheets for a reference. Things were so much simpler then... :sigh:

"A Journey of a Thousand Rest Stops Begins with a Single Movement"