I until recently worked on a large project, where we decided to use 3rd party stuff. In the beginning it worked fine. We got our stuff together. But as time went by, we discovered, that the libraries we used were too un-flexible. We decided to replace the 3rd party libraries piece by piece with our own code, now knowing exactly what we needed and how to do it.

I left the project when we were nearly finished replacing all the 3rd party stuff with our own stuff. We got very far with the project in the beginning and had something working and running pretty soon.

Now, I work on a large software project in the company I am employed at. Our architect told me, that what ever we can build our-selfs is far better than the 3rd party libraries out there, well knowing, that it costs a lot of time (and money) to build something, that is already available.

My opinion is, that using 3rd party is fine for getting projects far in short time, but in the end, you should rely on your code. 3rd party libraries are often tested by a lot of people and sometimes not (depending on the source). If you work carefully and test your code, you can create everything you can dream of. Build your own little repository of snippets and classes and make them reusable. It will get you further in the end.

I until recently worked on a large project, where we decided to use 3rd party stuff. In the beginning it worked fine. We got our stuff together. But as time went by, we discovered, that the libraries we used were too inflexible. We decided to replace the 3rd party libraries piece by piece with our own code, now knowing exactly what we needed and how to do it.

I left the project when we were nearly finished replacing all the 3rd party stuff with our own stuff. We got very far with the project in the beginning and had something working and running pretty soon.

Now, I work on a large software project in the company I am employed at. Our architect told me, that what ever we can build our-selfs is far better than the 3rd party libraries out there, well knowing, that it costs a lot of time (and money) to build something, that is already available.

My opinion is, that using 3rd party is fine for getting projects far in short time, but in the end, you should rely on your code. 3rd party libraries are often tested by a lot of people and sometimes not (depending on the source). If you work carefully and test your code, you can create everything you can dream of. Build your own little repository of snippets and classes and make them reusable. It will get you further in the end.

I until recently worked on a large project, where we decided to use 3rd party stuff. In the beginning it worked fine. We got our stuff together. But as time went by, we discovered, that the libaries we used were to unflexible. We decided to replace the 3rd party libaries piece by piece with our own code, now knowing exactly what we needed and how to do it.

I left the project when we were nearly finished replacing all the 3rd party stuff with our own stuff. We got very far with the project in the beginning and had something working and running pretty soon.

Now, I work on a large software project in the company I am employed at. Our architect told me, that what ever we can build our-selfs is far better than the 3rd party libaries out there, well knowing, that it costs a lot of time (and money) to build something, that is already available.

My opinion is, that using 3rd party is fine for getting projects far in short time, but in the end, you should rely on your code. 3rd party libaries are often tested by alot of people and sometimes not (depending on the source). If you work carefully and test your code, you can create everything you can dream of. Build your own little repository of snippets and classes and make them reuseable. It will get you further in the end.

I until recently worked on a large project, where we decided to use 3rd party stuff. In the beginning it worked fine. We got our stuff together. But as time went by, we discovered, that the libraries we used were too un-flexible. We decided to replace the 3rd party libraries piece by piece with our own code, now knowing exactly what we needed and how to do it.

I left the project when we were nearly finished replacing all the 3rd party stuff with our own stuff. We got very far with the project in the beginning and had something working and running pretty soon.

Now, I work on a large software project in the company I am employed at. Our architect told me, that what ever we can build our-selfs is far better than the 3rd party libraries out there, well knowing, that it costs a lot of time (and money) to build something, that is already available.

My opinion is, that using 3rd party is fine for getting projects far in short time, but in the end, you should rely on your code. 3rd party libraries are often tested by a lot of people and sometimes not (depending on the source). If you work carefully and test your code, you can create everything you can dream of. Build your own little repository of snippets and classes and make them reusable. It will get you further in the end.