A k

[A k @DaJabba]

@bcherny Cheers!

[A k @DaJabba]

@andrewchen You’re onto something. Invest accordingly!

[A k @DaJabba]

$amd

[A k @DaJabba]

Buffalo your f*^%ing amazing!
Making me glad to be your neighbour

[Sportsnet @Sportsnet]

After a microphone issue in Buffalo, the entire crowd helps with the singing of O Canada ahead of Game 5 👏

[A k @DaJabba]

@DailyIranNews When are going to include these guys?

[A k @DaJabba]

@techspence It’s a PEBKAC error

[A k @DaJabba]

@fahdananta Not just SF. This is tech in general

My fav is when someone at a technology company tells me they aren’t technical

[A k @DaJabba]

@theficouple So do farmers

[A k @DaJabba]

True

[Dr Milan Milanović @milan_milanovic]

𝗪𝗵𝗮𝘁'𝘀 𝘁𝗵𝗲 𝗺𝗮𝗶𝗻 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝗸𝗶𝗹𝗹𝗲𝗿 𝗳𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀?

Context switching.

You send a colleague a "quick" Slack message. Takes you 𝟱 𝘀𝗲𝗰𝗼𝗻𝗱𝘀, but it costs them 𝟮𝟯 𝗺𝗶𝗻𝘂𝘁𝗲𝘀 to get back into deep focus.

Now imagine this happening 5-10 times a day. Your best engineers aren't shipping slow. We keep breaking their flow.

It takes about 𝟭𝟱 𝗺𝗶𝗻𝘂𝘁𝗲𝘀 of uninterrupted work to reach flow state. One notification can break it, even if the developer never opens it.

Here is what helps:

- 𝗗𝗲𝗳𝗮𝘂𝗹𝘁 𝘁𝗼 𝗮𝘀𝘆𝗻𝗰. Not everything needs an instant reply
- 𝗕𝗹𝗼𝗰𝗸 𝗳𝗼𝗰𝘂𝘀 𝘁𝗶𝗺𝗲. Protect 2-4 hours for deep work daily
- 𝗕𝗮𝘁𝗰𝗵 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀. Combine five scattered pings into one message
- 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗮𝗻𝘀𝘄𝗲𝗿𝘀. If it's asked twice, write it down once

One team I worked with blocked focus time for a month. Story completion went up 𝟯𝟱%. Bug reports dropped 𝟮𝟴%.

Stop treating your team's focus like it's free. It's the most expensive resource you have.

[Dr Milan Milanović @milan_milanovic]

𝗪𝗵𝗮𝘁'𝘀 ���𝗵𝗲 𝗺𝗮𝗶𝗻 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝗸𝗶𝗹𝗹𝗲𝗿 𝗳𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀?

Context switching.

You send a colleague a "quick" Slack message. Takes you 𝟱 𝘀𝗲𝗰𝗼𝗻𝗱𝘀, but it costs them 𝟮𝟯 𝗺𝗶𝗻𝘂𝘁𝗲𝘀 to get back into deep focus.

Now imagine this happening 5-10 times a day. Your best engineers aren't shipping slow. We keep breaking their flow.

It takes about 𝟭𝟱 𝗺𝗶𝗻𝘂𝘁𝗲𝘀 of uninterrupted work to reach flow state. One notification can break it, even if the developer never opens it.

Here is what helps:

- 𝗗𝗲𝗳𝗮𝘂𝗹𝘁 𝘁𝗼 𝗮𝘀𝘆𝗻𝗰. Not everything needs an instant reply
- 𝗕𝗹𝗼𝗰𝗸 𝗳𝗼𝗰𝘂𝘀 𝘁𝗶𝗺𝗲. Protect 2-4 hours for deep work daily
- 𝗕𝗮𝘁𝗰𝗵 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀. Combine five scattered pings into one message
- 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗮���𝘀𝘄𝗲𝗿𝘀. If it's asked twice, write it down once

One team I worked with blocked focus time for a month. Story completion went up 𝟯𝟱%. Bug reports dropped 𝟮𝟴%.

Stop treating your team's focus like it's free. It's the most expensive resource you have.

[A k @DaJabba]

@smartnakamoura But … but…

[A k @DaJabba]

@knowRowan Humans already do this really well

[A k @DaJabba]

@asaio87 Sure. If you don’t like money

[A k @DaJabba]

@0xlelouch_ See this even from “experienced” developers

Great post

[A k @DaJabba]

@WallStreetMav If you are good - make something, otherwise get ready to be paid to learn

[A k @DaJabba]

@brianlilley @grok is this true? Does this ruling change who has claim to title in Vancouver?

[A k @DaJabba]

@pmitu No, more stuff!

[A k @DaJabba]

@2sush Look I did it - I just posted an app! Http://192.167…. ;)

[A k @DaJabba]

@justinskycak Imagine being the exec that created that tech debt beast - and parachuting out just as it all blow up ;)

[A k @DaJabba]

@MrPitbull07 Tipping culture creates mismatched expectations. Pay your staff - tip if you like the service - but don’t expect it