Curious to catch the very crisp English voicing by most speakers, compared with very distinct ways of speaking commonly heard from Indians from different provinces today.
I know the exact expected behavior before I start coding. But I am having trouble translating that expected behavior into my TDD test cases. For example. an expected behavior could be the functionality I am building should periodically look into database, compute some metrics and then generate a report.
This is a broad piece of expected behavior, unlike a unit test when you test small functionality.
As per the TDD principles, it is advised to write tests at your interface and avoid any dependency on your implementation details as these may change in future. I am having a hard time trying to understand how do I do this for the use case I just mentioned ?
If anyone is curious about their deployment process https://slack.engineering/deploys-at-slack-cd0d28c61701?gi=e...
Seems hard for a new deployment to cause a global outage since they do a phased deploy. Could be some network glitch causing this issue. We never know until they come up with an update.
Everywhere I’ve worked has done phased deployments. Shit still goes wrong all the time. Also, I would wager that most outages are not due to code deployments, but live config changes.
I would suggest something basic. Take a print out of monthly habit tracker from here: https://tealnotes.com/free-printable-bullet-journal-habit-tr... and add the goals/ habits you want to achieve. Put the goals in the order in which you want to do every day. Stick it on your wall such a way that it is very visible to you (this matters as this act a reminder for you). Every day check this list off.
I have tried a lot of things in the past, and found this approach the most effective.
Yes. We ran into this early on. Setting your bid price(maximum price you are willing to pay for the resource you are spinning up) higher than the average spot price do not protect you against instance termination. Also even if you place your spot bid price at current on-demand price (you only get charged at the current spot market price) your instane will be terminated if there is no resource availble in the spot instance pool. For example, you have spin up an ec2 instance with 100 GB RAM with type spot instance, with bid price set to the on-demand price. If someone else spin up a 100GB as on-demand instance type- if there is no resource left in spot pool, your instance will be terminated.
Ubereats user from India here. Just opened the Ubereats app and it says "your account is now set up on Zomato" and directing to Zomato app. Looks like they completely shut down the app and moved their operations to the Zomato app.
