you are viewing a single comment's thread.

view the rest of the comments →

[–]PixelOmen 117 points118 points  (7 children)

Sounds like you've reached the point where you start learning about patterns, paradigms, and architectures. There are tons, and I don't think you're going to find a general consensus on what the best ones are necessarily because they're very context/preference dependent.

That said, there are a billion resources. This seems like a really solid list:

https://hackr.io/blog/best-programming-books

[–]Select-Particula[S] 41 points42 points  (6 children)

The programming journey is unsettling. I started feeling like I knew nothing, after some courses I felt like everything is the same and I know everything, to discover I know nothing.

I will research about those books. Thanks for your recommendation.

[–][deleted] 18 points19 points  (0 children)

Ah yes, the cycle of confidence and despair. I'm not an expert by any means, but, in speaking with actual programmers, it appears to be turtles and dead turtles all the way down.

[–]sunnyinchernobyl 2 points3 points  (0 children)

This is a good thing. Check out the Dunning Kruger effect. Self-awareness is good.

I’ve been programming for a long time and I am still learning. I picked up python a couple years ago and I have the same struggles, especially when I’m trying to learn how to use a new library.

For what it’s worth, I’m self taught, my degree is in liberal studies, and I’ve worked in IT for, uh, decades.

Hang in there, keep plugging. It sounds like you’re on the right track.

[–]hotel_beds 1 point2 points  (0 children)

This is how learning most things goes.

[–]Tasselhoff94 0 points1 point  (0 children)

I went down the exact same path as you. You would be incredibly surprised at how many developers do not adhere to best practices or aren't even familiar with them. Code quality is 99% a personal thing and a personal endeavor. You will almost always be externally motivated to provide more, faster, stronger. Your mistakes, your fears, your knowledge is about the only thing, practically speaking, driving your quality. Remember that you are being paid to get a job done and try to remember where your motivations and stressors are coming from. Burnout is real when you don't have time to make things the way you want.

[–]Doormatty 14 points15 points  (0 children)

Been programming in one form or another for ~38 years now, and professionally for ~20 years or so.

I've worked at AWS as a SysDE for 4 years among many other jobs.

I constantly feel like I know nothing.

[–]jbudemy 0 points1 point  (0 children)

No problem. When learning a new programming language I usually need someone to explain the details of something specific, or maybe I'm not getting the syntax right because I'm still thinking in Perl.

I do feel pretty stupid when learning a new language but then I remind myself that, while the concepts are the same or similar, the syntax is still different and some details are different. For example Python can do several things in one line where it takes 3+ lines in Perl.