10 Top Signs Of An Inexperienced Developer

What makes a good developer/web developer? What thing should you avoid? In this video I discuss 10 top signs of an inexperienced developer!

Dylans Channel

Code Tech And Caffeine Facebook group

[ProgramWithErik]

Hey! These are tips that I've used to get better however, I'll be the first one to say that I"m still learning. I've made these mistakes and sometimes I still do :) So please keep that in mind, we are all learning to be better! What are some mistakes you think inexperienced developers make?

[mariofajardo]

Thanks for the insight! I've been a Tech Recruiter for about 5 years and always appreciate getting this type of perspective. Sometimes it's easy to just ask "how many years of this tech do you have". Your video has helped me come up with some great screening questions I plan on using as I talk to candidates. I subscribed and look forward to checking out some of your other content!

[clarkd]

I have only completed more than 1, 000 projects over a 40 year career and I find a huge number of tiny functions are a huge problem that doesn’t get much coverage. The fad of no comments and 7 word strung together variables are equally horrible.

If people are going to preach what kind of coding is good or bad, there should be a reasoned debate or at the very least, there should be lots of experience to draw your conclusions from.

Just one example. How do you make a small fast function out of the execution engine of a byte code interpreter that has a few hundred instructions? The only unbreakable rule in computing is that any rule can legitimately be broken in certain circumstances.

And one more. Using goto’s in C to make a single exit at the bottom of a function. Goto’s are normally bad but the best solution for exiting given many error conditions (see Linux code use of gotos).

[XSnipersArmyX]

I'm italian. I eat spaghetti code.

[SK-ybbx]

They're always a better way of writing code and in engineering in general, there is always room for improvement. I definitely should dedicate more time to creating effective unit tests.

[willietebs]

You can use this time to teach better coding online instead of spending time criticize others and bragging how you know better than others. This is absurd. There is always room for improvement in every field.

[KayOScode]

Nope, unit tests are way more valuable than end to end. You can never fully debug end to end and the closest you will get is if each individual component does everything exactly correctly. That said, you should test end to end to see if you connected the units properly and debug that as necessary.

I usually overengineer to make sure I can very easily modify my code in the future. For example, when building a compiler, I would set it up in such a way I can modify the syntax and pretty much everything just by modifying an array. I am not sure if its good or bad, but I know it makes me comfortable.

[Kingromstar]

What about trunk based version control strategy with pair programming, then committing directly to master is fine

[phoenix-walker]

I would add one:

Not being able to explain why you decided to use a tool or framework to accomplish a task.

Some Bad answers:

"Because it's new!" - Appeal to Novelty.
"Because it's what we always do!" - Appears to tradition.

"Because we need it!" - Does not answer why we need it.

I hear these all the time.

Some Good answers:
"It's solves xyz problem more efficiently than we could, writing it ourselves."

"We have to solve xyz problem. This already solves xyz problem. Therefore we shouldn't waste our time solving a problem that's already been solved."

[yackawaytube]

I would add the following:
1) Can't articulate what the problem to solve and how the code solves it. Try to hide it by using big jargons or calling people ignorant.
2) A lack of curiosity when using third party framework.
3) Apply hammer to every problem because when your only tool is a hammer, every problem has to become a nail.

[bouhannacheabdallah]

there is something that you didn't really care to mention is how to ask question online because you're gonna get humiliated every time if you ask a question with bad manner of even if you wanna have the answer on a precise thing and dev community throw you away just because you are entitling it with a similar title of existing ones

[Gunsong]

I have to be honest and admit to being terrible at asking for help. Not because I think I am better than everyone else, but because I get angry with my own ignorance.

Also
# 11 is dogmatic.
# 12 thinks in absolutes as opposed to tradeoffs.
# 13 Weak personality.
# 14 Lacking curiosiry.
# 15 Overrelying on theory to the point where of assuming that every vendor will by some force of nature adhere strickly to IEEE standards and textbook discriptions.

[SaintTheDreamer]

I found learning to.code fairly intuitive but I still get stumped if I need to integrate design patterns in the code. Firstly I find it difficult to visualise the solution without having the full picture of the visualization of the problem in the code context. Next, sometimes I end up refactoring way too much based on the framework I'm using and other things.

[fsanchezdelacampa]

Hi, On minute 6, what do you meanby testing a happy path?

[PhanTimo]

I personally only research and experiment with frameworks and languages relevant to my job or a side project I want to work on. But I don't really explore outside of my main stack. Do I qualify as a bad developer?

[joedarrington]

Rely to* heavily on copy pasted code - you should have copy pasted that! *Too

[nathanlewis]

You mean Rely too heavily on Copy Pasted Code

[blasttrash]

Where's the usual "hey hey developers"? :P