4 ms·
I think a degree of skepticism is required with NIH. I'm probably not going to roll my own crypto, or high performance statistical routines. But if something in
by HumanDrivenDev 9y ago
I think a degree of skepticism is required with NIH. I'm probably not going to roll my own crypto, or high performance statistical routines. But if something invented elsewhere "solves" a problem that really isn't rocket science, or if it's a framework - I will almost always avoid it.
- virmundi 9y agoout of curiosity, did you roll your own logging framework? When I read that point, logging came to mind. Should I use SLF4J, or simply print to out?
- flukus 9y agoThat's a wheel I have reinvented to good effect. Most logging libraries are quite dumb, if you set your threshold to info you get way to much information, if you set your threshold to exception you lose to much information from before the exception was thrown. Different messages from different threads are all mixed together, etc. My app specific logger is aware of the context it is running in, it will store all the context but only write it on an exception or error and discard it otherwise, so I get all the information I need without the noise from the 99.9% of the time I don't need it. I do use logging libraries, but they are for the low level stuff like file truncation, rollover, etc and I wish there were "logging" libraries that did just those tricky little parts on let me write the 50 or so LOC that the high level interface needs.