@Daniel Malmgren de Oliveira I'll take the next few days to see who else puts their hand up and I will get back to you with the details. A couple of people from the paid portion of the site are also interested so hopefully we can put something together :)

@Daniel Malmgren de Oliveira @Carla Mendes Excellent, if all of you could DM me your personal email addresses I will set up a group chat with you and we will go from there. If anyone has a slack channel we can join or maybe google meet works better then please let me know. Let's aim to choose the book in the next week and then have our first session in 2-3 weeks. The idea of having this weekly meeting with people all over the world is pretty amazing and I am certain we will all grow from it.

@Iulia Puiu This is an article you're writing? Deliberate practice is a concept that has helped me in my life immensely and is something I try to apply to my career. Please share the article here once you're finished because I'd love to see some idea's on how to apply it to software development.

@Iulia Puiu it was an easy read and I like that you are applying principals that are not unique to programming to programming. The same methods we use to get fitter and stronger or to learn something different can be used to level up as software developers. I am a fan :)

This is such a great idea and will be perfect to listen to on our way to work etc. Are you planning to have guests on the podcast or see how things go before making other plans? I've posted a question in the link and look forward to listening.

A bit late to the party on this one but this caught my eye and I thought I'd offer my thoughts. The advice to try not to take it personally and to listen to the feedback is good but for most people, the blunt force of the criticism will be a barrier to work around. The examples you have given "This code is crap", "this makes no sense", "are you not paying attention" all sound very direct and are not particularly helpful. These kinds of statements cause most people on the receiving end to reflexively become defensive when they hear it. My 2 cents and what I try to embody in my personal life: "the way that you say things really matters". The information might be the same but "Elizabeth I am not sure I understand what's going on with your code here, can you explain it to me?" is much more productive and effective communication than "this makes no sense". Personally, as a leader, I would rather focus on growth and positive reinforcement by building up the people who work under me and encouraging them to do better. If I see someone's code is not up to par I would work with them directly, always making it clear that I believe in them, and then if/when I see improvements in their work I would call it out, potentially even at standup in front of the team. You're on this forum seeking advice from people so clearly you want to do well and are self-motivated. I hope your conversation with him went well and that the workplace is less tense because I would find that sort of energy coming from a senior developer difficult to deal with and it would make the work much less enjoyable.

JavaScript/Typscript, Jest, React hooks, MUI, styled components, NextJS, NodeJS