Shaun Abram

Northern Ireland native, Northern California local.
Software and leadership.
Views probably stolen from someone smarter.

[Shaun Abram @shaunabram]

4. Work together

For the I95 "project, local, state and federal officials coordinated closely with each other.

In your world, that may mean ensuring that Software is coordinating and collaborating with peer departments such as Legal, Marketing, and Security.

(5/5)

[Shaun Abram @shaunabram]

I loved this article in the Washington Post, ostensibly about how "We fixed I-95 in 12 days", and "lessons for U.S. infrastructure", but I think it is really invaluable lessons about leadership in general...
(1/5)

https://t.co/qy4O8hg4hY

[Shaun Abram @shaunabram]

3. Encourage creativity

Allow everyone to bring their ideas forward. You will move faster and people will feel real ownership in the project.

(4/5)

[Shaun Abram @shaunabram]

An older but still relevant article from @matthewpskelton. He discusses antipatterns, including DevOps silos, and better team topologies to try.

What Team Structure is Right for DevOps to Flourish?https://t.co/ON6eRjGhMz

[Shaun Abram @shaunabram]

Some thoughts on why, as an Engineering Manager, your team is not a democracy.

https://t.co/n7aJZySJoX

[Shaun Abram @shaunabram]

Interesting article from @skamille on How to handle a reorganization as an engineering manager
https://t.co/VnevoRcnrM

[Shaun Abram @shaunabram]

Shift left conventionally means testing earlier in the development cycle.
A better definition may be testing earlier 𝘢𝘯𝘥 more frequently.
I would suggest it can also mean shifting left in the deployment pipeline (and down the Testing Pyramid).
https://t.co/Gmrzu8VFrn

[Shaun Abram @shaunabram]

“Some books should be tasted, some devoured, but only a few should be chewed and digested thoroughly.”

― Sir Francis Bacon

[Shaun Abram @shaunabram]

@jkodumal Yes, and I should have provided source!

Forsgren PhD, Nicole; Humble, Jez; Kim, Gene. Accelerate Ch 2 Measuring Perfomance (p. 51 Kindle Edition).

I also just realized I have 2 paper copies and a Kindle copy of Accelerate. A book worth buying 3 times :-)

[Shaun Abram @shaunabram]

@jkodumal But to (not) answer your question, I don't know of a way to reduce batch size other than by deploying frequently. Interested to hear if there are ways...

[Shaun Abram @shaunabram]

@jkodumal Deployment frequency does seem a great proxy for batch size. Where it fails is in distinguishing between apps updated infrequently but still deployed every time, vs updated frequently but deployed infrequently. LoC changed per release can help distinguish.

[Shaun Abram @shaunabram]

@DavidOG87361059 I would say that a unit is the smallest piece of code/functionality that can be tested in isolation. Perhaps a single line, or an if clause, or a method.

A unit test executes that unit and confirms the behavior or result is as expected.

[Shaun Abram @shaunabram]

I liked this "We need to talk about testing" post by Dan North (@tastapod) and thought worth sharing...

https://t.co/S0lGre0yQF

A short thread (1/10)

[Shaun Abram @shaunabram]

@DavidOG87361059 If the bug found in an integration test can be recreated in a unit test, it will run faster and typically run more often too. Shifting left, where possible, results in a faster feedback loop.

[Shaun Abram @shaunabram]

10/10

5. North concludes with "We should all be thinking about how testing and testers fit into software development."

Great article, highly recommend.

[Shaun Abram @shaunabram]

9/10

Shifting left doesn't mean doing traditional testing earlier, we are setting ourselves up to never need it at all.