Teaching in the field
-
I work with an electrical engineer and he's learning software development in the field as he goes. I often work with him, and am teaching him C++. It can be challenging because there are things he needs to know by certain deadlines, and he's got about 2 hours worth of stamina for a lesson at any given time. He knows a little C, still new to classes, understands pointers (sort of), gets static members to the point where he wished he knew they existed in previous endeavors of his. I have to teach him C++ templates and avoid STL containers because I've only got two hours to convey the fundamentals. Also he's in Eastern Europe right now, and I'm in North America, just to up the difficulty setting a bit. *cracks knuckles* *sips coffee* I got this.
To err is human. Fortune favors the monsters.
honey the codewitch wrote:
*sips coffee*
smokes a big bowl, I mean huge bowl Now, I got this.
-
honey the codewitch wrote:
*sips coffee*
smokes a big bowl, I mean huge bowl Now, I got this.
Heh. Whatever works for folks.
To err is human. Fortune favors the monsters.
-
If you've done it before, you know that teaching is a dance for two. Even the best teachers have useless students. I hope in your case things will turn out well. On the other hand, if you are contracting people from Eastern Europe, it might be easier to find someone that already knows C++. In those parts of the world they are dime a dozen - I am a living proof :D (not that I would value myself at 0.10/12$) Good luck anyways!
Mircea
Mircea Neacsu wrote:
On the other hand, if you are contracting people from Eastern Europe
He's temporarily there on vacation - he's from the states. And he brought *me* the project - brought me on as a consultant because he knew he was out of his depth. Also he's a good student. First, he knows his limitations. Second he's ambitious and dedicated without being "hold my beer" about it - he's a good engineer as it is. We'll be fine. :)
To err is human. Fortune favors the monsters.
-
I work with an electrical engineer and he's learning software development in the field as he goes. I often work with him, and am teaching him C++. It can be challenging because there are things he needs to know by certain deadlines, and he's got about 2 hours worth of stamina for a lesson at any given time. He knows a little C, still new to classes, understands pointers (sort of), gets static members to the point where he wished he knew they existed in previous endeavors of his. I have to teach him C++ templates and avoid STL containers because I've only got two hours to convey the fundamentals. Also he's in Eastern Europe right now, and I'm in North America, just to up the difficulty setting a bit. *cracks knuckles* *sips coffee* I got this.
To err is human. Fortune favors the monsters.
-
Quote:
I have to teach him C++ templates
Do not leave out meta programming... :laugh:
"In testa che avete, Signor di Ceprano?" -- Rigoletto
We actually touched on the concept a little today before he tapped out. He doesn't need to learn it - more just recognize it when he sees it. :)
To err is human. Fortune favors the monsters.
-
I have been too long in the industry to know how this kind of things will end : On your day off there will be a quick metal piece that need to be urgently welded, it will be done because urgent and stuff, and the welded axle of the school bus will not be well welded, will break and the bus will violently hit two walls, run through the kindergarten, and fall from a cliff. :)
This applies to every new dev. Even you! It’s called experience and it’s why you have more experienced people in charge of juniors. If he crashes the bus that’s not just his fault. It’s also the witches responsibility. That’s just the way it is. Edited to not be such a dickhead. Sorry!
If you can't laugh at yourself - ask me and I will do it for you.
-
We actually touched on the concept a little today before he tapped out. He doesn't need to learn it - more just recognize it when he sees it. :)
To err is human. Fortune favors the monsters.
-
I work with an electrical engineer and he's learning software development in the field as he goes. I often work with him, and am teaching him C++. It can be challenging because there are things he needs to know by certain deadlines, and he's got about 2 hours worth of stamina for a lesson at any given time. He knows a little C, still new to classes, understands pointers (sort of), gets static members to the point where he wished he knew they existed in previous endeavors of his. I have to teach him C++ templates and avoid STL containers because I've only got two hours to convey the fundamentals. Also he's in Eastern Europe right now, and I'm in North America, just to up the difficulty setting a bit. *cracks knuckles* *sips coffee* I got this.
To err is human. Fortune favors the monsters.
May I inquire the number of lines of code he is expected to write and the duration of task. -Best PS When I began work at a company learning intel 8088 assembler the first thing I did was type RET AL I hope and trust your student is a better C++ learner than I as assembler. PPS My current sage advice to any student is below though no doubt yours is superior. As for myself I find it very helpful to design C++ code in a manner which suits "ease of use" and "ease of understanding" and then figure out the language details to make it so. It is all merely a matter of providing all necessary information to compiler and to one's own code to perform requested task whether it be to compile or to execute. So in summary I recommend ask yourself for each task you wish to execute what is the most "easy" manner to specify said execution what information is needed from whence does that information come how it should be processed/calculated with/utilized where it should be stored/passed and its types
-
May I inquire the number of lines of code he is expected to write and the duration of task. -Best PS When I began work at a company learning intel 8088 assembler the first thing I did was type RET AL I hope and trust your student is a better C++ learner than I as assembler. PPS My current sage advice to any student is below though no doubt yours is superior. As for myself I find it very helpful to design C++ code in a manner which suits "ease of use" and "ease of understanding" and then figure out the language details to make it so. It is all merely a matter of providing all necessary information to compiler and to one's own code to perform requested task whether it be to compile or to execute. So in summary I recommend ask yourself for each task you wish to execute what is the most "easy" manner to specify said execution what information is needed from whence does that information come how it should be processed/calculated with/utilized where it should be stored/passed and its types
We don't count lines of code, and it's a year long project, though at some point - probably 9 months in, we'll be ready to freeze development. I'd really like my C++ code to be easier to understand, but I don't write efficiently that way, because I don't think efficiently that way. I use GP. People don't like GP even though with C++ it's what's for dinner. So it's comments to a degree but I accompany my code with external documentation about it.
To err is human. Fortune favors the monsters.
-
We don't count lines of code, and it's a year long project, though at some point - probably 9 months in, we'll be ready to freeze development. I'd really like my C++ code to be easier to understand, but I don't write efficiently that way, because I don't think efficiently that way. I use GP. People don't like GP even though with C++ it's what's for dinner. So it's comments to a degree but I accompany my code with external documentation about it.
To err is human. Fortune favors the monsters.
sorry to ask: what is "GP" here? GNU C++?
diligent hands rule....
-
sorry to ask: what is "GP" here? GNU C++?
diligent hands rule....
No, sorry, I mean Generic Programming.
To err is human. Fortune favors the monsters.
-
I work with an electrical engineer and he's learning software development in the field as he goes. I often work with him, and am teaching him C++. It can be challenging because there are things he needs to know by certain deadlines, and he's got about 2 hours worth of stamina for a lesson at any given time. He knows a little C, still new to classes, understands pointers (sort of), gets static members to the point where he wished he knew they existed in previous endeavors of his. I have to teach him C++ templates and avoid STL containers because I've only got two hours to convey the fundamentals. Also he's in Eastern Europe right now, and I'm in North America, just to up the difficulty setting a bit. *cracks knuckles* *sips coffee* I got this.
To err is human. Fortune favors the monsters.
Having graduated as a mechanical engineer, and being a very good programmer, one of my first jobs was as a liaison between a pack of engineers and my programmer brethren. The engineers thought they knew programming because they wrote a few crappy programs in FORTRAN and dumped their data in a heap into a database they could do little with, so the hard part was convincing them that the programmers knew things and had skills that they needed. It sounds like your engineering friend has that part down. So tell me, how does learning C++ from a base of 'a little C' compare to learning Java from the same base?
-
This applies to every new dev. Even you! It’s called experience and it’s why you have more experienced people in charge of juniors. If he crashes the bus that’s not just his fault. It’s also the witches responsibility. That’s just the way it is. Edited to not be such a dickhead. Sorry!
If you can't laugh at yourself - ask me and I will do it for you.
A new dev is usually hired based on a set of competences and skills, may them also be small at the beginning, and software dev is their future job. Here we are talking about making people whose it is not the main job to do software, which is something completely different, and, and that was my point, only possible because software is so easy to produce. And precisely that is how to generate, again IMHO backed up by now 20 years of experience, very quickly very bad software. Our coding witch is very skillful and I do not doubt she has good teaching skills, but this is kind of an exceptional situation : I am facing every day, literally, people who are given tasks of coding (whatever it is, excel macros, vb code, website cms, ... ) and who are not qualified to do it. If what they would need to to do so was more than a computer and a bunch of software tools, like for instance a caterpillar or a $20k equipment, a professional would have been recruited so as to not waste money and they would not have ask to touch software. Not sure about what you wrote, but I am not impressed anymore by the Internet, don't worry :-D ;)
-
Having graduated as a mechanical engineer, and being a very good programmer, one of my first jobs was as a liaison between a pack of engineers and my programmer brethren. The engineers thought they knew programming because they wrote a few crappy programs in FORTRAN and dumped their data in a heap into a database they could do little with, so the hard part was convincing them that the programmers knew things and had skills that they needed. It sounds like your engineering friend has that part down. So tell me, how does learning C++ from a base of 'a little C' compare to learning Java from the same base?
Cpichols wrote:
So tell me, how does learning C++ from a base of 'a little C' compare to learning Java from the same base?
Honestly, I would have to learn Java better before I could teach it, so I can't comment on that. I only know enough Java to be able port code away from it, same with python.
To err is human. Fortune favors the monsters.
-
honey the codewitch wrote:
It can be challenging because there are things he needs to know by certain deadlines, and he's got about 2 hours worth of stamina for a lesson at any given time.
I don't know, but this seems like a loose-loose situation. good luck.
CI/CD = Continuous Impediment/Continuous Despair
Lose the loose and loose the lose! :)
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
I have been too long in the industry to know how this kind of things will end : On your day off there will be a quick metal piece that need to be urgently welded, it will be done because urgent and stuff, and the welded axle of the school bus will not be well welded, will break and the bus will violently hit two walls, run through the kindergarten, and fall from a cliff. :)
-
Cpichols wrote:
So tell me, how does learning C++ from a base of 'a little C' compare to learning Java from the same base?
Honestly, I would have to learn Java better before I could teach it, so I can't comment on that. I only know enough Java to be able port code away from it, same with python.
To err is human. Fortune favors the monsters.
That exactly sums up my knowledge of assembly languages. Well it used to. I haven’t touched it in 15 years or so. So my current knowledge of assembly language is that it is called assembly language!
If you can't laugh at yourself - ask me and I will do it for you.
-
A new dev is usually hired based on a set of competences and skills, may them also be small at the beginning, and software dev is their future job. Here we are talking about making people whose it is not the main job to do software, which is something completely different, and, and that was my point, only possible because software is so easy to produce. And precisely that is how to generate, again IMHO backed up by now 20 years of experience, very quickly very bad software. Our coding witch is very skillful and I do not doubt she has good teaching skills, but this is kind of an exceptional situation : I am facing every day, literally, people who are given tasks of coding (whatever it is, excel macros, vb code, website cms, ... ) and who are not qualified to do it. If what they would need to to do so was more than a computer and a bunch of software tools, like for instance a caterpillar or a $20k equipment, a professional would have been recruited so as to not waste money and they would not have ask to touch software. Not sure about what you wrote, but I am not impressed anymore by the Internet, don't worry :-D ;)
Rage wrote:
And precisely that is how to generate, again IMHO backed up by now 20 years of experience, very quickly very bad software.
Seems optimistic to me. I have seen senior developers create bad code. Not to mention that most cannot even create a design document.
Rage wrote:
I am facing every day, literally, people who are given tasks of coding (whatever it is, excel macros, vb code, website cms, ... ) and who are not qualified to do it
But the reality is too much work and not enough people.
-
A new dev is usually hired based on a set of competences and skills, may them also be small at the beginning, and software dev is their future job. Here we are talking about making people whose it is not the main job to do software, which is something completely different, and, and that was my point, only possible because software is so easy to produce. And precisely that is how to generate, again IMHO backed up by now 20 years of experience, very quickly very bad software. Our coding witch is very skillful and I do not doubt she has good teaching skills, but this is kind of an exceptional situation : I am facing every day, literally, people who are given tasks of coding (whatever it is, excel macros, vb code, website cms, ... ) and who are not qualified to do it. If what they would need to to do so was more than a computer and a bunch of software tools, like for instance a caterpillar or a $20k equipment, a professional would have been recruited so as to not waste money and they would not have ask to touch software. Not sure about what you wrote, but I am not impressed anymore by the Internet, don't worry :-D ;)
While I completely agree with all of the POTENTIAL horror stories people have raised...points to the teacher for accepting the challenge and points to the student for stepping up to a challenge. This IS where knowledge comes from. BTW, 40+ years coding in the real world and mentoring many people. If you want to know true despair do what I do: teach a college course one night a week in C programming to a bunch of students who only saw the dollar signs of software development. Of the 59 remaining (out of initial class of 74) there are perhaps 5 - 8 that might have a future in software development.