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.
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 a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
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! 😉
I'm a software developer based in Newcastle Upon Tyne, England. I've got a wide range of experience in companies of varying sizes and cultures, and in roles of varying degrees of responsibility.
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.
I teach college web development classes in Denmark and I have been messing around on the Internet since the WWW became a thing.
I love simple solutions and humour!
They should know the seven commandments and keep them in the drawer for easy reference:
Snickers, Toblerone, Ritter Sport, Nestle Crunch, Almond Joy, Kit Kat, Milky Way
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.
How a computer works.
Every developer should understand how their tools work. That is, OS, IDE, text editors, shell/command prompt
that php, javascript and java jokes never get old :)
How to google stuff :)
git
"How to solve it" by G. Polya or "How to solve it by Compute" by R. G. Dromey?
Every developer should know how to learn and do research
Adding to the list.
They should know the seven commandments and keep them in the drawer for easy reference:
Snickers, Toblerone, Ritter Sport, Nestle Crunch, Almond Joy, Kit Kat, Milky Way