Yes I usually try to stick to the current language's standard library as much as possible --- and then for DB or other interop/protocols not already in there, t

Yes I usually try to stick to the current language's standard library as much as possible --- and then for DB or other interop/protocols not already in there, there's typically the canonical mature library or binding in place. Other stuff where libs/modules may exist, I often prefer attacking the small sub-set actually required myself manually. This may not always work out and one cannot always be sure beforehand how well it'll work out, but especially for the things where you only need 10% of the actual functionality and some framework's/lib's focus is mostly on "the other 90%" (in terms of perf / stability / bug-free-ness), on balance I end up with "more LoC written & to maintain but less time spent now and going forward". This approach can definitely fall flat on its face occasionally when just by writing the 10% you thought you needed, you only at the end slowly realize the rest will need to be pulled in after all. That blows. Not a very common occurrence imho tho