ATumne

Build and scale teams, product, little humans, engineering leader, mom to 2, wife, passionate foodie, views are my own

[Min Choi @minchoi]

I gave Opus 5.5 one prompt + music.

12 hours later, I woke up to this.

[Cindy Sridharan @copyconstruct]

You know what’s more sobering?

Amazon *already* has some of the most stringent/sophisticated CI/CD game in the business. See https://t.co/D7Upm1VTZD

Most embracing “vibe coding” don’t have the guardrails Amazon already does and are going to relearn reliability first principles.

[Nivi @nivi]

The opportunity cost of employees who need to be told what to do has gone through the roof.

[Peter Steinberger 🦞 @steipete]

@shl @daviduche03 People act as if using agents to build software removes all the work; it accelerates the process, but it also upped expectations.

[Corey Quinn @QuinnyPig]

This killed me.

[Matthew Dominick @dominickmatthew]

We flew over Hurricane Milton about 90 minutes ago. Here is the view out the Dragon Endeavour window. Expect lots of images from this window as this is where I’m sleeping while we wait to undock and return to Earth.

Timelapse coming in a separate post.

1/6400 sec, f8, ISO 500

[Shreyas Doshi @shreyas]

Just a few notes to myself (a driven & ambitious person):

1) Kings are overrated and usually unhappy. It is much better to be kingmaker.

2) Eventually, everyone realizes that they don’t want to be Elon Musk or Steve Jobs. How quickly do you want to get there?

3) Legacy is overrated. So is impact.

4) Learn from everyone & everything. Don’t view people as better or worse than you, worthy or unworthy of teaching you. And if something doesn’t fully resonate, don’t reject it wholesale. Try extracting the useful bits and learn from those. Wisdom is everywhere, if you can spot it.

5) When you find someone inspiring, try to separate their content and their charisma. And if it’s the charisma that inspires, be very careful.

6) The chief indicator of authentic confidence isn’t bravado. It’s the person’s openness to discovering why they’re wrong.

7) Whatever industry or domain you are in is probably smaller than you imagine it is. People talk. Don’t burn bridges over the small stuff.

8) When in doubt about where to take a job, pick the place with the better people. Even if it ends up being the wrong bet, you will still be more fulfilled with your work.

9) In the tech industry, things often change. Platforms change, technologies change, office signs change, employers change, centers of gravity change. The one thing that remains constant is the people. Always optimize for the people.

10) If you choose to understand just one cognitive bias, let it be the Fundamental Attribution Error. If you choose to understand one more cognitive bias, let it be Confirmation Bias.

Last but not least, very important note:
No rule is valid for every single situation in life. Except this rule.

[Rebekah Jones @GeoRebekah]

A quick summary of why all these UFOs are popping up now.

Call it Science Sunday… or Superbowl Science Sunday.

In spatial science (in this case radar/satellite data), we use techniques to filter out noise so we can identify objects in space (the abstract space, not outer space).

Think of it like trying to find a tennis ball on the beach using a 3d scan of the beach read as lines of text.

You know how big the tennis ball is, so you take all the data from the beach and tell the computer to find a round object that is the approximate size of a tennis ball.

It would take a lot longer to find the tennis ball if every small object on the beach had to be reviewed one-by-one. So we tell the computer to ignore everything that doesn’t look like a tennis ball.

Same goes with detecting aircraft.

We know the range of sizes aircraft typically are, and we know they move across space, so we filter out tiny objects that aren't large enough to be typical aircraft and/or are stationary so we can readily find objects that fit the parameters we set for things like war/spy planes/drones/etc.

When the balloon thing happened, NORAD reduced the filter sensitivity to allow smaller objects to pass through.

Now, we're picking up these small, slow-moving objects that had been filtered out before.

Back to the beach analogy: we essentially turned off the filter and now we’re picking up sea shells, coins and lost rings.

What the objects are and what nation/entity they're from has not been announced. They are simply unidentified flying objects (UFOs) at this point.

These weren’t necessarily launched or sent recently, we just never looked for them. Now we are.

And we’re finding there are quite a few of them there.

[Charity Majors @mipsytipsy]

Last weekend I read @GergelyOrosz's piece speculating on why Apple is (so far!) the only member of BigTech to avoid a round of layoffs. https://t.co/HzUYRfzVSw

(in short: they also didn't participate in the bonkers hiring boom, or compete in the bidding war for talent.)

[ibrahim @ibscribe]

Planning cycles (annual / quarterly / etc) always brings up the topic of output vs. outcomes. One of the better books I’ve read on the topic is Radical Focus by @cwodtke, which is basically a parable about implementing OKRs.

You read that correctly. I studied a book on OKRs. 🧵

[ATumne @ATumne]

KRs without KPIs are no good

[R 'Nearest' Nabors @ SF @rachelnabors]

Today I explained OKRs and KPIs twice and why you should never mistake KRs for KPIs. My fave example from the two showed how you can apply this framework in your every day life..

[Jasper Polak @polak_jasper]

Most companies suck at solving problems

So they pay McKinsey $500K+ to do it for them

Here’s their 7-step problem-solving framework (for free):

[ATumne @ATumne]

Engineering management wisdom

[Charity Majors @mipsytipsy]

Interviewing and hiring managers is really hard.

It’s hard for all the reasons that interviewing and hiring engineers is hard, times 10. It’s easy to give answers that sound decent; it’s harder to evaluate their judgment or dexterity in applying an answer to a situation.

[Gergely Orosz @GergelyOrosz]

Happens every single time:

1. Company realizes: "We pay ~2-3% of our revenue to payment processors! This accounts for more than $1M/year!"

2. "We should cut out the middleman."

3. They hire a team, build their own processing... to realize it's more complex & way more expensive

[gabsmashh @gabsmashh]

treat yourself like I-95 and never stop working on yourself no matter how inconvenient it is for everybody else

[Gergely Orosz @GergelyOrosz]

What many sw engineers don't realize:

The majority of jobs do not hire you to write the highest quality code or produce the cleanest architecture.

They hire you to solve their business problems very efficiently. Sometimes this means high-quality code. Sometimes not at all.

[Brian Feroldi @BrianFeroldi]

Over 51,000,000 YouTube channels exist.

99.8% of them are a waste of time.

Here are 10 channels that are GUARANTEED to entertain you AND make you smarter🧠:

[Marissa Goldberg @mar15sa]

I've helped dozens of companies switch to an async-first work environment. This means fewer meetings and more quality work done.

When companies switch to async wrong, it slows their work. I created the Work Forward Approach to prevent this.

Here are the 8 core principles ⬇️

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

Code review does not work (and asynchronous code review is particularly bad). As Deming said: "You can not inspect quality into a product." NO form of code _review_ yields quality. Collaborative programming that assures that the defects don’t exist to begin with does.

[Adam Grant @AdamMGrant]

A company isn't a family. Parents don't fire their kids for low performance or furlough them in hard times.

A better vision for a workplace is a community—a place where people bond around shared values, feel valued as human beings, and have a voice in decisions that affect them.