5 Things you should NOT be ASHAMED of as a developer

Vaibhav Namburi - Jul 22 '19 - - Dev Community

There are several of these, but these are the 5 most common things I've found engineers in my experience hesitate to do because it might make them feel less of an engineer or worse less "senior" as an engineer or developer.

The 5 things you definitely shouldn't be ashamed of as a developer:

1. Readability

It's okay to allow for some repeatability in your code as an offset for developer readability. Remember your code is only as good as it is easy to understand and debug when the time comes.

Code can ALWAYS be faster, there are always ways of making it more performant, you just need to maintain a good balance between readability and performance.

2. Pace

It's okay to not be the "fastest" developer. A common misconception in the industry that a "fast" dev or a dev who smashes out code is a better than one who might take a little longer. It's okay to take time and examine the architectural consequences for developing a feature set

3. The choice for today

Everything you write today will be replaced eventually, don’t get too attached to solutions, get attached to problems.

It's okay to not be too happy with your solution for today and come back and optimise it down the track.

4. Asking for help

Honestly, senior or junior - you should ask for help when you need to. We have a rule, if you spend more than 10-20 mins on something, just ask someone, 2 heads always beat 1 head.

However, always try your best to improve your "solution finding" skills if don't have time to improve on your "problem solving" skills. Asking the right question is half the battle.

5. The language

Not knowing every corner of the language is fine. It makes no sense to learn every single thing about a language and not build in the end. It's an iterative process, understand core principles really well, and all the sugar syntax can come when you face the problem - google it.

Learning every bit of a language without actually using it in production to solve problems is the equivalent of knowing every rudimental in drumming but not being able to piece together an actually good beat.

These are the things we've tried to employ at the engineering culture at five2one.com.au. There's a long journey ahead to building an even better culture and we're pushing for it every day!

I'd love to hear your thoughts/additions or edits in the comments section 💪

If you liked this, definitely follow me on for the similar stuff:

twitter: twitter.com/@veebuv
linkedin: linkedin.com/in/vaibhavnamburi
instagram:_veebuv

. . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player