Can someone take a look at a PC build and tell me how long it will last?

Question

Iron

AMD A8 9600 Processor + AeroCool Verkho Plus CPU Cooler
MSI B450M PRO-VDH MAX Motherboard
AMD Radeon R7 Performance Series [R744G2606U1S-U] 4 GB RAM

Excluding Power Supply and HDD

Answer 1

No , no one can tell how long it will last.
Depends on so many factors, even if planned obsolescence is excluded. Mechanical parts (coolers and hard drives) wear out from the number of rotations and the number of on / off. Moreover, the limit depends not only on the model, but also on the batch, which may be partially defective, with a reduced lifespan. Other parts may break due to overheating, which in turn depends on the load, cooling and temperature conditions of the environment, temperature fluctuations, dust, etc. etc. Separately, it is worth mentioning voltage drops, shock loads, etc.

Answer 2

Prots should be changed to 4-core
RAM to kinkston or hynix, don't take AMD, it's shit. and 4gb is not enough, at least 8gb is needed

Answer 3

Yes, as long as you like. But most likely in a couple of years it will be necessary to change the cooler, and in 5-7 years the capacitors on the motherboard will dry out and glitches will appear.

Answer 4

It will work, the question is only to the processor. For 6k 2-core? why? You can get a 4-core AMD A8 9600 for almost the same price.
Again, there will be questions to the power supply. Suddenly you will put Aerokul Xas?

Answer 5

Suitable for a typewriter. For something more, you need 8-16 GB of RAM, Ryzen 3-5 / Core i3 / 5, ssd at least for the system.

Answer 6

There are many options and you can choose only knowing the specifics of a particular project. In addition, there is no limit to perfection and there are many nuances that can be put up with in some cases and not in others.
So without knowing the projects it is impossible to say whether you understood something correctly or not. Therefore, I will try to answer the voiced questions, but I will not provide a complete picture.
Developers can test their code either, as you said, on their computers - then the developer needs to be able to run a copy of the system on their computer.
They can also use one test server with which they will synchronize their source code during work. This can be done with rsync or winscp or whatever. You can use a separate subdomain vasya.develop.com for each developer , or a separate folder develop.com/vasya/
Since there can be several different tasks in one "build", that is, several branches are merged - you need to test them all together. To do this, after the merge, place this code somewhere for testing (for example, test.develop.com or develop.com/test/). Some changes need to be made already in the branch into which these changes were merged. It all depends on how you organize it in git. When everything is tested, you can deploy the code to production.
You can upload the code, as you said, via ftp / sftp, or you can deploy a copy on the test server when pushing to a specific branch in the central repository. For example, when pushing to the test branch, fetch is done on the develop.com server and the current state of the test branch is uploaded to the develop.com/test/ folder. Well, this is all in general terms - you still need to decide how and from where the settings specific to a particular instance of the system will be transferred, if any, which database this instance will work with, etc.
It all depends on how you use it and how you deploy. I can recommend keeping the database structure and "system" data in some form in the repository. So that you can deploy an "empty" database only based on the data in the repository. For example, you can simply store scripts there for creating tables with the desired structure and for filling in some system data. When any changes are made to the structure, you need to make them, respectively, in the repository. In general, transferring database changes is a separate big question - google "database migration".