Meet GitHub Copilot - your AI pair programmer. https://t.co/eWPueAXTFt

Is code the best way to enforce principles?

Realizing that a more sensible definition of "low-code" may actually be "you do get to write some code but you don't ever have to learn git"

https://t.co/1Ylclvp2rK: Put your Sprints on Autopilot https://t.co/xjpITzLmBP

@nyootron You're featured on BetaList! 🙌 https://t.co/xjpITzLmBP

"Agile proponents worry that a working backwards approach takes the authority and urgency away from teams to launch new code, get feedback from customers, and iterate rapidly. But speed isn’t everything, especially when it comes to breakthrough products."

We never met with customers as we built the software for the original iPhone. We had a small team, and we relied on each other. It was enough.

HA. This spreadsheet "uses the cost of delay to convert CI/CD terms into financial improvements". First-order impacts only, based on rough @circleci pricing. which means it's undershooting the mark by a lot AND YET A+++ FANTASTIC WORK MORE OF THIS PLEASE 😍📈$$$🥰

Great conversation on @joinclubhouse today with @balajis, @NandanNilekani and @BKartRed @NandanNilekani shared his experience working with the Indian government, while @balajis let us in on his vision of the future Here are my (mildly paraphrased) notes, in case you missed it👇

I think it's time to discuss the efficacy of Pull Request Reviews as a way to ensure code quality and shared understanding on software teams. Here's a little thread on some of the experiences I've had in my career, why I think this matters, and what we can do about it.

After accounting for everything, add some buffer(slack), at least in the critical path. Adding buffers is really the state-of-the-art in estimation, each reporting layer adds their own buffers.

Estimates are wrong mostly because of conflating "coding time if everything goes right" with actual delivery time. One must take into account all the tasks needed to deliver - code review, copy review, QA, data migration, etc, their dependencies, and people's existing commitments

In the 20th century, synchronous information flows were most efficient because the alternative was paper. We're in a different century now. Programming helps us create clarity without conversation. We call it Management 2.0 https://t.co/2rsa7JLZ2N

In TDD, if all tests are green we can ship it. Does it matter if I write the code or GPT-3? Is it possible to "reverse-engineer" tests to write code? Continuous functions is one example where it won't work as well I suppose. @KentBeck @unclebobmartin

We still have too much of a schism in our thinking between pre-prod and post-prod verification of our software. Different terms, people, tooling, mindsets. But in both worlds, we're asking the same question. Is our software good enough?

https://t.co/3nDBVzOgZs A not so short post I wrote on Story Points, with fresh and, hopefully, helpful analogies from Physics.

https://t.co/kxxsDDgrMe

@ScottPrugh @ronnyk @nicolefv @jezhumble @davefarley77 @RealGeneKim I see two particular pieces of math that explain the benefits 1. Every dependency you remove doubles your chances of "on-time" delivery, feature flags "break" dependencies - here is an article and online calculator explaining this concept:

"There are 2 fundamentals that matter more than anything else if you're going to make any small team great: first, you've got to have trust. Second, you have to be aligned on a common set of purposes and goals." #TheIdealcast https://t.co/dKwYclGF1U @dksilverman @RealGeneKim