- 146
- 2 586 074
Sleuth TV
United States
เข้าร่วมเมื่อ 18 พ.ค. 2020
Sleuth is a mission control software for teams doing Continuous Delivery. It provides centralized visibility into software delivery progress and performance, plus automation that empowers developers to make frequent deploys easier and less stressful.
Sleuth's metrics tracker gives managers an accurate and ongoing picture of their project's delivery performance as measured by Accelerate metrics.
Sleuth's deployment tracker and automation tools help developers own, coordinate, verify, and streamline deploys, and ultimately improve on the metrics.
Sleuth's metrics tracker gives managers an accurate and ongoing picture of their project's delivery performance as measured by Accelerate metrics.
Sleuth's deployment tracker and automation tools help developers own, coordinate, verify, and streamline deploys, and ultimately improve on the metrics.
Just deploy a tiny change... with Nathen Harvey, DORA Lead Researcher
ICYMI - Nathen Harvey's "Just deploy my tiny change" story was featured on the Nasdaq billboard in Times Square: www.linkedin.com/posts/sleuth-io_just-deploy-my-tiny-change-activity-7270119719246934018-fBYo/
Want more Just stories? Read them all here: www.sleuth.io/just
Want more Just stories? Read them all here: www.sleuth.io/just
มุมมอง: 5
วีดีโอ
If Engineering Managers had their own Christmas...
มุมมอง 5416 ชั่วโมงที่ผ่านมา
What if Engineering Managers had their own Christmas? Who will be put on the naughty list? What presents will be under the tree? Wait, who will be Santa?? Don and Carl explore in this lighthearted video 🎄✨😁
2024 DORA Report Takeaways
มุมมอง 73วันที่ผ่านมา
The 2024 edition of DORA Report (previously State of DevOps) is here 🎉 As you know, each year Sleuth partners with Google Cloud and DORA Institute to conduct an industry benchmark study on what an elite Engineering team looks like. This year, in addition to the core topic of DORA metrics, the report also focuses on relevant contemporary topics, like DevEx. Special guest: Derek DeBellis, Lead Re...
Dashboards are dead; long live Reviews!
มุมมอง 164หลายเดือนก่อน
Dashboards are everywhere. We use them to inform us about the next big decision we need to make, understand the current state of our business, or see how our Engineering org is running. However, are dashboards actually useful? Are dashboards truly solving a problem for us? Ultimately, we don’t really want more data in our lives - we want answers. Getting these answers is not about adding anothe...
Delegate engineering toil to the robots | QCon tech talk
มุมมอง 70ปีที่แล้ว
Robots, AI or otherwise, that's clearly the answer. In this tech talk at QCon 2023, Dylan explains what is engineering toil and how to use robots, er, automations to ease the pain. Check out all of our issue tracker automations here on Sleuth Marketplace: marketplace.sleuth.io/?filter=issues Subscribe: www.youtube.com/@SleuthTV/featured Website: www.sleuth.io/ Live Demo: app.sleuth.io/sleuth/sl...
How I stopped bugging devs for PR format NITs
มุมมอง 83ปีที่แล้ว
How I stopped bugging devs for PR format NITs
Do these 5 things to get started with DORA
มุมมอง 149ปีที่แล้ว
Do these 5 things to get started with DORA
Sleuth | DORA Metrics + Automations = Engineering Efficiency & Continuous Improvements
มุมมอง 19Kปีที่แล้ว
Sleuth | DORA Metrics Automations = Engineering Efficiency & Continuous Improvements
The DevOps tool catapulting Gigpro from slow to swift
มุมมอง 75ปีที่แล้ว
The DevOps tool catapulting Gigpro from slow to swift
How Jackpocket scaled to 220% more software deploys a week
มุมมอง 2.3Kปีที่แล้ว
How Jackpocket scaled to 220% more software deploys a week
Do you think of software developer toil like Atlassian, LaunchDarkly, Okteto and Sleuth?
มุมมอง 120Kปีที่แล้ว
Do you think of software developer toil like Atlassian, LaunchDarkly, Okteto and Sleuth?
Software Teams: You Could Be Getting More from DORA Metrics
มุมมอง 10Kปีที่แล้ว
Software Teams: You Could Be Getting More from DORA Metrics
Unhealthy code? Don't rely on customers to tell you
มุมมอง 19Kปีที่แล้ว
Unhealthy code? Don't rely on customers to tell you
Automate these to ensure high quality code
มุมมอง 1.7Kปีที่แล้ว
Automate these to ensure high quality code
Pulse-check your engineering team performance
มุมมอง 59Kปีที่แล้ว
Pulse-check your engineering team performance
Issue breakdowns and drift details stoke software delivery
มุมมอง 11Kปีที่แล้ว
Issue breakdowns and drift details stoke software delivery
Amazon and Atlassian layoffs, Curl is 25 and more news
มุมมอง 260ปีที่แล้ว
Amazon and Atlassian layoffs, Curl is 25 and more news
New in Sleuth (Jan-Feb '23): Global nav, work in progress, reusable GitHub Actions, customer stories
มุมมอง 41ปีที่แล้ว
New in Sleuth (Jan-Feb '23): Global nav, work in progress, reusable GitHub Actions, customer stories
Real-world use cases for DORA metrics: Unlock your software team's performance
มุมมอง 447ปีที่แล้ว
Real-world use cases for DORA metrics: Unlock your software team's performance
Accurate DORA Metrics: How Sleuth Measures Engineering Efficiency
มุมมอง 171ปีที่แล้ว
Accurate DORA Metrics: How Sleuth Measures Engineering Efficiency
NewStore Uses Sleuth to Optimize Ways of Working
มุมมอง 2.5Kปีที่แล้ว
NewStore Uses Sleuth to Optimize Ways of Working
How Article Turns a Spotlight on At-Risk Work to See Gains Beyond Metrics
มุมมอง 30Kปีที่แล้ว
How Article Turns a Spotlight on At-Risk Work to See Gains Beyond Metrics
Puma + Sleuth = The Swiss Army Knife of Deployment Pipeline Orchestration
มุมมอง 4.4Kปีที่แล้ว
Puma Sleuth = The Swiss Army Knife of Deployment Pipeline Orchestration
How We Created A DevOps Tool Every Software Team Needs
มุมมอง 28K2 ปีที่แล้ว
How We Created A DevOps Tool Every Software Team Needs
Remote vs office, Stack Overflow diversity, CTO skills, Meta layoffs, hiring fraud, and more - News
มุมมอง 2.1K2 ปีที่แล้ว
Remote vs office, Stack Overflow diversity, CTO skills, Meta layoffs, hiring fraud, and more - News
so what do you do with the metrics? "Hey Bob, start programming faster!" lol just another system to make software development more costly and convulated. Great for job security, managers hate this. Just makes devs want EASIER tasks, so they ship "faster". While poor junior get guys huge complex feature that takes forever. So those metrics tell me nothing. Just give me css changes to make those metrics awesome.
We see DORA metrics most useful at a team or service level, and not at an individual level. A team, looking to improve their performance, may see a long review lag time and decide to change their process on PR reviews. A team seeing a high change failure rate may decide to increase deployments or invest in better CI testing. I agree trying to apply these metrics to a single developer, or worse, use them to compare devs with no other context is very harmful.
THis is all just words which I could have read on any website. Nothing is shown. How to capture the metrics is shown which is the main thing.
You mentioned for small teams working in Agile or big teams working on Monolith, smaller the shipping the better it is. But how small the packages should be delivered to Production? Deliver 1 story in an hour to production?? if it is so it also involves testing the code in Production. Can you provide more insights to that?
It depends on the product and situation, but as a general rule, the research backs up the correlation of higher deployment frequency with higher business success. For a self-contained backend microservice, a team may be able to go from coding to shipping within 15 minutes. We did that when working on email sending service in Atlassian. For a monolith that needs lots of soaking and external testing before production, weekly may be the best you can do. There are techniques that can help, such as feature flags and observability, but I think it is wrong to expect every service to deployed multiple times a day.
Am I hearing it wrong about “deployment frequency” definition at :54 sec ? It is number of successful deployments not “ change commit to production “.
Yup, I misspoke and somehow I missed it later. You are correct.
How does tracking team-level metrics contribute to achieving overall organizational outcomes? Is it that each team needs to focus on their own progress to collectively help the organization reach its maturity goals? If yes, is there way to track team level progress?
Thanks a lot for this video. I really appreciate it.
DORA Metrics are metrics, can be misunderstood and misused, leadership as usual look at numbers, but the numbers doesn’t explain the story or the research and all the dependencies that caused these numbers.. and sooner or later, these metrics will be used to measure performance, and payout bonuses, it’s going to be a mess.. just my opinion
Deployment frequency mean How fast you do changes on prod environment. It measure number of changes on basis on weekly or monthly. Most common organisation use project management tools to track those changes
Interesting I need a mentor
Yo these camera angles are leet.
Thank you :)
❤
❤
❤
Min 0:30 - Deployment frequency is NOT "how long it takes to get a change to production". Deployment frequency = How often an organization successfully releases to production Min 0:37 - Change lead time is not "From the developer works on it all the way to it gets in production", that is called Cycle Time "Lead Time refers to the amount of time between when an order is placed and when it is delivered, Cycle Time refers to only the amount of time when actual work is done to complete an order"
You are right - I misspoke on change frequency. Good catch! As for change lead time vs cycle time, the definitions vary depends on who you are talking to. Cycle time, for example, could also include the moment when the ticket is first created or even first requested by a customer. Technically, in the DORA metrics context, change lead time measures them time the change is "ready" or committed to when it reaches production. However, in practice, measuring from PR merge to deploy isn't actually that useful, so people tend to prefer measuring from coding time to production.
technically correct, the BEST kind of correct
Wonderful video, as always😊
Many thanks for this video! About the MTTR, when should we consider a hotfix instead of revert? Is it only about failure natural? Should we consider production as “cumulative stack of changes” and avoid revert even for a critical issue ?
The rule of thumb I use is what gives the best customer experience. If you are deploying frequently and have the ability to push out a fix quickly, then rolling forward is usually the right choice. However, if your deployment process is long and you have the ability to quickly jump back to the previous version, start there then roll the fix out asap. Something to remember with rollbacks is one way things like database migrations. Sometimes, a deployment may contain a database migration that is one direction and can't be reverted, so if that is something your service uses, rolling forward may be your only option. There are ways to structure and rollout database changes that are seamless and can even be reverted (old code on a new db), but they have a cost in complexity, both code and deployment process. That said, I'm usually willing to make that tradeoff.
Beautiful. Incredible. Informational. Slay
People who like Sleuth 👇
We're taking the hobbits to Isengard
First!!!
Can we just appreciate how much time they put into these videos 🙏❤
On Business value points, it is not the metric that corrupts the system, it is the fake managers that are not qualified to lead engineers. You need someone with engineering knowledge to manage engineers or you end up with the usual bloated companies where every problem requires more hires and small features take forever and politics is the real focus vs business value.
Lines of code mean nothing, but that said, if you spend 6 months and all you contributed is 5 lines, then something is wrong either with the work environment or with you.
I agree with your points on lines of code, but I think it is more orthogonal to the general concept of measuring developer productivity. Can you measure the effort, activity, or even the output of developers? Sure, but does any one number accurately represent the "productivity" of the developer? I'd argue there is no such thing or even collection of metrics to "measure developer productivity" accurately and completely. To your point, however, there are indeed insights to be gained by objectively looking at any single metric.
No way to measure an individual developer? That is NOT true, there is clearly a HUGE difference between individual abilities, creativity, passion, learning ability, IQ etc. People who don't want to be measured are the ones who are insecure about their contribution and want to hide it in the team. Managers are a problem when they have no idea what the developers do, non-technical people who call themselves leadership but contribute nothing but a bunch of fake process that wastes time and fake ceremonies that just give PC optics vs really useful activities.
I love this!! Super creative
Big thanks to Nathen Harvey for joining me today! So many insights and great discussions. If you think DORA is just about metrics, you are missing so much!
I like how you had to emphasise that it is "not about the metrics, but about the developers". Obviously just another way to micromanage developers and have micro level insights, so this message had to be stressed, kind off like propaganda brainwashing. Not a sincere product definitely. 100% agreed with @JonathanCrossland and his comment - it is not about developers, but about desire to do more quicker, which in a long term is a recipe for disaster.
*promo sm* 😚
In my experience it's the opposite. We say it's impossible to generate duplicate UUIDs, when what we mean is you'd have to generate a billion per second for 85 years to have a 50% of a collision occuring
can we generate C++ videos with it?
Wow dad you're becoming a tiktok star
Very interesting 40 minutes...good work! Value prop chat was a worthwhile listen - M
I ❤️ your videos 😜🙂😜🙂😜😜😡🙂😜🙂
WOW SO INCREDUBLE WOWZEES ISSUE BREAKDOWNS ARE SO COOL
I really like your videos, very useful. Suggestion: make the music way lower in volume
'Promosm'
OpenFeature is the open standard for feature flagging.
Thanks again to my guests Daniel and Torsten. How do you use DORA metrics and how do you enable your teams to learn from them?
Maybe Habit Teacher could be a headline that could spark some understanding and foster a conversation about what we do. You know I love your videos, but just to iterate. That amount of distance between the camera and you in these videos is the distance you should keep 😆
Very well explained! thank you!
good day~buddy! you created unreal video.🤩
Are you running selenium tests with every build on main? Or only against feature branches? Aren't they slowing down the deployment pipeline time?
Both actually. We use the CircleCI tool to automatically split tests, based on execution time, into batches. This allows us to run all the tests within 5 minutes or so.
If it needs an approval for deploying to production, is it continuous deployment?
The CircleCI workflow is implemented using an approval, but we use Sleuth Actions to automatically approve it after 5 minutes of a healthy status on staging. Thus, in practice, it is completely automated, but what is nice about the approval is it gives us an easy way to block the deployment or manually override if the staging unhealthy status is invalid.
Loving this man, keep it up :D
ρяσмσѕм 👊
There are so many bad assumptions here. These metrics do not show anything to developers. Every time you sample these metrics the context is different. Different work, task, code, requirement etc. Shipping more and smaller is wrong. Ship well and when necessary is more correct. Small changes can easily affect a lot of things. The assumption here is that a small change is small. Sometimes a small change is huge. It also has nothing to do with quicker. Being fast is nonsense for developers, it is a business desire. We should stop trying to apply business desires as a positive to developers. Change failure rate is bad, because a failure ALWAYS changes.the nature of a failure is always different, in how you measure and how it works.
I think both things can be true. The State of DevOps research showed by surveying 30+k companies that deploying frequently did strongly correlate to organizations achieving their business goals, but as you correctly point out, at the micro it is a lot more complex. I noticed you have a TH-cam dev channel, would you be up for a collab/debate/discussion/whatever? I'd love to chat further :)
Context matters here. The goal is to be capable of releasing software on demand. This typically means at the tempo of the business value proposition(features and bug fixes). The DORA metrics align to this concept, just balance them against the deployment cadence needed to achieve business value.
@@donbrown573 This is basic correlation/causation cargo cult fallacy. Just because successful people disproportionately own BMWs does not mean owning a BMW will make you successful.
I've watched this video multiple times in the past months, very insightful, thanks!
I love the more professional look with this one. Love the thumbnail too. The footage really adds to the video in a good way. Short, but sweet. Great job with this one. For next time, your lighting was a little weird but thats totally fine. Good job!