John Ferguson

It's been particularly gratifying to see such positive reactions to the announcements Grafana Labs made during GrafanaCON last week. For those who couldn't make it or want to relive all the keynote highlights, the recording is now available on our YouTube channel and includes a demo of Explore Metrics and Explore Logs, along with Grafana Alloy, Loki 3.0, and the Grafana App Platform. So many users and customers are excited about Explore Metrics coming out of Grafana 11, and once you watch the demo, you'll see why. https://lnkd.in/gigW_kb9

58

1 Comment

If you need a BYOC solution, this is the way

1

Many organizations still use rolling restarts to fix problems, but it simply isn’t acceptable anymore. Check out Sumo Logic CEO Joe Kim's latest blog to learn why standards for #observability and #reliability are changing and what you need to stay ahead.

3

Being "Enterprise Ready", or crossing the chasm, is critical "milestone" that startups must go through, at least those in the enterprise B2B space. I outline the impact that enterprise customers have on processes, product capabilities and GTM. The evolution to be enterprise ready can be hard, but the payoff can be substantial https://lnkd.in/gp_BPrvq

15

2 Comments

Get your code into production. One of my pet peeves is when a team develops new functionality QA for months before pushing to production…then are surprised when they try to push to production and (1) 4233 things break and (2) their business counterparts are underwhelmed with the result. My teams generally push to production every sprint - each user story must go into production Developing a muscle for regularly and frequently pushing changes as an IT/data organization forces you to: 1️⃣ Automate: common processes, security checks, quality 2️⃣ Containerize: everything should be reproducible including environments and packages 3️⃣ Decouple: if your deployment breaks it should not affect other teams/deployments 4️⃣ Simplify: deploy less at a time, also reducing risk

5

Want to supercharge your database performance? Actian Zen has you covered with its latest enhancements. Discover how these updates can benefit your business in Actian's newest blog post.

5

🚨 Happening tomorrow at 10 AM PT! Discover how to develop, manage, and integrate workflows using your code and systems to optimize your agreement processes with the ✨ new ✨ #Maestro API (beta). Joining this webinar will provide you with the opportunity to: 👉 Learn Integration Techniques: Gain insights on how to seamlessly integrate the new Maestro API with your existing systems. 👉 Explore Use Cases: Understand practical applications and use cases to effectively use the Workflow Designer. 👉 Interactive Learning: Participate in a live Q&A and watch demonstration coding solutions in real-time. 👉 Early Access: Be among the first to join the beta program and start utilizing the new features. This session is perfect for developers and technical professionals looking to streamline their agreement processes with advanced API integration.

1

Performance testing can seem like a complex puzzle, especially when it comes to interpreting the results. 😕 What do all those numbers really mean, and how do they translate into actionable insights? Our latest Tech Talk episode with Amit Elimelech and Yam Shal-Bar from Radview Software breaks down the most critical performance testing metrics and explains their significance in clear, easy-to-understand terms. Whether you’re a beginner or an experienced tester, you’ll gain valuable insights into how to measure and improve your application’s performance. From correlation vs. parameterization to analyzing test results, this episode will leave you feeling confident in your ability to deliver high-performing applications. Tune in and learn how to make sense of your metrics and use them to improve your results! 👇👇👇 https://lnkd.in/gSzBJuDk #loadtesting #loadtestingsolution #endtoendloadtesting #performancetesting #performanceengineers #TechTalk #TechTalkbyTestGuild #Radview #WebLOAD #AI #AITools #AIinTesting

28

The entire plot of the Iliad is like one big code review gone bad. You just spent the better part of the week painstakingly building out that killer new feature. In fact, it's some of your best engineering, the unit tests are a work of art, and the function names would make Uncle Bob proud. But not so fast! The next thing you know your work is completely ripped apart by someone more senior. This is what sparked the rage of Achilles! Agamemnon used his opportunity to save the Greek army as a means to assert his dominance over Achilles, rather than leading as he should. Agamemnon took what was treasured by Achilles in front of everyone setting in motion the epic on anger and pride. At one time or another we've all been tempted like Agamemnon when giving a review. So remember, code reviews aren't a means to satisfy our own pride and insecurities about our position. Have you ever been in a code review that felt more like a battle than a collaboration? Let's turn these moments into opportunities to learn and grow with each other rather than using each other. How do you ensure your code reviews are constructive and empowering? "Achilles’ wrath, to Greece the direful spring  Of woes unnumber’d, heavenly goddess, sing!  That wrath which hurl’d to Pluto’s gloomy reign  The souls of mighty chiefs untimely slain;" - The Iliad, Book 1

7

1 Comment

I've been toying with this idea for the past few weeks: there's a limited number of production lines of code a team can have per engineer before quality starts to suffer through unexpected bugs or reliability issues. Let's call it team's carrying capacity :-) Teams can increase their carrying capacity by investing in testing and integration practices, reducing model complexity, and as their engineers learn more about the domain and the tech stack. Carrying capacity probably drops temporarily as you add more people to the team or add more external dependencies to the project. This framing is interesting because it opens up interesting trade-off discussions as: * is adding engineers to the team worth it? our carrying capacity will drop for the next 6mos so we won't do new stuff or will start seeing bugs in existing stuff if we were already at capacity * not deprecating a project will either decrease our quality or prevent us from building new features * is it worth adding a dependency to the project instead of doing it ourselves? It feels intuitive, but obviously needs more digging. I'd be curious to see if tools like Sourcegraph or Swarmia could be used to start measuring the ratio of production lines of code / engineer and see if there's something useful there. Has anyone seen attempts at measuring something similar?

55

14 Comments

Great podcast on asynchronous messaging, it's origins, criticality, standardisation and evolution. Well done AndySC and Clemens Vasters, well worth a listen! https://lnkd.in/ewBQJtAC

30

1 Comment

I like beer, and don't mind it in a can. From the perspective of the traveling canning line business, there's a powerful insight into providing flexible, niche services, which parallels Software as a Service (SaaS) models. ° Targeting the In-Between Market: Traveling canning lines serve breweries too small to invest in their own equipment but large enough to need consistent service. Similarly, SaaS companies target businesses that require specialized services but aren’t ready for the cost and complexity of building in-house infrastructure. Both models thrive by offering scalability without heavy up-front investments. ° Flexibility as a Core Value: Traveling canning lines are mobile and adaptable, servicing multiple clients with varying needs. SaaS providers similarly offer plug-and-play solutions, serving a broad range of businesses without the need for heavy customization or on-premise deployment. Just as traveling canning lines save breweries from bottlenecks, SaaS solutions prevent businesses from needing to invest in costly, permanent tech too early. ° Serving a Growth Phase: Both businesses provide critical support during a company’s growth phase. They offer agility and scalability until clients eventually outgrow the need and invest in permanent infrastructure. However, by adding premium services, SaaS companies can remain valuable even as clients scale, mirroring how traveling canning lines can stay relevant through flexibility and premium offerings. In essence, like the traveling canning line, SaaS thrives by serving businesses in transition—offering flexibility, scalability, and the ability to delay costly investments. #saas #no_pickle #LinkedInLunacy #beer

10

2 Comments

Markdown to... command line app - wat? That's the topic for today's unsolicited face time. A single Pipedown pipeline can be used in numerous contexts thanks to the way it consistently accepts inputs and produces outputs. I waffled about my love of pipelines a while back: https://lnkd.in/gERrAsvA Though it's much handier to see in action! https://lnkd.in/giR-KVDT Let me know your thoughts 🚀

4

Improving the CI/CD build environment is critical to developer ease, doing so in a sustainable way is icing on the cake! Read more about Embracing Efficiency: The Future of CI/CD with Ampere on GitHub Actions - in case you missed the announcement of hosted GitHub Arm64 builders powered by Ampere Altra recently: https://lnkd.in/dRKVCRbc -

19

1 Comment

Learn about the evolution of the Elasticsearch .NET client and how it will gradually phase out the old NEST library: https://gag.gl/tCCrQX #ElasticSearchLabs

2

Appreciate seeing that App Store review time has roughly halved since the summer (down to about 4hrs compared to 9hrs). I can't help but wonder why starting a review for Testflight external beta is still at the 8hr mark (though I certainly understand that those should be lower priority compared to production builds). I +1'd the Google Play IN_REVIEW status issue and recommend others do the same! On the green goblin [Android] side of things, I've personally experienced a lot of variance lately, resulting in some unexpectedly [days long] reviews. I also see that Google recommends waiting for production reviews while alpha reviews are in-progress, citing longer review times. My experience has been the opposite, where the synchronous reviews results in a MUCH longer review cycle. The numbers point to improvement, but there's still further progress to be made, both for timing and consistency of policy enforcement.

9

1 Comment

Many strategies get sold in a packaged format. Buy this and it will solve all of your problems. And many "success" stories repeat the same pattern: Company X implemented Y and they got cost reduction, speed, agility and are on their way winning a nobel price. Which might be true in their context yet seldom is in another context. Models like the ones in #cloudstrategy and #platformstrategy by Gregor Hohpe are very helpful tools to understand what you are buying and getting yourself into.

1

With DORA metrics, the precision matters more as the metrics matter less. It doesn't matter if the number lacks precision when it takes 30 days to get a change into production. You could be +/- 5 days, and you'd still be deploying "monthly". When you reduce this to less than a day and start measuring in hours, the lack of precision would mean the noise disguises the signal. However, you don't need to fix this as your constraint has likely moved elsewhere. #DevOps #Metrics

19

3 Comments