Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

BREAKING || Several WhatsApp accounts, including those in India, placed 'under review'; users locked out for 24 hours without prior notice. During the review period, affected users were unable to access chats, make calls, or use other WhatsApp features. Sabyasachi Roy Chowdhury & Prathibha break down the details.

22,130 Aufrufe • vor 18 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Possibly the biggest change in Microsoft Teams history? Teams without the Teams? Public preview in November to desktop, mobile, iOS, and Android. Here is what you need to know: 🟣 Microsoft is introducing a new combined chat and channels experience. Meaning chat and teams/channels will show up under the "Chat" sidebar icon. No more dedicated Teams sidebar button. 🟣 Teams and Channels will have their own section in chat. 🟣 Group your chats and/or channels however best works for you with favourites and custom sections (up to 50 sections and 50 items per section) 🟣 “Unread,” “Chat,” “Channels,” “Meetings,” and “Muted” Filters 🟣 New message can initiate a new chat or new channel post 🟣 New Mention view gathers all your mentions into a single interactive list. 🟣 At launch, a self-service, guided onboarding will help users discover the new experience and configure it to their preferences (on or off) 🟣 Users who prefer to keep chat and channels separate can easily do so during the onboarding process or at any time later. So far, it looks like there are no IT/tenant-level override controls. This experience change is targeted at getting more users using teams/channels. Most Teams users live in "chats", not teams/channels. There will undoubtedly be some pushback from users who use teams/channels well and like having the mental separation of teams/channels vs chats. I've been fortunate to be using it for a while, and I'm personally a big fan; my use of the correct channels has gone way up, and now I can find them all in one place in the app, particularly on mobile. I'm now much more likely to see channel conversations I need to see. What do you think? #MicrosoftTeams #Microsoft365

Tom Arbuthnot

64,542 Aufrufe • vor 1 Jahr

How did a tiny team of 30 engineers build WhatsApp, more than a decade ago? From Jean Lee, engineer #19 at the company. Timestamps: 00:00 Intro 01:39 Early years in tech 06:18 Becoming engineer #19 at WhatsApp 13:53 WhatsApp’s tech stack 18:09 WhatsApp’s unique ways of working 25:27 Countdown displays and outages 27:07 Why WhatsApp won 28:53 The Facebook acquisition 33:13 Life after acquisition 39:27 Working at Facebook in London 44:07 Transitioning to management 47:27 Performance reviews as a manager 53:29 After Facebook 58:53 AI’s impact on engineering 1:02:34 Jean’s advice to new grads and startups 1:06:45 Empowering employees 1:08:17 Book recommendations Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar – The makers of SonarQube, the industry standard for automated code review. • WorkOS – Everything you need to make your app enterprise ready Three interesting observations from this episode: 1. WhatsApp had no code reviews after in-place. WhatsApp cofounder, Brian Acton, reviewed the very first pull request of each new hire, and after that, there were no more code reviews. Jean recounts how Brian reviewed her debut PR in extreme detail. This first (and only!) review set the bar high, and she wrote code to that standard from then on. 2. WhatsApp had close to zero formal processes. WhatsApp had no Scrum, no Agile, no TDD (test driven development), and no formal code reviews beyond the first commit. In contrast, Skype had 1,000 engineers and mandatory Scrum training, but WhatsApp still outcompeted it and won. Jean’s response to hearing of all the formal processes Skype used in order to execute faster: “I’m surprised to hear they thought they were shipping faster because of it.” Perhaps process is often a substitute for trust, not quality?” 3. Saying “no” to features was a competitive advantage. WhatsApp’s CEO, Jan Koum, rejected 99% of feature requests from the team. While competitors shipped dozens of shiny, new features, WhatsApp ruthlessly prioritized reliability and simplicity. Jan repeatedly told the team what the mission was. “I want a grandma living in the countryside to be able to use our app”, he said.

Gergely Orosz

111,903 Aufrufe • vor 5 Monaten