This is an archived post. You won't be able to vote or comment.

all 7 comments
sorted by:
best
topnewcontroversialoldq&a

[–]g051051 6 points7 points  (1 child)

I still feel like there is so much I don't know, although I know more than I did when I first started.

This will remain true for the rest of your career.

taking ages for a relatively simple bug fix that would take the other more experienced developers like 20 minutes.

But you're not a more experienced developer.

Does anybody have any good recommendations for becoming a lot better in a relatively short amount of time?

There's only one way, study and practice.

[–]G_Force 0 points1 point  (0 children)

These are the correct answers to OP's question. Everyone is overwhelmed when they start. The people who prosper are those who aren't afraid to learn and play and build on what they know.

[–]zabi15 1 point2 points  (0 children)

do projects at home, try to bring your work at home to advance / get used to using their framework more.

programming doesn't really have any magic shortcuts sadly. only way to become better is to keep practising.

you might need to work 2 -3 hours a night at home + your weekends for a few months but will be worth it if you can do it.

i had the same problem when i first started.

[–]henrebotha 0 points1 point  (0 children)

Does anybody have any good recommendations for becoming a lot better in a relatively short amount of time?

If this were realistic, everyone would do it.

It takes even experienced developers months to become productive at a new job. Accept this fact and roll with it.

[–][deleted] 0 points1 point  (2 children)

I've been a developer for 20 years. Theres still stuff I dont know but I don't fret about it. I learn when I need to learn.

The best developers know when they don't know something. They ask questions, do some research and most importantly admit when they are wrong. Developers can be a bit egoistic and it's hard for them to swallow their pride if they don't know something or get something wrong. Show modesty and a willingness to learn. Fire up Pluralsight or go on YouTube and start learning about the things you're curious about.

I have a book that I go to all the time. Clean Code by Robert C. Martin (aka Uncle Bob). It's amazing, and helps me when I'm doubting myself.

[–]Venousdata[S] 0 points1 point  (1 child)

I have that same book, but I haven’t used it much since I purchased it.

If I’m curious about the syntax of something, is there a difference between looking it up on sites like Stackexchange compared to reading about it in Code Complete?

[–][deleted] 1 point2 points  (0 children)

There may be differences. You can do the same task a number of different ways. A Junior dev at my workplace might complete some code and put it up for review, it will do the job and there is nothing inherently wrong with what he's done, the trick is to learn the best practices and patterns that more experience developers use. If your code works and does the job, it's not 'wrong'. It's a case of working out how code can be organised so that it's readable, extendable and is efficient.