You are preparing to become a Software Developer. And you are coding, practicing, completing exercises, following tutorials online, learning JavaSc...
For further actions, you may consider blocking this person and/or reporting abuse
Good article, I would add
..want to avoid conflict ? Listen to people. We live in a world where answer should be instantaneous, we don't like to wait but interuption when someone is talking may lead to a conflict. We have to listen, analyze, listen to a bit of silence before sharing an answer. This is the good way to team working.
What is it that people say? There's a reason why we have two ears and one mouth? I do agree, in some way. But I will also say that I come from a place of great conversationalist. Since moving, I do miss said conversations. I feel like everyone is so afraid now a days, or harming other individual's emotions in some capacity. There is nothing more satisfying in my book, that worming out a solution as a group. Yet maybe I am in the minority with this mindset?
It's not that things will be instantaneous in this manner, but cohesive. It's a cheesy concept, but when communication is kinetic or synergistic, I think humans are at their most beautiful. Because we are trying, as a unit, to move towards one goal in earnest.
I don't quite buy the idea that anyone can just master coding, regardless of time or experience. I don't even think that anybody can become really good at it. It's just like any other skill: It's just not for everyone.
That's a good point. Programming is not for everyone... but neither is driving, playing sports, or any other thing. I see coding as something from the movie Ratatouille: not everyone will become the best chef/coder in the world, but everyone can learn how to cook/code and do a decent job. Maybe not master-master, but at least good enough.
I think having an open-ear on things needed is very important, and this is the very essential ingredient we developers need to grow as a person also. I've been working solo in a start-up project, which I struggle most of the time, and I rarely get the chance to talk with other developers that are relevant to the technologies that I use. :)
Same thing happened to me when I was alone in a start-up. At that time, I attended many meetups and programming gatherings that helped me meet new people and see new technologies and ideas... I really miss that.
Apparently somethings that seems so simple, is actually the hardest things to do. Nice writing, this reminded me that listening is one of the key skill that we must have to grow up as a professional & personal
Thanks!
Great post on some of the other skills we need as developers. I worked with a lot of junior developers who either wanted to become senior developers or start freelancing/consulting that only focused on their programming skills.
They assumed because they wrote great code they should be able to move up or easily get clients, forgetting all the other responsibilities and tasks that go with being a senior developer or consultant.
Don't just code... documentation is a useful task because it helps developers understand the core concepts clearly. As many have said, it's only when you can explain something in simple language, you begin to understand it yourself. It's with this focus that we started Devopedia.
well said!
Thanks!