moveax

It's not a book, but I loved it and it is really helpful.

Haven't tried it yet, but it looked good so far

https://hub.docker.com/r/linuxserver/paperless-ngx

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.

This works good for us. Pretty manual, but works out well.

At my work we wouldn't be able to serve our legacy and non-legacy codebases if we could only use typescript.

Yeah, you can only use it if you start new. But if company exists some time longer you can't only rely on TS

He only can learn from this.

Thank you for your feedback

Good Link.

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.

I'm thankful for your thoughts :)

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 :)

I will give that book a shot!

Git is something on my earlier Todo list, I just introduced the existence of git at first and think we will investigate there more soon.

Thanks for your answer

He already has some knowledge because he visited an IT focused school here in Germany and his father is a coder too.

So I don't need to explain loops, or if statements and can go a bit further in logic and processes

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 will keep that even more in mind now.

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!

Well after reading your message, i just hope to stick in the "good teacher" category soon.

My feelings say i found a good student who wants to learn, so i have a rock solid base here.

But that sounds reasonable and i just made a note about this for my plannings.

Thanks for your insights.

I will follow your suggestion.

Well, over 6k tutors sounds like you found ways to guide people successfully through the process.

My Question about this is, was peer-programming a standard tool, or just plain code-reviews?

I am glad that i will start with only one Person here and i can focus on how he learns :)

Yeah, real world problems are what my favorite way to teach particular ways of building things. No one wants to build the 7th calculator.

Thanks for your Feedback!