DEV Community

Tailo Mateus Gonsalves
Tailo Mateus Gonsalves

Posted on

What should every developer know?

Top comments (20)

Collapse
 
ben profile image
Ben Halpern

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.

Collapse
 
essanpupil profile image
Ikhsan Noor Rosyidin

Write maintainable code from the start.

Collapse
 
williamlawrence profile image
Will Lawrence

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. :)

Collapse
 
nickytonline profile image
Nick Taylor

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! 😉

Collapse
 
ignoreintuition profile image
Brian Greig

How to talk to people. This has become a dark art.

Collapse
 
graham_woodruff profile image
Graham Woodruff

Sometimes the best way to solve a technical problem is to go for a walk

Collapse
 
bgadrian profile image
Adrian B.G.

Everything and 42.

Collapse
 
sergiodxa profile image
Sergio Daniel Xalambrí

Design and UX specially

Collapse
 
duduindo profile image
Eduardo Paixão

Tests.

Collapse
 
nimmo profile image
Nimmo

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.