This is really interesting research. Details from 18 well-known tech companies, about how they attempt to measure + answer “what impact do our AI tools have on software development?”
Excellent research by @rhein_wein, details shared here for the first time:
Anyone – of any race, creed or nationality – who came to America and worked like hell to contribute to this country will forever have my respect.
America is the land of freedom and opportunity. Fight with every fiber of your being to keep it that way!
🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸
12-hour timelapse of American Airlines, Delta, and United plane traffic after what was likely the biggest IT outage in history forced a nationwide ground stop of the three airlines.
1. Ask Questions
- No matter how dumb you sound
- No matter how silly that question is
Just ASK
- Don't assume anything, have absolute clarity of your work before you start.
- A minor communication gap will ruin your entire hard work so keep asking questions.
Just because you are nervous prior to a major meeting or an important presentation doesn’t automatically mean you have Imposter Syndrome. It usually just means that you care about ensuring it goes well.
This discussion between a Google engineer and their conversational AI model helped cause the engineer to believe the AI is becoming sentient, kick up an internal shitstorm and get suspended from his job. And it is absolutely insane. https://t.co/hGdwXMzQpX
Here's a list of tips to improve your systems' observability and reduce MTTR based on my own fire-fighting experience and well-known industry best-practices.
Anticipate failures and avoid getting your team burned out.
🧵 (1/12)