4 ms·
Few things off the top of my heads - horrible at negotiating and playing it safe - biggest mistake was probably being afraid to read source code of third part
by awareBrah 10y ago
Few things off the top of my heads
- horrible at negotiating and playing it safe
- biggest mistake was probably being afraid to read source code of third party libraries when the docs led me to a dead end. Always read the source
- stop trying to make everything DRY, duplication is better than obfuscation
- asidiali 10y agoSecond point is huge. Not sure what it was about my junior dev self and the horrors that lied beyond that `src` folder. As soon as I got over that and started inspecting the source of different projects I was using, I definitely became more confident in my own development skills by comparison, and I became instantly more valuable with the libs I was using because I had more control/understanding of what was actually happening behind the scenes.
- twoquestions 10y agoI still have problems with the second one, as I assume I'm unworthy of reading the code of programmers Much Better Than Me, for fear I'd try something tricky and mess everything up. I'm also mostly a .Net guy right now in a very .Net area, and they generally frown on that sort of thing until very recently. Not an excuse I know, but just for background.
- kzisme 10y agoHow often do other programmers make use of third party libraries? I use them fairly often to parse things or make things more seamless, but is that the general way people go about solving problems? Is that wrong? Implementing a OSS library yourself seems overkill, but at what point is it worth writing something yourself?
- HeyLaughingBoy 10y agoThird party libraries should be the nails and screws of the software world: you should be able to trust that they are fit for the job and not waste the time building them yourself. The main reason to write it yourself is if the libraries you find are crap, or you can't find any at all.