2 ms·
This may sound flippant or pushing of stereotypes, but teach these things: The value of planning before cutting code: What exactly, precisely, unambiguously, i
by BLKNSLVR 7y ago
This may sound flippant or pushing of stereotypes, but teach these things:
The value of planning before cutting code:
What exactly, precisely, unambiguously, is the desired outcome? Ask enough questions to determine whether the requester really knows what they want or whether they're fishing for self justification of their own role. Create some brilliantly frustrating examples of ambiguous requests, get your students to create a solution, then examine all the different ways they interpreted it. Demonstrate the questions to ask to get to the brass tacks.
Don't expect non-technical people to innately understand the parameters you have to work within. It's your job to explain the boundaries of your ability to create a solution. You know the "why's" of this, but the non-technical folk don't, otherwise they'd be the technical folk...
Don't take criticism personally. If you're taking it personally then you're exposing your own sensitivities about your competence. If you can't do it, ask someone for help. If the platform or tools can't get you the best solution then work towards the nearest best possible solution or change the tools / platform.
I've seen and experienced a lot of ICT angst that is entirely caused by the wrong mental approach. Nothing to do with anything remotely technical. Get that shit sorted early, and the technical stuff becomes eas(y|ier).
"First you must fill your head with knowledge. Then you can hit ice with it"
(Obviously not for the early stages as it will probably scare / bore them away. That's where scenarios or real life examples may help though)