Meetings, most of them without bullet points or a specific topic.
I'm coordinating another devs too and that costs less time then meetings to projects. We don't have the best product owner culture, so I need to fill that role too. But we are working on that topic atm and we are reaching the first goals.
It's funny and I like it, but sometimes I just block time in my calendar to do tasks two weeks ahead. So nobody is able to schedule me on a meeting without asking before.
That makes most people think about if I'm really necessary.
I am self-tought and i made the experience that being wrong helped me to evolve. I guess i grinded the gears of many people in bulletin boards or irc channels in the moment i came by with my naive solutions.
But getting corrections and new insights helped me to grow. This is something i want to transfer to my trainee aswell.
Well, he has the basics like data control structures, database usage, a little bit OOP. I think the missing link is how to build real world processes with it.
I'm sure we will find basics that are missing and will have to fill that with knowledge, but we have a good starting point.
By what you said above, don't underestimate yourself there. Building scripts that touch real things to make it better working for you (and others) is a great step on the journey to write good code! Thanks for your feedback :)
Point 3 is something I haven't thought of yet. During reviews I pointed on some issues, not every. But that was never something I had a specific reason for, I was just focused on what we want to learn in this lesson.
I'm not able to answer all your comments right now. But i want to let you know, that i read all of them and i love your feedback.
Up to this moment i learned that going with real world examples is the way to go. Since i work in a software department of a real world company and mainly code Inhouse solutions, i am sure that i can provide a lot of them.
Beeing available for Questions and Feedback and provide Learning Material and doing sessions about technology and patterns, before they are needed to solve a problem is the next thing i noted down in my plannings.
I am very thankful for all the Feedback and can't wait to get more!
I am lucky that he already have those coding basics and wants to learn. And i experienced in his intership that he came back the other day and said "i tried this at home, how could i do this better" and was all open for suggestions ect
It's not a book, but I loved it and it is really helpful.