← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 89
  1. Here is a small tip that has saved me a lot of time: Always log your entire parsed configuration when your service or application boots.

  2. I think many companies could use a formal learning review process for non-mutual employee departures.

  3. On Challenging AI

    In April, I published the article “What type of AI usage?”

  4. What type of AI usage?

    These past years, I have had a lot of people reaching out and wanting to talk “AI” (or LLMs) with me.

  5. I was once assigned as the onboarding buddy for my then-new colleague Jeff.

  6. Code freezes

    Code freezes commonly stirs up strong emotions within the engineering community.

  7. The term AI is everywhere these days.

  8. A shell --dry-run trick

    I recently read the blog post “In Praise of –dry-run”.

  9. If a tree falls in a forest and no one is around to hear it, does it make a sound?

  10. An incident framework usually has the concept of an incident priority: priority 1 (“Systems are DOWN!”)

  11. Incident process?

  12. Kagi Translate supports translating from English to LinkedIn Speak.

  13. I have never been a big fan of how some people equate “contract testing” with using something like PACT.

  14. Work Charades and Values

    Charade.

  15. The Dangers of an IDE

    I recently stumbled across the post “Does Visual Studio Rot The Mind?”

  16. This post will be the first in a series of blog posts where I will be talking about the limitations of Apache Kafka as a task queue and how we overcame these limitations at a previous employer where I managed tens of fairly high-throughput Apache Kafka cl…

  17. A one-on-one template

    I have used the same one-on-one template with my last six managers, including other regular check-ins.

  18. Raise and Release

    Amazon’s founder Jeff Besos is famous for his “disagree and commit” management principle used in leadership.

  19. Pair and mob sessions

    Many people believe pair programming has to be a session where coding is the only action.

  20. Throughout my career I have heard soooo many people complain about the general concept of process - the standardized series of steps needed to perform a task.

  21. In safety systems engineering (SSE) people talk about “safety type 1” and “safety type 2”.

  22. I recently read the article “Why I don’t like discussing action items during incident reviews” by Lorin Hochstein.

  23. Earlier this year, I was on a complex multi-team project that was handed to us by our product organization.

  24. In software engineering jargon, people often speak of “performance” without defining specifically what they mean.

  25. In the article “Natural solutions”, I wrote […] product engineering is equally much about defining the problems we are trying to solve. and I think that statement is somewhat more controversial than first meets the eye.

  26. Natural solutions

    I recently wrote about the solution vs. problem space.

  27. Today I wanted to write something about the recent CrowdStrike Falcon incident and about one contributing factor, namely centralised risk management.

  28. In the article Scaling the Practice of Architecture, Conversationally by Andrew Harmel-Law he talks about the concept of Architectural Decision Records (ADRs) as a way to align and document architectural decisions.

  29. The Problem Space

    As engineers, we are great at solving problems and working in the “solution space”.

  30. There is a belief that “software architecture” only involves designing the “big picture” of how software is built.

  31. Innovation is the skill of going from idea to action.

  32. What's in a good answer?

    This is a follow-up on How to Ask Good Questions.

  33. On staging environments

    Info This article is about staging environments, but it almost equally applies to the concept of single-tenant environments.

  34. I think our software industry sometimes is blindsided when it comes to security.

  35. The Agile Manifesto states Responding to change over following a plan This implies that we must design our systems to be malleable to change and allow for evolutionary design.

  36. Background Story Link to heading Imagine you’re mentoring an engineer who’s eager to brush up on their coding skills after a hiatus from programming.

  37. I was on my first podcast discussing the topic of “SRE & Full Ownership”!

  38. Info This post is part of my blog series about My Simplicity Toolkit.

  39. I recently read the excellent article Data is not a Strategy.

  40. I once almost burned out

    I have been very close to burnout two times in my career.

  41. An AI/ML accuracy tale

    I recently read the article “What I learned getting acquired by Google” by Shreyans Bhansali.

  42. Info This is the second part of two talking about my simplicity toolkit when programming.

  43. Info This post is part of my blog series about My Simplicity Toolkit.

  44. Info Blog series: My simplicity toolkit: Intro (this page) My simplicity toolkit: Programming (part 1) My simplicity toolkit: Programming (part 2) My simplicity toolkit: Testing My simplicity toolkit: Architecture My simplicity toolkit: Patterns “Perfecti…

  45. Back in the day when The Cloud (AWS) was The New Hot Thing™️, I thought autoscaling would solve most of our problems related to costs, availability, performance, and scalability.

  46. Goodbye Disqus

    Enterprise hostage situation: First @disqus roles out ads on all free tiers.

  47. As engineers, we all occasionally need to reach out and ask for help.

  48. MTTR is the wrong metric

    Shower thought: Why do we talk about MTTR (Mean Time To Resolution), when it’s a latency?

  49. Mean vs. median

    Over the years, I have heard many people say something like Over 50% of people think they are better than the average car driver.

  50. Microretros

    I tend to love a “quick feedback”.