Deep dives into software, hardware, and the ideas changing how we build things.
We cover the technical side of technology — not just the product launches and press releases, but the architecture decisions, the tradeoffs, and the engineering culture that affects what gets built. We dig into the messy reality behind the polished demos.
Topics we cover: Software · Hardware · Developer Tools · AI & Machine Learning · Open Source · Security
The shirt reads I HAD POTENTIAL in white capitals. Beneath the words, a white curved ramp descends from an upper-left ledge to a lower-right flat. At the top of the ramp, on the upper-left ledge, sits a dashed empty circle. At the bottom, on the lower-right flat, rests a solid white ball. The ramp is curved, not a straight diagonal. That curve matters more than the slogan.
Most joke shirts with this phrase stop at the words. The sentence alone is a familiar piece of self-deprecation: past tense, closed case, a person announcing that whatever promise they once carried has already been spent. It is the kind of line you can put on a mug, a hoodie, a Slack emoji. The drawing is what makes this one worth looking at, because the drawing does not simply illustrate the sentence. It argues with it.
Read the diagram literally. A ball at the top of a curved ramp has gravitational potential energy relative to the bottom. The dashed circle marks where the ball was. The solid ball marks where it is. The ramp is the path between those two states. In physics, potential is not a moral quality and it is not a fixed quantity. It is a function of position and configuration. Move the ball, change the configuration, and the potential changes. The diagram is not saying the ball was wasted. It is saying the ball moved.
That is a different joke than the words alone. The words say: I had potential, and now I do not. The drawing says: I had potential at the top of the ramp, and now I have a different potential at the bottom, because potential is relative to where you measure it. The dashed circle is the ghost of the earlier state. The solid ball is the current state. Neither one is a failure. They are two positions on the same curve.
I keep coming back to the dashed circle. It is the only element on the shirt that is not filled in. Everything else is solid white: the letters, the ramp, the ball. The dashed circle is an outline of a shape that used to be occupied. In a packet capture, a dashed line often marks a path that was attempted but not completed, or a route that exists in the routing table but is not currently forwarding. The dashed circle on this shirt reads the same way: a position that was available, a state that was possible, a configuration that has since changed. It is not an accusation. It is a record.
The curved ramp is the other quiet decision. A straight diagonal would have made the joke simpler: ball rolls down a line, potential becomes kinetic, done. The curve introduces a changing slope. On a curved ramp, the acceleration is not constant. The ball’s experience of the descent depends on where it is on the curve. That is a more honest picture of how most technical careers actually go. The slope changes. The forces change. The ball does not fall at a constant rate, and neither does anyone’s trajectory through a stack of protocols, a series of jobs, or a long incident.
I am not going to claim the shirt is making a rigorous physics argument. It is a cartoon. But the cartoon is doing something more interesting than a slogan. It is using the visual language of a potential-energy diagram to complicate a sentence that would otherwise be pure self-deprecation. The words say the story is over. The drawing says the story is a state change. That tension is the whole object.
For readers who spend their days reading state machines and protocol diagrams, the shirt is a small pleasure because it rewards the same habit: look at the diagram, not just the label. The label says I had potential. The diagram says potential is a function of position. The dashed circle says here is where the position used to be. The solid ball says here is where it is now. The ramp says the path between them is curved, and the slope changes. None of that is a claim about the wearer’s actual life. It is a claim about how to read the drawing.
There is a work-culture reading here too, and it is worth being precise about it. The phrase I had potential is often used as a boundary marker in technical organizations: a way of saying I was once considered promising, and now I am considered something else. The shirt does not resolve that tension. It just puts it on a ramp. The dashed circle is the performance review you did not get. The solid ball is the on-call rotation you did get. The curve is the org chart. That is not a rigorous analogy, and I am not pretending it is. It is just the reason the shirt lands for a certain kind of reader.
The design is minimal in the way that technical diagrams are minimal: white on a dark ground, no decoration, no extra text. The only elements are the words, the ramp, the dashed circle, and the ball. That restraint is what makes the double meaning legible. If the shirt had added a caption or an arrow or a second joke, the diagram would have collapsed into a meme. Instead it stays a diagram, and the diagram does the work.
If you want to look at the listing, it is the I Had Potential shirt from Quirky Cotton Collective. The retail title calls it a funny physics pun and a sarcastic minimalist quote. The visual observation is more specific: white capitals, a curved descending ramp, a dashed empty circle on the upper-left ledge, a solid white ball on the lower-right flat. That is the object. The rest is interpretation.
Editorial note: this publication and Quirky Cotton Collective share an owner.
A trans-Pacific SRT contribution can look healthy on every superficial check and still bleed frames. The encoder reports a steady bitrate. The receiver locks and plays. A quick ping to the ingest endpoint shows a round-trip time that fits comfortably inside the configured latency. Then a burst of loss hits, the NAKs go out, the retransmissions come back — and the receiver drops them anyway because they arrive after their presentation deadline. The stream does not collapse; it degrades in a way that is easy to blame on the encoder, the CDN, or the venue uplink. The first thing to inspect is the latency setting, and the first thing to understand is that it is not a delay knob. It is a deadline.
SRT’s own documentation is explicit about the scope of the term. Latency in SRT is “only the delay introduced by sending over the network,” measured between the srt_sendmsg2 call at the sender and the srt_recvmsg2 call at the receiver (libsrt latency documentation). It is not glass-to-glass latency, and it is not a fixed sleep inserted into the pipeline.
The mechanism is Timestamp-Based Packet Delivery (TSBPD). Each packet carries a sender timestamp. The receiver computes an expected arrival time from that timestamp and the connection’s start reference, then schedules delivery at:
PTS[x] = ETS[x] + LATENCY + DRIFTwhere PTS is the presentation time, ETS the expected arrival time, and DRIFT a correction for clock-rate divergence between the two hosts. The same document explains why drift tracking exists: sender and receiver clocks are not identical, and over a long session the mismatch can imply a negative network delay or an absurdly large one.
Read that formula as a scheduling rule. A packet that arrives early waits in the receive buffer until PTS. A packet that arrives late — because the path spiked, or because it had to be retransmitted — is handed up late or, if it misses the deadline, dropped as too late. The latency value is the width of the window in which a retransmission can still be useful. Everything else follows from that.
The socket-options reference lists SRTO_LATENCY with a default of 120 ms and a settable range starting at 0 (SRT API socket options). That default is inherited from UDT-era assumptions and is a poor fit for any path that crosses an ocean.
The naming is a common source of confusion. SRTO_LATENCY is the legacy, symmetric option. In modern libsrt, the negotiated latency is derived from SRTO_RCVLATENCY on one agent and SRTO_PEERLATENCY on the peer. The documentation is careful to say these options “do not define the true time interval between the srt_sendmsg2 and srt_recvmsg2 calls for the same packet.” They add receiver-side delay to compensate for late arrival or retransmission. The negotiated value may differ from what either side individually configured; always read back the negotiated value on both ends after connection rather than trusting the configured value on one side.
SRT recovers loss through selective retransmission (ARQ), optionally combined with forward error correction; the protocol draft describes both mechanisms and their combination as a design choice spanning “the lowest possible latency to the highest possible reliability” (draft-sharabayko-srt-01). The ARQ path is the one that matters for sizing.
When the receiver detects a gap, it sends a NAK. The sender retransmits. The retransmitted packet must arrive before its PTS. The minimum cost of that exchange is one round trip: NAK out, retransmission back. In practice it is more, because the NAK is generated after the receiver has observed the gap, the sender may be pacing other traffic, and the retransmission shares the path with the primary stream. A window that equals one RTT leaves no margin for any of that.
Haivision frames the sizing question with an RTT multiplier: “SRT Latency = RTT Multiplier * RTT,” where the multiplier reflects “the maximum number of times SRT will try to resend a packet before giving up” (Haivision RTT multiplier guidance). Their table gives a minimum multiplier of 3 at ≤1% loss and 4 at ≤3% loss, with corresponding minimum latencies of 60 ms and 80 ms for paths at or under 20 ms RTT. The same page is candid about the table’s provenance: the numbers are “intended as conservative guidance,” based on “a model using an earlier version of SRT,” and newer versions “may incorporate more efficient retransmission algorithms.”
That caveat matters. The widely repeated “4× RTT” rule is vendor guidance derived from a constant-loss model, not a protocol requirement. It does not appear in the SRT draft. It is a defensible starting point and a bad finishing point.
Engineers who tune TCP for long-haul paths tend to reach for the same instincts here, and the instincts mislead. TCP maintains a smoothed RTT and an RTT variance, computes a retransmission timeout from them, and backs off exponentially on repeated loss; RFC 6298 also requires that a computed RTO below one second be rounded up to one second (RFC 6298). That is an adaptive timer with a conservative floor.
SRT does not work that way. The latency is negotiated at connection setup and held for the session. There is no exponential backoff on the delivery deadline, and there is no one-second floor. Importing TCP’s numbers into an SRT configuration produces windows that are either far too large — adding avoidable delay — or sized against a mean RTT that the path exceeds routinely. The relevant statistic for a fixed deadline is not the mean. It is the tail.
A path with a 150 ms median RTT and a 120 ms configured latency is already misconfigured: the median exceeds the window, so ordinary packets are arriving after their deadline before any loss occurs. But the more common failure is subtler. A path with a 90 ms median and a 120 ms window looks fine on average and drops retransmissions every time the path spikes to 160 ms. The mean hides the events that matter.
The sizing procedure is a measurement procedure:
Consider a contribution path with a 150 ms median RTT, a p99 of 220 ms, 2% average loss, and occasional 100 ms outages during peak hours. These numbers are illustrative, not measured; substitute your own.
At the 120 ms default, the window is narrower than the median RTT. Every retransmission is guaranteed to miss its deadline, and even primary packets arriving on the slow side of the distribution are at risk. The receiver will show too-late drops continuously, and the operator will see intermittent macroblocking that correlates with nothing obvious.
At 450–600 ms, the window covers the p99 RTT plus a retransmission round trip plus margin for a burst. The cost is explicit: roughly 0.3–0.5 seconds of additional end-to-end delay relative to the default. Whether that is acceptable is a production decision — a remote commentary feed and a live auction have different budgets — but it is a decision that should be made deliberately, with the number written down, rather than inherited from a default that was never intended for this path.
The trade is not free in the other direction either. A window sized at 2 seconds “to be safe” buys recovery margin you will never use and pays for it in delay on every packet, including the ones that arrived on time. The window should be the smallest value that covers the tail and the burst, not the largest value you can tolerate.
No. It increases the receiver-side deadline — how long a packet may wait in the receive buffer before being handed up or dropped. The packets still cross the network at whatever speed the path provides. The added time is buffer time, which is why it shows up as end-to-end latency but does not change the RTT.
No. It appears in Haivision’s vendor documentation as guidance derived from a constant-loss model on an earlier SRT version. The SRT IETF draft describes the protocol mechanisms but does not prescribe a latency-to-RTT ratio.
Because ping measures a sample, not a distribution, and because ping does not measure burst loss. A path can have a healthy median RTT and still spike above the configured window often enough to drop retransmissions. Capture the p95 and p99 over a full day and compare those against the negotiated latency.
The socket-options reference marks SRTO_LATENCY as restricted before connection; the negotiated value is established at handshake. Plan to reconnect with the new value rather than expecting a live adjustment.
FEC can reduce the number of retransmissions required, which reduces pressure on the window, but it does not eliminate the need for a window that covers the path’s tail RTT. The two mechanisms are complementary; the draft describes them as usable separately or combined.
The first thing the shirt shows is not a cat. It is a notification. A white rounded banner, a small bell icon, and the sentence There is motion at your front door — the exact register of a consumer doorbell app, stripped of its app. Below that banner sits a circular, green-tinted view: an orange tabby pressed absurdly close to the lens, wide-eyed, porch siding and lights receding behind it. The design is a screenshot of a moment, printed on cotton.
That ordering matters. The banner comes first, the image second, which is how the alert actually reaches you: the phone buzzes, the text arrives, and only then do you open the feed to find out what the motion was. The shirt reproduces the sequence faithfully. It is not a picture of a cat on a porch. It is a picture of an alert about a cat on a porch, and the joke lives in the gap between the two.
Look at the geometry. The notification is a rounded rectangle, the kind of shape a mobile OS uses for a heads-up banner. The camera view is a circle — the fisheye crop that doorbell hardware produces, tinted green by night vision or by the sensor’s low-light processing. The cat is not centered in a portrait; it is too close, filling the circle, nose nearly touching the glass. Behind it, the porch reads as ordinary architecture: siding, a light fixture, the suggestion of a doorway.
None of that is decorative. Each element is doing specific work. The banner establishes the system — a sensor, a threshold, a rule. The circle establishes the medium — a cheap wide-angle lens doing exactly what it was built to do. The cat establishes the payload — the thing that tripped the rule, and the thing that turns out to be ridiculous. The design is legible in about a second and a half, which is roughly how long a real notification stays on screen before you swipe it away.
What makes the shirt work is that the notification text never winks. There is motion at your front door is a factual statement, grammatically flat, delivered with the confidence of a system that has correctly detected a change in state. It does not say a cat is here. It does not say surprise. It says motion, which is technically true and completely useless, because the motion is a tabby with its face against the camera.
That is the whole joke, and it is a joke about classification. A doorbell camera is a motion detector with a camera attached. It is very good at answering did something change in this region of the frame. It is not asked to answer what changed, and on the evidence of this design it does not try. The banner reports the trigger; the circle reports the truth; the gap between them is where the humor sits. The shirt is funny because the system is honest and the system is also, in this instance, an idiot.
I find that more interesting than a straight cat picture. A cat on a shirt is a cat on a shirt. A cat inside a notification about a cat is a small diagram of how automated systems talk to people: terse, confident, and frequently missing the only detail that matters.
Strip the banner and you have a green-tinted cat. Charming, forgettable. Strip the cat and you have a sentence. The sentence is what people will read across a room, and it is the sentence that carries the recognition — anyone who has ever had a phone buzz with that exact phrasing knows the small lurch of what now before the feed loads. The design borrows that lurch and then defuses it with a face.
This is also why the shirt reads as a there is motion at your front door shirt rather than a cat shirt with a caption. The phrase is the object. The cat is the punchline. If you have spent any part of your working life writing alert text, status messages, or on-call pages, the flatness of that sentence is its own quiet pleasure. It is a model of the form: short, declarative, no adjectives, no apology. It tells you something changed and leaves the interpretation to you. The shirt then supplies the interpretation, and the interpretation is a cat.
The green-tinted circle deserves its own paragraph because it is doing more than framing. A doorbell camera does not show you a scene; it shows you a slice of a scene, chosen by a lens and a sensor and a compression pipeline, delivered at whatever resolution the uplink allows. The circle is the visible edge of that pipeline. Everything outside it — the rest of the porch, the street, whatever the cat was actually doing two seconds earlier — is gone. What you get is a tight, slightly distorted, green-cast crop of the one thing that crossed the threshold.
That is a recognizable experience for anyone who works with monitoring. The dashboard shows you the metric that fired, not the system that produced it. The alert shows you the symptom, not the cause. The shirt puts the same shape on a chest: a bounded view of a small event, presented as if it were the whole story. The cat’s expression — wide-eyed, slightly indignant, extremely close — is the expression of a subject who did not consent to being the payload.
I want to be careful here, because it would be easy to overread the design. The shirt does not demonstrate anything about camera systems, detection accuracy, or the state of consumer hardware. It is a drawing of a notification and a drawing of a cat, arranged to be funny. The green tint is a visual convention, not a measurement. The fisheye circle is a shape, not a specification. I am reading the artwork, not citing it.
What I will say is that the design is unusually disciplined about its own joke. It does not add a second caption. It does not label the cat. It does not explain the alert. It trusts the viewer to recognize the banner, recognize the crop, and supply the missing half-second of context. That restraint is why it works as a shirt rather than as a meme screenshot: the composition is complete on its own, and the punchline is structural rather than textual.
Most of what I write here is about the machinery between a camera and a viewer — the encoders, the transport, the retransmission windows, the places where a packet goes missing and a frame never arrives. This shirt is not that. But it is a clean little diagram of the same underlying tension: a system reports a change in state, and a human has to decide what the change means. The banner says motion. The circle says cat. The distance between those two statements is where all the actual work lives, whether you are debugging a stream or answering your door.
The shirt is available as a standard t-shirt from the Amazon listing, printed with the notification banner and the green-tinted doorbell view described above. If you want the object, that is where it lives. If you want the argument, it is on the front: the alert is the straight man, the cat is the payload, and the crop is the whole story.
Editorial note: This publication and Quirky Cotton Collective share an owner.
The native garment preview shows a dark shirt with large, bold, white lowercase lettering: meh. No animal illustration. No secondary graphic. No gradient or distressed texture visible in the supplied observation. Just four characters and a period, set at a scale that would be legible from across a control room.
That scale is the argument. meh. is a word that performs indifference. It is the verbal equivalent of a shrug, a half-closed eye, a Slack reaction that says I have seen this and I am choosing not to escalate. Printed small, it would be a private joke. Printed large — bold, white, centered on a dark field — it becomes a public statement about the limits of public statement. The shirt is not whispering meh. It is announcing it.
I keep thinking about this in the context of work culture for people who operate production systems. The engineers I know are not indifferent. They are selectively responsive. There is a difference between a person who does not care and a person who has learned that caring about everything at the same volume is a fast path to burnout, bad decisions, and a 3 AM page that did not need to happen. The large meh. reads, to me, as a boundary marker dressed as apathy. It is the visual equivalent of a runbook that says monitor, do not page.
That is an interpretation, not a claim about the shirt’s intent. The artwork does not come with a manifesto. But the visual facts support it: the word is lowercase, which softens it; the period is present, which closes it; the scale is large, which insists on it. A small meh. is a mood. A large meh. is a position.
There is a useful distinction here between a slogan and a usable promise. A slogan is designed to be repeated. A usable promise is designed to be relied on. Most workplace messaging fails because it tries to be both and ends up being neither. The meh. shirt does not promise anything. It does not say I will respond within SLA or I am passionate about synergy. It says: my baseline is lower than your urgency. That is not a great slogan. It is, however, an honest boundary, and honest boundaries are more useful than aspirational ones.
For technical readers, the appeal is obvious. We spend our days distinguishing signal from noise. We tune alert thresholds. We write filters. We argue about whether a 200ms p99 spike is worth a page. The large meh. is a human alert threshold rendered in typography. It is the shirt equivalent of setting severity: warning and walking away.
The design itself is unusually disciplined. No illustration means no competing focal point. The dark background makes the white lettering the only event. The period is doing real work: without it, meh is a sound. With it, meh. is a sentence. The period is the payload. It is the difference between a sigh and a verdict.
If you are looking for a meh shirt that commits to the bit without adding a cartoon or a secondary punchline, this is the one I would point to. The listing describes it as Meh Funny Sarcastic Saying Introvert Dry Humor, which is retail prose, not printed text. The printed text, per the supplied observation, is just meh. — lowercase, bold, white, on a dark shirt. That restraint is the point.
I would wear this to a meeting where someone has scheduled a quick sync to discuss a problem that has already been root-caused. I would wear it to a postmortem where the action item is improve communication. I would wear it on a Friday when the on-call phone has been quiet and I want to keep it that way. Not because I do not care, but because I have learned that the loudest person in the room is rarely the one with the most useful information. Sometimes the most useful thing you can say is the smallest. Sometimes you have to say it very large.
Editorial note: This publication and Quirky Cotton Collective share an owner.
The first thing I notice is the ring of text. LET’S ROOT FOR EACH OTHER AND WATCH EACH OTHER GROW wraps around four root vegetables — carrot, radish, beet, onion — each with a face and each with its roots drawn down into soil. The second thing I notice is that the sentence is doing two jobs at once, and only one of them is about gardening.
That double duty is the whole design. “Root for” means to support. “Root” also names the thing the vegetables are doing underground. The shirt puts the two meanings in the same frame and lets the ring of type hold them together. It is a pun, but it is a pun with a structure: the text is the canopy, the vegetables are the crop, and the roots are the part you don’t see until someone draws them.
The observation is literal: the phrase surrounds four smiling root vegetables, and their roots are visible in soil. That last detail matters more than it might seem. A carrot with a face is a cartoon. A carrot with a face and a taproot drawn into dirt is a diagram of a plant that has been personified. The design commits to the underground half of the metaphor. The roots are not hidden; they are the visual anchor.
I read the ring of text as a deliberate choice rather than a layout convenience. A straight line of type above four vegetables would read as a caption. A ring reads as a boundary — something enclosing the group, the way a team charter or a status page encloses a set of services. The vegetables are inside the sentence, not beneath it. That is a small thing, but it changes how the slogan lands: the promise is the container, and the plants are what the promise is about.
The phrase joins two clauses with “and”: root for each other, and watch each other grow. The first clause is about encouragement. The second is about observation. They are not the same activity, and the shirt is more interesting because it does not collapse them.
Rooting for someone is cheap to declare and hard to sustain. Watching someone grow is a different commitment: it requires attention, patience, and a willingness to let the growth happen on its own schedule. The design puts the two side by side and lets the reader decide whether they are a package deal or two separate promises. I think the strongest reading is that the second clause is the test of the first. Anyone can root for you in the abstract. Watching you grow means noticing when you do, and not treating the noticing as a favor.
There is also a quieter tension in the word “grow.” In a work context, growth is often a euphemism for scope creep, headcount, or output. The shirt’s vegetables grow downward as well as upward — the roots are the part that makes the visible growth possible. That is a useful corrective for anyone who has sat in a planning meeting where “growth” meant only the part that shows up in a chart.
Here is where I get skeptical, and the skepticism is part of the reading rather than a rejection of it. A slogan like this is a promise with no enforcement mechanism. “Let’s root for each other” is easy to print and hard to operationalize. The shirt does not tell you what happens when rooting for each other conflicts with a deadline, a performance review, or a reorg. It does not specify who watches whom, or what counts as growth, or how you register disagreement inside the ring.
That is not a flaw in the design; it is the limit of any slogan. The artwork is a diagram of an intention, not a policy. The four vegetables are smiling because the drawing is friendly, not because the underlying arrangement has been stress-tested. I like the shirt more, not less, for making that visible: the roots are drawn, but the soil is blank. There is no fertilizer, no weather, no competing weeds. The metaphor is clean in a way that actual mutual support rarely is.
Carrot, radish, beet, onion. Four different shapes, four different colors, four different root structures — and all of them edible, which is a detail the design does not lean on but the viewer supplies. The choice of root vegetables rather than, say, flowers or trees is what makes the pun work. A flower’s root system is less iconic; a tree’s is too large to fit in the ring. Root vegetables are the plants whose underground half is the point. You pull them up to eat them. The visible growth and the hidden growth are the same object.
I read the four faces as a small ensemble rather than a hierarchy. None of them is centered; none is larger. The ring of text gives them equal billing. That is a visual argument for the first clause of the slogan: the group is the unit, and the support runs around the circle rather than down from the top.
This is not a shirt that demonstrates anything about streaming infrastructure, and I am not going to pretend it does. It is a piece of printed cotton with a legible joke and a clear visual structure. The reason it belongs in a column like this one is that technical readers spend a lot of time reading diagrams, and this is a diagram of a social arrangement: a boundary, four nodes, a two-part promise, and an underground layer that the drawing insists you notice.
If you want the object itself, the listing is here: Let’s Root For Each Other And Watch Each Other Grow Garden. The design is the argument. The shirt is the medium.
Editorial note: This publication and Quirky Cotton Collective share an owner.