Respectfully it may have been above their risk tolerance, and of course you being successful with it doesn't make it a prudent investment. That's the "I won the lottery so everyone should have played the lottery" thing.
> What they don't see is that the engineer tossing the ball figured out that the solution they were about to spend 2 weeks coding can be achieved by leveraging an existing library requiring only a couple days effort.
Maybe this is an unpopular opinion, but that wouldn't mean that the engineer shouldn't implement in a couple days and then work on something else. HN loves the trope of the super smart engineer who is smarter than _everyone_ and can look like they're doing nothing.
It's so negligible for creators as to be meaningless. If it's meaningless except (maybe) to those who are so ultrapopular as to derive value from it, what good is it to normal people?
Same here, with AWS specifically. I'm used to AWS so generally stay in that ecosystem. Designed a web app and backed part of it by lambda and api gateway. Via a surge in traffic, my monthly bill went from about $6/mo to $150 for a month. Didn't catch it until I got the bill for the month, the timing of which meant my next month's bill was about $80.
Awesome, awesome, awesome. I know I have no right to think that anyone would care for a moment about the code I'm writing or the potentially money-making side-projects I'm working on, but I am paranoid about entities like current/future employers and third parties seeing what I'm developing in private. I often just keep those local and back them up privately to an SD card, or go with private bitbucket (which is harder because I do all my at-work development on GitHub).
This will significantly increase my use of GitHub.