Things the domain expert on the author's example cant tell (from the top of my head):
- is the app is properly deployed
- how will the release cycle be
- is it secure?
- can we run two instances of it without messing up the orders/routes/whatever?
- will we spend 5k/month in vercel if people start using it
- how will we notice service degradation
- if we change the data do we have downtime? how do we schedule that downtime window.
- where is the code stored? can the team access it?
- how are new contributors onboarded?
- does the app use credentials and where to store them?
- does the app manipulate or store PII?
- if the user refreshes the app does it generate a duplicate order/route/whatever?
- if there's an upstream service are we making sure our timeouts are properly configured?
- if there's an upstream service are we making sure our connection pool is properly configured?
- do we have a max connection lifetime so that middleware like AWS NAT or ALB don't leave us with dead connections in our pool?
I think that makes the point clearly. Also it may explain why software developer jobs are currently on the rise despite SWE-Bench-Pro-Ultra-Magic has been maxxed for months now.
Can't believe people is so eager to believe in this without any real scientific publication of vaccine efficacy.
Cuba lacks things so common as soap, to the point that you can bribe police officers or even pay sex workers with a tiny hotel soap bar or shampoo flask.
- is the app is properly deployed - how will the release cycle be - is it secure? - can we run two instances of it without messing up the orders/routes/whatever? - will we spend 5k/month in vercel if people start using it - how will we notice service degradation - if we change the data do we have downtime? how do we schedule that downtime window. - where is the code stored? can the team access it? - how are new contributors onboarded? - does the app use credentials and where to store them? - does the app manipulate or store PII? - if the user refreshes the app does it generate a duplicate order/route/whatever? - if there's an upstream service are we making sure our timeouts are properly configured? - if there's an upstream service are we making sure our connection pool is properly configured? - do we have a max connection lifetime so that middleware like AWS NAT or ALB don't leave us with dead connections in our pool?
I think that makes the point clearly. Also it may explain why software developer jobs are currently on the rise despite SWE-Bench-Pro-Ultra-Magic has been maxxed for months now.