6 ms·
Now re-read your first paragraph in light of the second one. Sometimes, it really is easier to just implement something your self than go through the "soul des
by jimbokun 11y ago
Now re-read your first paragraph in light of the second one.
Sometimes, it really is easier to just implement something your self than go through the "soul destroying process" of figuring out how to correctly set up and configure a library, framework, or piece of open source infrastructure.
Not an algorithm, but it can be a lot easier to write your own SQL, for example, than setting up and configuring Spring and Hibernate. (Talk about soul destroying. Yes, I am a Java developer, why do you ask?)
- Anderkent 11y ago> Sometimes, it really is easier to just implement something your self than go through the "soul destroying process" of figuring out how to correctly set up and configure a library, framework, or piece of open source infrastructure But then the next person to look at your code has completely 0 support, rather than the very little support they'd have from the crappy documentation and stack overflow if you used an open source library.
- mattmanser 11y agoYes, if you do what jimbokun suggests you're definitely doing it wrong. Edge cases will consume months of development instead of spending a day or two wrestling with poorly written error messages or badly documented APIs. The one I always hit in .Net development is logging, log4net and elmah are both abysmally poor at documentation, but incredibly easy once they're actually set up.
- kevindeasis 11y agoI remember making project using spring. I still have night sweats thinking about it. I'm really happy with node and scala play framework