What to read on architecture or proper programming?

Question

Software design

Good evening. I have been writing various web applications, sites, etc. for more than a year. I began to understand that I am writing some bicycles that are not clear and, as it seems to me, are not correct. What to read to get on the right track. So that I can understand my code after a while, or someone else. If important, then the main languages ​​\u200b\u200bof php and js

Answer 1

Oh, I thought there would be a lot of advice to read books on architecture. With them, such a set-up, at the level of a junior, you will not understand what these books are talking about at all. Or you will understand, and such, yes, the author burns, says the right things, but you don’t know what to do with it further, since there is no practice. But when you grow up to some leader, then you will re-read it again with the thought "ah, so that's what he had in mind." And it is precisely because of this that many at the initial stage do not master such books, therefore, if there is extra time, you can read it.
What you need to do: you go to the enterprise. Yes, or just to a company that cuts 1-4 products with different teams. The team should have several people. And you constantly get more experienced developers with questions about why it was done that way. Plus, there should be a review code so that more experienced people constantly point out your mistakes to you, that you don’t need to do this.
A year later, you change the office, but so that there are also complex projects and there are teams, and you also get questions about why it was done this way and not otherwise.
Then you will understand how to do it more conveniently and correctly. That's when you can read books on architecture, so that even more knowledge comes.
Avoid offices in which you will work one or two, this is a swamp that will not give you such a powerful professional development.
As far as writing clearer and cleaner code, this question is not about architecture. This will also come with practice and code review. As an option, to enhance it, you can look at the patterns, here is a cool website with nice pictures, light reading (of course, it’s enough that it’s in the public domain):
https://refactoring.guru/

Answer 2

Frameworks. Learn and start using.
You can read more about patterns and design principles if you don't know.

Answer 3

To write good code, you need to write a lot of bad code. Read the code of similar applications. Ask yourself questions like: "Why is it like this", "How would I do it." For the purity of the code, you can read "Clean Code", but you need to read it when you understand what it is about.

Answer 4

If without reference to PL, then it makes sense to read 3. Gamma E., Helm R., Johnson R., Vlissides J. - "Techniques of object-oriented design. Design patterns". If we are talking about PHP, then "PHP. Programming Objects, Patterns and Techniques" by Matt Zandstra. And also "The Pragmatic Programmer. Journeyman to Master" by Andrew Hunt and David Thomas. All this IMHO, of course.

Answer 5

Read books on design patterns. Gang of four type. Often there are similar books, but applied to some programming language. Well, write code, try to apply patterns in practice, study someone else's code, ask more experienced comrades to review your code.

Answer 6

You can learn something from here . They asked to check the code, what should I look at?