Knowledge sharing might seem like a lot of noise. However, when the knowledge is/might affect someone else, then it is worth it. Source(s): Turn The Ship Around; Reply via email | Reply via Mastodon | Comment
3 people assigned and two reviews are required. The more the merrier. Why do I want to do? We have a lot of (unintentionally) hidden knowledge about our services. Domain knowledge is not spread across the team. Learning domain knowledge is hard if you are trying to discover it by yourself. There are many legal or...
When we're onboarding, we often don't know the domain and the system. On a personal level, we have many known unknowns. If we're a junior developer, then we have many unknown unknowns. That's why mentoring and code review helps a lot in figuring out what we didn't know. Especially for junior people, it's a great...
The most convincing code review happens in four steps. First, make it obvious: explain in a very detailed form. Don't just say, please change X to Y. Explain the why so the change should be very obvious. Second, make it attractive: explain the benefits of the change. Make the change request very attractive that they...
In the cross-cultural communication scale (low- and high-context), which two communication styles have more conflicts and problems in communication? Two high-context cultures: Both high-context cultures try to read the air from their own cultural point of view. But the other side's cultural difference makes it...
You shouldn't assume things. For example, when you are not sure about someone's religion, you shouldn't even try celebrating the religious days of their religion. Assuming is one of the worst strategies in cross-cultural communication. It creates awkward moments. Unless you explicitly ask, hypothetical approaches...
The most successful learning method is the elaboration of what we've learned. When we elaborate, we first think about what we read. Then when we think about and write it, we start considering how it informs different questions and topics. And when we try to relate the note with our previous notes, we think about how...
There are many reasons why we must write: Writing is thinking. It shapes thoughts. We learn fresh ideas when we write them. Whatever we read, watch, and listen to is not ours. We internalize them by writing them in complete sentences. Writing is remembering. The thoughts that only stay in our minds abandon us...
How to make a career decision? Ask yourself and answer truly: Do you imagine yourself in five years still coding the same thing or coding at least? Related Note(s): 8a: Making the decision between management or IC Leadership; Reply via email | Reply via Mastodon | Comment
Growing in seniority requires more autonomous work. One needs to be able to work independently from others and in ambiguity. Helping others improve what they are doing becomes the kind of motto. Clear, concise, and transparent communication in written form is absolutely necessary. If the writing is abysmal,...
Look at the defined career path in your company. If you don't have one, ask your manager about the expectations. List them down and learn what moving to the next level requires. Then focus on achieving them one by one. While doing this, write down all the things you're doing on the way. Reply via email | Reply via...
If you have the energy, do side projects where you can test what you've learned in a sandbox environment. While growing, you need to be able to identify the gaps in your knowledge, and you need a place to test your ideas first before applying them to work in production. Source(s): Software World Podcast #9:...
