3 ms·
In the case of your JSON lookup table, as long as the damage was to the tune of < $50 and you don't need to run those jobs frequently, I wouldn't spend too much
by zomglings 5y ago
In the case of your JSON lookup table, as long as the damage was to the tune of < $50 and you don't need to run those jobs frequently, I wouldn't spend too much time on it.
I would ask for documentation and put a few notes about what to do if you started needing to run those jobs on a frequent basis - because it can be difficult to predict whether or not that one-off script that someone hacked together is going to become a foundational pillar of your product.
- fragmede 5y agoI've worked at places where the AWS bill was obfuscated/otherwise opaque, so an implementing engineer would have no idea if a job cost $50 or $5,000. (Without a lot of research that's outside the scope of their job.) What tools are you using to display costs to internal developers?
- zomglings 5y agoMy business is very small and there are only 5 of us writing code. I just screen share the AWS bill periodically and we make sure that things aren't insane. We will be switching over to our own hardware in data centers towards the middle of next year. At that point, the whole team will need to be more aware of our constraints in terms of access to hardware.
- morelisp 5y agoI'm talking about a daily service that's a core business process, not a one-off BI analysis. Way, way more than $50. It's cute - and another example of not counting right, I guess - how many people think everyone is on AWS or some other elastic compute system. If we want to run a job, we have to find computers for it.
- zomglings 5y agoDefinitely if it's a daily service, it's totally worth spending the time on automation. I did make the assumption about AWS/equivalent, didn't realize how much of an unconscious assumption it had become. Sorry about that.
- Dylan16807 5y agoWell, finding computers internally is usually cheaper.