programmers need a self inflicted rule of it being less than 500 lines of code means you need to write it instead of using a pre written package/library.
Then I end up doing that (https://github.com/Daniel15/jsframework is my most ‘recent’ one, now very outdated) but eventually the library gets outdated and you end up deleting most of it and starting again.
i wonder if maybe we just need personal package repos for shit like this, stuff that probably shouldnt be out on the internet and accessible, but that’s also worth packaging for regular use. Like a sort of “code macro” which is something i see people doing a lot for certain boilerplate strings.
You are describing a state of software development that has existed since the introduction of punch cards.
Practically every business I’ve worked at has had some internal library or repository of commonly used behavior that can be included in day to day projects.
That’s what I do, but then I end up with similar utils across multiple projects (eg some of these array, map, and set utils: https://github.com/Daniel15/dnstools/tree/master/src/DnsTools.Web/ClientApp/src/utils) and wonder if I should create a library.
Then I end up doing that (https://github.com/Daniel15/jsframework is my most ‘recent’ one, now very outdated) but eventually the library gets outdated and you end up deleting most of it and starting again.
It’s the circle of life.
i wonder if maybe we just need personal package repos for shit like this, stuff that probably shouldnt be out on the internet and accessible, but that’s also worth packaging for regular use. Like a sort of “code macro” which is something i see people doing a lot for certain boilerplate strings.
You are describing a state of software development that has existed since the introduction of punch cards.
Practically every business I’ve worked at has had some internal library or repository of commonly used behavior that can be included in day to day projects.