Aye. I prefer my own code over others. Probably because I already understand it as I'm building it. I do excessive documentation. Possibly too many comments.
I also try my best to keep my classes small. And when doing dependency injection, I use interfaces instead of concrete classes, so in the future if I want, I may switch to different adapters or something like that.
Some people have given me a lot of dirt because I reinvent the wheel. :P
If you can reinvent the wheel on time within budget and bug free, don't let anyone stop you. I was not allowed to use 3rd party code for a long time and I tried reinventing just the few wheels I knew I needed. 10 years later a dozen projects are running on flat tires that are painful to change or inflate.
I mean the few components of a framework that I built were poorly built, too tightly coupled, hard to test, hard to make changes to without breaking something else unexpectedly. You speak like you have both the skill and time to make everything from scratch properly. That is great if you can. For the rest of us, a framework is a very good and necessary thing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't use frameworks unless I wrote them myself. Debugging other people's sufficiently complicated code can eat too much time.
Aye. I prefer my own code over others. Probably because I already understand it as I'm building it. I do excessive documentation. Possibly too many comments.
I also try my best to keep my classes small. And when doing dependency injection, I use interfaces instead of concrete classes, so in the future if I want, I may switch to different adapters or something like that.
Some people have given me a lot of dirt because I reinvent the wheel. :P
If you can reinvent the wheel on time within budget and bug free, don't let anyone stop you. I was not allowed to use 3rd party code for a long time and I tried reinventing just the few wheels I knew I needed. 10 years later a dozen projects are running on flat tires that are painful to change or inflate.
What do you mean by "running on flat tires that are painful to change or inflate" ?
I mean the few components of a framework that I built were poorly built, too tightly coupled, hard to test, hard to make changes to without breaking something else unexpectedly. You speak like you have both the skill and time to make everything from scratch properly. That is great if you can. For the rest of us, a framework is a very good and necessary thing.