4 ms·
The difference is internal vs public. I'm saying build one for internal use (public is readonly). That way you don't deal with moderation and spam.
by JamesSwift 5y ago
The difference is internal vs public. I'm saying build one for internal use (public is readonly). That way you don't deal with moderation and spam.
- ajb 5y agoExactly. I did this at one company because it was less hassle than making sure that finance update the CC on yet another external service every year.
- WorldMaker 5y agoYeah, I'm just saying that's how it sometimes starts: a "quick and dirty" internal tool to just get something done snowballs over the years into "this needs an easier self-service interface to make it easier for Bob in Accounting because he just has so many slides" into "hey since we have this great self-service tool, let's make it customer facing and bill it as a product since we already put all this work into it". Maybe your internal systems are less prone to such complexity effects that turn "internal only" tools into "customer facing products" accidentally all the time, of course. Just that it's an interesting risk, well worth stating, and it is fun seeing all comments on shutdown notices of exactly one such "internal only" tool that accidentally became a "customer facing product" saying "just build it yourself". "Just build it yourself" doesn't entirely protect you from it being your "internal only" tool that's the next trending HN deprecation notice headline.