why wouldn't you ask?

Frontmatter

{
  "id": "7d3f2a18-6b94-4c2e-9f1a-2c5e8b0d4a61",
  "type": "blog-post",
  "stage": "drafting",
  "title": "why wouldn't you ask?",
  "author": "human:devarno",
  "created": "2026-06-20",
  "audience": [
    "build-in-public-followers",
    "aerospace-adjacent"
  ],
  "register": "reveal",
  "subtitle": "the day a 16-year-old asked me about oracle",
  "trace_id": "CE-CONTENT-DQ-001",
  "created_at": "2026-06-20T00:00:00Z",
  "published_at": null,
  "seo_keywords": [
    {
      "intent": "informational",
      "keyword": "level 2 swimming teacher qualification",
      "priority": "primary"
    },
    {
      "intent": "informational",
      "keyword": "career advice teenager tech",
      "priority": "secondary"
    }
  ],
  "canonical_url": "https://devaqua.blue/journal/why-wouldnt-you-ask/",
  "last_modified": "2026-06-20T00:00:00Z",
  "target_domain": "devaqua.blue",
  "thesis_anchor": "most people run the wrong question — 'can i?' invites every reason you can't; train onto 'why wouldn't i?' and the reasons against have to defend themselves.",
  "internal_links": [],
  "primary_systems": [
    "personal"
  ],
  "seo_schema_type": "BlogPosting",
  "target_url_slug": "why-wouldnt-you-ask",
  "meta_description": "a 16-year-old at my level 2 swim course asked if i'd used oracle. it became the best conversation i'd had in months — and a reminder to ask 'why wouldn't i?'",
  "minimum_dwell_met": true,
  "scheduled_publish": null,
  "secondary_systems": [],
  "transition_history": [
    {
      "actor": "human:devarno",
      "reason": "backfilled from devaqua-blue journal (CE-CONTENT-DQ-001)",
      "to_stage": "drafting",
      "from_stage": null,
      "transitioned_at": "2026-06-20T00:00:00Z"
    }
  ]
}

Body

she asked it the way you ask something you've been turning over for a while. a small breath first. then the words, slightly too fast.

"have you ever used oracle?"

## the question

i'm starting my level 2 swimming teacher qualification with the institute of swimming this week. for now my whole life fits in one element. i teach in the morning, and in the gaps i get back in and swim. laps to spend the spare hours, laps because the water is the one place the noise in my head drops to nothing. the water is doing a lot of work for me right now, and not just the laps.

so i'm at the side of the pool, towel round my neck, and one of my classmates comes over. she's sixteen. you can watch her decide whether to speak, right up to the second she does. and what she lands on isn't small talk. it's a real question, about a sixty-billion-dollar database company, asked at a swimming course on a wednesday morning.

it threw me. then it did something better than that.

## oracle is who hires you and never lets you go

here's what oracle is, if you've never had reason to know. it's the plumbing. databases and java, the quiet machinery running banks, airlines, hospitals, the back office of half the things you touched today without noticing. nobody's posting about it. it isn't the shiny thing. the fashion now is to throw out the thing that works and rebuild it over a weekend because the old way felt heavy.

i have several friends whose dads have spent their entire working lives inside it. thirty years, one stack, one steady hand on something enormous. and the longer i build, the more i understand what that actually means. these are the people who laid the floor the rest of us are standing on. the systems are boring in the way a load-bearing wall is boring. you only notice it the day it isn't there.

so when i say oracle is who hires you and never needs to let you go, i don't mean it as a joke about old tech. i mean it as the closest thing my industry has to a lifelong vow. you learn the thing properly, and it keeps a roof over your family for a career. there's a quiet dignity in that i didn't appreciate at twenty and can't stop appreciating now.

which is also why a sixteen-year-old asking about it, out of nowhere, at a pool, is such a strange and lovely thing. no teenager reads a page about enterprise databases and just becomes curious. that's not how it works at sixteen. there's always a person in the middle. someone whose life makes the abstract thing real.

so i asked her the only question that mattered: "who do you know?"

we both laughed, because of course there was someone. there always is. you don't fall for a field. you fall for a person who's at home in one, and the field walks in behind them.

## what she was actually doing

i think she'd found my page first. the other half of my life, the systems and the engineering, lives online, and i suspect she'd read it before she ever stood next to me. so when she finally asked, she didn't reach for "oh, so you code?" or "so you're into planes and space then?" those are the two i usually get. both of them fold a whole working life into a hobby.

she asked something specific instead, which is harder. specific carries a risk: you might not follow the answer, and you might have to sit there not following it in front of someone.

she asked anyway. that's the part that stayed with me. not the database. the nerve.

## i've been her

i know that exact nerve, because i've stood where she was standing.

my first internship was at a satellite company. i applied because i wanted to work on rockets. anything with propulsion, anything pointed up. the offer came back for something else entirely: software engineering experience. at the time the word "software" alone was enough to make me hesitate. i genuinely sat there wondering whether it was a mistake.

the whole career i have now, the one that sixteen-year-old went looking at before she found the pool, exists because i walked through a door with a word on it that scared me.

the first client after that was a carpenter who wanted a website. i had no idea what i was doing. i didn't know what an invoice was. i charged him and felt like i'd robbed the man. that job is now just an early entry on a long list, and every name on it taught me something i still use today.

every one of them started the same way her question did. somebody decided to be uncomfortable on purpose.

## the water was a "why not" too

i should tell you how i got in the pool in the first place, because it's the same move.

the first time was before university. michael phelps had just done something absurd at the olympics and i wanted to know what the fuss was about, so i got in to see for myself. no plan. just: why not.

the second time was the start of uni, and it was an escape. i'd walked into a wall of aggressively macho student culture, and somewhere around american football i drew a line. i wanted teamwork that didn't require me to flatten myself to fit it. somewhere i could work on my body, work on my head, and eat a meal without guilt. the pool was right there. why not.

that's nearly ten years ago now. i never got back out. the committee roles came after, then the qualifications, then the frameworks i'm building on this week. all of it traces back to a teenager who couldn't be bothered to invent a good reason not to get wet.

## the bit i keep thinking about

the conversation wandered somewhere i didn't plan, and afterwards one thought wouldn't leave.

it takes a particular bravery to ask an honest question about a thing you don't understand yet. you're saying, out loud: i don't know this, i'd like to, and i'll risk looking like i don't know it to find out. kids do this without thinking. we spend our twenties training it out of ourselves.

the version i wish more adults still had is the one pointed inward. asking the honest questions about yourself. i wish more people talked plainly about therapy, about the deeply unglamorous work of finding out what's actually going on in your own head. because if you could see the wiring, and maybe even adjust it, why wouldn't you?

that word still makes people flinch, and i've never understood the flinch. the hardest paths in a life come with the same label stuck to them: find a way to carry this, because it's coming. the least glamorous way is the one that works. say it out loud. to a professional, a friend, anyone. the strategies were never a secret. we just don't pass them to each other often enough.

there's a longer piece i want to write here soon, in the open, about how my own head actually runs. about adhd, the diagnosed kind, with the assessments and the paperwork and all of it. i don't have the shape of it yet. but a brave question from a sixteen-year-old at a pool feels like roughly where it started.

## the part i'd rather not write

in case any of the above reads like a man who's worked it all out: i haven't. nobody has.

i've spent most of my life packed for a trip i never booked. bags by the door, standing at a gate, watching a board i can't quite read for a flight i'd recognise the instant i boarded it. there are things about how i eat i keep meaning to fix. table manners my grandparents drilled into me that still don't survive the first plate. a standing promise to sort my sleep that renews itself, unkept, every year, and a nail-biting habit i'd sell to a stranger for a pound. i'm nowhere near whatever "sorted" is meant to mean, which is fine, because nobody is. it's as ordinary as the ground.

the honest one, underneath the rest, is fear.

i'm thirty and i get scared. daily. about things i don't have words for, in a head that often feels like a jar with the lid screwed on. some of that fear is useful. it's the thing that pushed me through every scary door. but i'd be lying if i said it was all the useful kind.

i'm scared of what the get-rich-overnight machine is doing to people younger than me, and the flat grey feeling i think waits for them on the other side of it. i'm scared that "go and play outside" is becoming a sentence kids need translated. that dinner is losing to a screen. i worry, with no proportion at all, about the year the world quietly stops printing enough books. i worry about the slow adult job of choosing who i want walking into the rest of my life with me. and harder than that, about the people already worth mending things with, where i hold off reaching out because i'm afraid my own wiring will scramble the message and make the wound worse instead of closing it: the thing you most want to fix is the thing you're most scared of fumbling.

and the big one. that the decent things we've managed to build could come apart fast, because a small number of people would rather measure whose button is bigger than admit that ending real, named, human hunger turns out to be embarrassingly payable.

i list it not to frighten you but because naming a fear is the first move through it. the thing i'm trying to build a life around is easy to say and hard to do: walk at the thing that scares you, and watch for the comfort zones closing quietly around you before they set.

and when fear stops being useful, when it gathers and stalls you and pulls you inward, away from people, the move is the least heroic one available.

say it to someone. anyone. your best mate or your barber. your mum or the postman. the person in the next lane. it does not matter who. it matters that the thought leaves your skull and meets the air, because a fear said out loud is half the size of one kept in.

## why not

if you're young, and there's an adult whose work you're quietly curious about: ask the specific question. the nervous one. most of us aren't just willing to answer. we're quietly thrilled to be asked something real.

and if you're the adult: be askable. be the person a kid finds when they go looking. that's where the chain starts. that's how a field gets its next person.

there's a line in *we bought a zoo* i've quietly run a whole life on. a father tells his son that sometimes all you need is twenty seconds of insane courage, and something great comes of it. her question was her twenty seconds.

here's what i've worked out, slowly, at every door i was scared of. most people run the wrong question. they ask "can i do this?", and "can i" is just an invitation to list the reasons you can't. i trained myself onto the other one. not "why would i", but "why wouldn't i". it flips who has to make the case. suddenly the reasons against have to defend themselves, and most of them can't.

i got handed that lesson again at general electric, in cheltenham, as a very excited intern. the work didn't look like much from the outside: old avionics, the kind of tech a cockpit keeps precisely because it already works and nobody sane gambles a flight on novelty. my interviewer actually closed with it. the tech here is quite old, he said, cockpits build what works and stick with it, are you sure you want to be here? why not, right.

then i got in, and it was the most freedom i'd ever been given. full matlab and gui run of an experimental rig. requirement-to-test visibility end to end. at one point i was defining and mapping my own failure modes for a micro interface unit that never left the conceptual stage, and for a brain with no conductor and no diagnosis yet, that kind of structured freedom felt like being handed the keys. i wouldn't be the engineer i am without that building and the people in it. the whole circuit of cheltenham, human and digital, is wired into how i think. my plug had no spark before ge. anyone from there who reads this knows exactly where they sit in that diagram, and i owe them more than a paragraph can hold.

therapy is the cleanest case i've got. as "why would i sit and talk about my feelings?" it sounds like a chore you can always put off. flip it. "if i could actually understand how my own head runs, and maybe make it run a little better, why wouldn't i?" put like that, putting it off is the strange choice. same with her question. same with the door marked software. same with the carpenter's website i had no business taking. same with the pool. why not.

so. have you ever used oracle?

yeah. i know people who gave it their whole lives. and now, so does she. because she ran the right question, out loud, to a stranger at a pool.

why wouldn't she.

---

**what's next:** the harder piece. the open, honest account of diagnosed adhd: the assessment, the paperwork, what it costs and what it quietly hands back, and why the water is the one room where my head goes quiet. there's a lot of noise online about this condition from people performing it for a feed. i'd rather just tell you the real version. this was the warm-up lap.

*devaqua is the other half of my work. water competence as a mission, written by a systems engineer currently earning his level 2. [more here](https://devaqua.blue?utm_source=blog&utm_medium=journal&utm_campaign=oracle&utm_content=why-wouldnt-you-ask)*