@raganoakley@Adobe Log in with your username on https://t.co/iKSnstsW7r and accept the Terms of use there. You will be able to continue in the app afterwards.
If you want to go multi-cloud, start by going multi-region in one provider. You'll learn a lot of valuable lessons.
Also migrate to AWS spot fleets. Having things you're using turned off with a 2 minute warning is good preparation for Google Cloud's offerings.
@IanColdwater That's an easy one: site has a character limit on passwords, sign in and sign up do not truncate before sending to backend, but reset does.
You'd be amazed how often that happens and how many times reset is a second class citizen compared to sign in/sign up...
I liked this backend developer roadmap by @kamranahmedse https://t.co/Swp67RSuau -- it's impossible to build a list like this that everyone agrees on but it's a good starting point
Tuesday Technical Tweet Thread Time! Let's go on the roller coaster of what happens at a low level when a DNS server sends an 4,000 byte EDNS0 response to a client whose MTU is 1200 bytes. Confused already? don't worry, we'll break it down. I promise it's super interesting.
@0xcafebabe@noahsussman As always, context matters, and the same tools can be used for good or evil. FWIW, the team I'm in moved from ~100/8000 flaky tests to ~10/9000 flaky tests in the past year. Would have I been better off leaving the team/company when we were at 100/8000? I highly doubt it.
@0xcafebabe@noahsussman Also, it's more about retry-to-total-tests ratio. Is it 10 tests out of 10.000? Then it might be OK to always retry them. Is it 100 tests out of 5000? Maybe you're better off spending _some time_ investigating and fixing the root causes. Is it 200 out of 400? Stop now & fix 💩
Currently state of AI:
Someone makes some garbage
Which they sell to someone else, who doesn't care that it's garbage
Who uses it in a way that makes everyones life garbage
And life is great for everyone but the AI target.
Just like the Ancient Internet Meme about bullshit
@lucianadrian@santhoshst I would rather ascribe it to the (perceived) lack of feedback that saving usually has. When you're unsure if you really pressed those keys and there's no way way too tell it, you do it a couple of times “just to be sure”.
I doubt vim users :w! multiple times in a row 🤓
Thoughtful and nicely explicited thread. Applies to many things in software development, including #testing and #infrastructure (incl. testing infrastructure)
This is in response to my statement that senior engineer's job is to point out and amplify hidden costs. Not one time, but patiently, consistently, repeatedly.
I told this story unplanned and impulsively at code freeze, I may as well tell it here too.
It was deep in the dog days of last summer, our funding situation at its grimmest. I lay awake every night gnawing and fretting over whether we really had product market fit or not.