3 ms·
First... assume you are wrong. Ask defining questions, and re-approach the issue until you understand. Second... when you are explaining code, unless it is `1
by tracker1 8y ago
First... assume you are wrong. Ask defining questions, and re-approach the issue until you understand.
Second... when you are explaining code, unless it is `1+1` don't assume that it's simple logic. I've seen people freak out seeing code like this.
Object
.entries(obj)
.filter(([k,v]) => /foo\-/.test(k))
.reduce(([k,v], o) => ({...o, [k]: v}))
Is it simple? to me, pretty much so, to someone else, maybe not so much. Even more so if the abstractions are custom to a particular library, language or behavior.
Third... if, and that's a big IF you are right... be considerate in your communications.
You may or may be able to not work with someone... but if you're a junior, and they're a senior.. they may not be your direct manager, but they are senior and may have a more critical understanding of a project and the company as a whole.
In 25 years in software development... I've met literally one person that was too arrogant for me to actually work with and one that was actually too ignorant for me to work with. This is out of hundreds of people I've interacted with in the workplace regularly.
Reflecting back on it. In most cases, the issue was me.
- tracker1 8y agoObject .entries(obj) .filter(([k,v]) => /^foo\-/.test(k)) .reduce((o, [k,v]) => ({...o, [k]: v}), {})