For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Antonio | CEO at Litlyx.com -
Baltasar García Perez-Schofield -
OpenSource -
Ben Halpern -
Top comments (20)
Debugging strategies: Eliminating variables and addressing your own assumptions about the system in order to debug effectively. I think this fundamentally applies to all subsections of our industry.
Write maintainable code from the start.
What do you mean by know? Are you referring to languages and technologies, or are you talking about... refactoring, planning and things that are not strictly related to development? Because I would love to talk about either, but one is definitely shorter to write. :)
I'm saying what some would assume is obvious, but I'll say it anyways. It's OK to ask questions. No one knows everything. What you should do though before asking your questions is do your due diligence. Step through the code, check the logs, Google the error etc.
Someone more junior would perhaps due less of this, but as you progress in your career your diligence should increase.
Part of being a software developer is being a detective. 🔎 Now crack the case! 😉
How to talk to people. This has become a dark art.
Sometimes the best way to solve a technical problem is to go for a walk
Everything and 42.
Design and UX specially
Tests.
That when people say "oh [X person] is just difficult to deal with - they're a fantastic engineer but they have no people skills", they shouldn't think that this is okay, and they _definitely shouldn't aspire to be that person.