Baseball

Podcast 2 — In conversation

Speaker A: I keep encountering baseball idioms in American business writing — step up to the plate, out of left field, touch base — and sometimes I am not entirely sure which ones are still genuinely used and which ones are clichés to avoid.

Speaker B: They are all still in active use, but you are right that some are fresher than others. Touch base is so ubiquitous in business English that most British speakers use it without thinking of baseball at all — it just means to make brief contact or check in with someone. Out of left field still feels vivid; it means something unexpected and surprising, coming from an unusual direction. Step up to the plate is solid — it means to take responsibility or rise to a challenge. The one I would use cautiously is three strikes and you're out, which can sound a bit heavy-handed in a business context.

Speaker A: What about ballpark figure? That is one I hear a lot in British business contexts too.

Speaker B: Ballpark figure is completely naturalised in British business English — it means an approximate estimate, a rough number. You would say give me a ballpark figure for the cost of the project, meaning do not worry about precision, just give me a rough sense of the scale. The ballpark is the stadium where baseball is played, so the idea is that you are in the right general area even if you are not at the exact seat. That image has entirely faded from British usage — it is just a phrase for an approximate number now.

Speaker A: And baseball cap — that is obviously from baseball, but nobody thinks of it as a sporting term any more.

Speaker B: Right, the baseball cap has completely escaped its origin. It is a global fashion item. The forward-facing brim design was practical for baseball players — keeping sun out of their eyes during daytime games — but the cap has been adopted into every subculture from hip-hop to hiking to corporate casual. When someone says baseball cap, they mean the style of hat, not any connection to the sport. It is a compound noun that has gone through the same process as many others — the sport name is now just a modifier describing the shape.

Speaker A: So baseball as a vocabulary item is interesting because it gives you both a technical sporting vocabulary and a huge set of idioms that have migrated into general English.

Speaker B: Exactly. And the idioms are the ones worth mastering if you are communicating with American audiences, because they are genuinely embedded in professional and everyday speech. Step up to the plate, out of left field, touch base, ballpark figure — know those four well and you are covered for most situations.

Podcast 3 — Prompt engineering

Speaker B: Baseball is a data-rich sport with a century and a half of statistics, complex scoring rules, roster management, and a passionate fan base — which makes it an outstanding domain for software prompting. Whether you are building a statistics tracker, a live scoreboard, a fantasy league system, or a sabermetrics analytics platform, the word baseball in your prompt signals the full domain to the AI. Let me walk through five prompts.

Speaker A: The statistical dimension is what makes baseball particularly interesting for data applications — batting averages, earned run averages, on-base-plus-slugging percentages. There is a lot of structured data to model.

Speaker B: More structured baseball data has been compiled than almost any other sport. First prompt — core statistics database.

Speaker B: Design a PostgreSQL schema for a baseball statistics database. Players table: player_id UUID, first_name, last_name, position as enum pitcher catcher first_base second_base third_base shortstop left_field centre_field right_field designated_hitter, team_id foreign key, debut_date, active boolean. Batting_stats table: stat_id, player_id, season year, games integer, at_bats integer, hits integer, doubles integer, triples integer, home_runs integer, runs_batted_in integer, walks integer, strikeouts integer, stolen_bases integer. Computed columns via views: batting_average as hits divided by at_bats, on_base_percentage, slugging_percentage, ops. Pitching_stats table: player_id, season, games_pitched, innings_pitched decimal, earned_runs, strikeouts, walks, wins, losses. Computed view for ERA as earned_runs divided by innings_pitched times nine. Index on player_id, season, and team_id.

Speaker B: The computed column views for batting average, OBP, and OPS are the correct architectural choice — these statistics are always derived from the raw counting stats and should never be stored as separate values that can become inconsistent. The position enum with all nine fielding positions plus designated hitter is complete and domain-accurate. The ERA formula — earned runs divided by innings pitched multiplied by nine — gives you a per-nine-innings normalised value, which is the standard form for comparing pitchers across different workloads. A database with this schema can answer virtually any statistical query a baseball analyst would ask.

Speaker A: The ERA formula embedded in the view definition is exactly the kind of domain knowledge that makes the prompt output immediately usable rather than needing correction.

Speaker B: Domain accuracy in the prompt generates domain accuracy in the output. Second prompt — live scoreboard.

Speaker B: Build a live baseball game scoreboard single-page application. Display: home team and away team names and logos via URL, current inning and half-inning top or bottom, score per team per inning in a grid layout matching the traditional baseball scorecard format, current batter, pitcher, count of balls and strikes and outs, last play description, bases occupied shown as a diamond graphic with lit bases. Controls for a scorekeeper to advance the game: add run, add out, advance inning, record strike, ball, hit, walk, home run. Auto-calculate totals. Vanilla JavaScript, dark stadium-night theme.

Speaker B: The bases occupied diamond graphic is the visual element that makes a baseball scoreboard unmistakably baseball rather than generic sports. The diamond with lit bases showing which are occupied is immediately readable to any baseball fan and impossible to confuse with another sport. The traditional scorecard grid — nine columns for nine innings, one row per team — is the format that baseball audiences expect; deviating from it confuses users who know the sport. The count display of balls, strikes, and outs represents the within-at-bat state that changes every pitch.

Speaker A: The within-at-bat state is the thing that gives baseball its moment-to-moment tension — three balls and two strikes with two outs is a completely different situation from one ball and no strikes.

Speaker B: Context within at-bat is what makes the game statistically rich. Third prompt — fantasy league management.

Speaker B: Build a fantasy baseball league management application. Leagues table with commissioner and settings including scoring categories — batting average, home runs, RBI, stolen bases, ERA, WHIP, wins, saves. Teams table with owner, team name, salary cap. Roster table: team_id, player_id, acquisition_type as enum draft free_agent trade, salary decimal, active boolean. Draft room: snake-draft order, pick timer, available players sorted by projected value. Waiver wire: claim requests processed by waiver order. Trade module: propose a trade listing players exchanged, commissioner approval required if enabled. Standings: live standings by total score across all categories. Vanilla JavaScript, dark theme dashboard.

Speaker B: The scoring categories in the settings — batting average, home runs, RBI, stolen bases, ERA, WHIP, wins, saves — are the standard rotisserie baseball categories that have defined fantasy baseball since the 1980s. Naming them explicitly in the prompt ensures the AI builds a scoring system calibrated to actual fantasy baseball conventions rather than inventing generic scoring. The WHIP metric — walks plus hits per inning pitched — is a pitching quality indicator that fantasy baseball popularised before it became widely used in professional analysis. The waiver wire with priority ordering is the roster management mechanism that distinguishes casual from competitive fantasy leagues.

Speaker A: WHIP is an interesting metric because fantasy baseball was using it seriously before many professional teams were.

Speaker B: Fantasy players were among the early sabermetricians. Fourth prompt — sabermetrics analytics dashboard.

Speaker B: Build a sabermetrics analytics dashboard for comparing baseball players. Input: paste or upload season batting stats as CSV with player name, team, at_bats, hits, doubles, triples, home_runs, walks, hit_by_pitch, sacrifice_flies, total_bases. Automatically calculate: batting average, on-base percentage, slugging percentage, OPS, OPS-plus normalised to league average of 100, isolated power, walk rate, strikeout rate. Display a sortable comparison table with all metrics. Scatter plot of OBP versus slugging for all players. Highlight the top five players by OPS in a summary panel. Vanilla JavaScript, Chart.js loaded from local CDN-free script, dark theme.

Speaker B: The OPS-plus calculation — normalised to a league average of 100 — is the metric that makes cross-era and cross-ballpark player comparisons meaningful. A raw OPS of point eight hundred means different things in a hitter-friendly park in the steroid era versus a pitcher-friendly park in the 1960s; OPS-plus adjusts for both. Including that in the prompt signals to the AI that this is a sophisticated analytics tool, not a basic stats table. The scatter plot of OBP versus slugging is the visual that sabermetricians use to see which players have unusual combinations of plate discipline and power hitting.

Speaker A: The OBP versus slugging scatter plot is the chart that reveals the players who are undervalued by traditional scouts who focus on batting average alone.

Speaker B: That was exactly the insight Moneyball made famous. Final prompt.

Speaker B: Build a complete baseball team management system as a single-page application. Modules: Roster Manager — full player profiles with position, contract details, injury status, and 40-man roster designation; Game Log — record game results with box score entry including per-inning runs, hits, errors, and pitcher stats; Statistics Tracker — season cumulative stats auto-calculated from game logs with sortable leaderboards for batting and pitching; Scouting Reports — add written notes and ratings for players, linked to player profiles; Schedule — 162-game schedule view with results for completed games and upcoming opponents; Front Office — contract salary table with payroll total and luxury tax threshold warning. Left-side navigation, dark theme, vanilla JavaScript, no frameworks.

Speaker B: The luxury tax threshold warning in the Front Office module is the detail that makes this feel like a real Major League Baseball management tool rather than a generic sports roster app. MLB teams pay a competitive balance tax when their payroll exceeds a threshold set by the collective bargaining agreement, and tracking that limit is a genuine operational concern for front office staff. The 162-game schedule is the correct season length for MLB — not 80, not 100, but 162, and specifying it makes the schedule module correctly sized. The 40-man roster designation in the Roster Manager reflects the real distinction between the active 26-man roster and the protected 40-man roster that determines which players can be called up from the minor leagues.

Speaker A: Knowing those specific numbers — 162 games, 26-man active roster, 40-man protected roster — is what separates a prompt that produces a recognisable baseball system from one that produces a generic team management template.

Speaker B: Vocabulary is domain knowledge. Baseball gives you a deep vocabulary, and that vocabulary generates software that people who know baseball will actually trust and use.