That is because we were taught procedural coding throughout our schooldays. I was taught procedural coding at the age of five. Admittedly neither Miss Cutler nor I knew it was called procedural coding, but that is what it was. It was the sort of thing I learnt that lays the foundations for procedural thinking for life. Have a little example:-Junilu Lacar wrote:. . . students . . . said they were more comfortable with C++ than they were with Java . . .
If you start reading procedural code and compare it to school algebra/maths/arithmetic, doesn't it look similar? I think that is why people gravitate towards a procedural way of thinking. Of course, if people will start by teaching procedural coding, they are going to find it even harder to get people to think in objects later on.Miss Cutler wrote:Campbell, what's 1 + 2?
Swastik
Amanda Clark wrote:now I get a new error to try to troubleshoot 'else' without if' at line 20 which is the if statement for F grade. I will play around with that
Amanda Clark wrote:I am not going to school to be a developer, this is a class to help me learn to talk to my developers but this has been much harder than I thought. Any advice is greatly appreciated.
Paul Clapham wrote:
Amanda Clark wrote:now I get a new error to try to troubleshoot 'else' without if' at line 20 which is the if statement for F grade. I will play around with that
Look at lines 15, 17, and 19. They should all look similar but one is different. In a bad way.
Junilu Lacar wrote:
Amanda Clark wrote:I am not going to school to be a developer, this is a class to help me learn to talk to my developers but this has been much harder than I thought. Any advice is greatly appreciated.
I'll offer you advice not on the programming parts but rather the "talk to my developers" part. I take it that you're in some kind of management role then? First bit of advice, stop thinking of them as "your developers." Speaking from experience, I would rather be thought of by others outside of the development team who also share a stake in the work we're doing as a partner. If you're part of a development team, you think of other developers as your teammates.
I don't know what kind of conversations with the developers at work you have in mind but if you want to support them as best you can, you'd make the conversation more about what you can do for them. As you may have realized by now, developers have enough to struggle with as it is in code and coming up with a clean solution to a problem without having to deal with everything else that's thrown at them from outside of all that.
So rather than "When are you going to be done with this feature?" you can ask "What I can I do to help you get this done sooner?"
Rather than ask "Why haven't you done this (or that)?" you can ask "What can I do to help you get this (or that) done?"
What I'm really getting at is the idea of servant leadership. In my opinion (and experience), this is the best way you as a leader can work with developers and help them do their best.
This guy is skipping without a rope. At least, that's what this tiny ad said:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|