What are your thoughts of Triple A games and the current trajectory of mainstream gaming as a whole?
Do you think videogames today are more optimal now? Or not as good as they made it back in the day?
okay. OKAY. someone finally asked. buckle up because we're gonna be here for a while
from a playerâs perspective first: modern AAA games are, with a few exceptions, a disappointment that i have made my peace with in the same way you make peace with a chronic condition. theyâre not unplayable. theyâre just⌠safe. aggressively safe. like someone spent 300 million dollars to ensure nothing surprising ever happens.
the budgets went up. the risks went down. somewhere in between we lost the plot.
i grew up on games that felt like the developers were arguing with their hardware. you could feel it. systems pushed past what the machine should technically be able to do. mechanics that existed because someone refused to accept that a limitation was final. when I boot up a lot of modern AAA titles now it feels like every design decision went through three layers of market testing and a legal department. technically impressive. spiritually hollow. like eating very expensive cardboard
now. from a programmerâs perspectiveâŚ
oh itâs worse. so much worse.
hereâs the thing about Doom. 1993. id Software. the hardware situation they were working with was ridiculous by modern standards. a 486 processor if you were lucky. four megabytes of RAM. no GPU in any meaningful sense. the idea of programmable shaders didnât exist yet. the machine was basically a calculator with ambitions
and what Carmack built on top of that is still one of the most elegant pieces of software engineering iâve ever read.
I mean that literally. iâve read the source code. multiple times. not in a nostalgic way. in a âthis is still pedagogically usefulâ way. if someone asks me how to become a better systems programmer I tell them to read the Doom engine before they read almost anything modern lol
the architecture is clean. the platform abstraction is clean. game logic and system-specific code are separated in a way that makes porting almost trivial. the renderer uses binary space partitioning so the engine can determine whatâs potentially visible before it draws anything. which means the CPU spends its time drawing things the player can actually see instead of blindly throwing geometry at the screen.
today that sounds obvious. at the time it was borderline wizardry.
remember. this machine had NO GPU doing the work. the CPU is calculating everything. projection math. visibility. texture mapping. all of it. fixed-point arithmetic because floating point was too slow. clever lookup tables everywhere. entire systems designed around the idea that cache misses are the enemy and memory bandwidth is precious
the whole engine feels like a watch mechanism. every component exists because it absolutely has to.
and then four years later id releases the source code
and suddenly an entire generation of programmers can study it. modify it. port it to anything with electricity. calculators. refrigerators. oscilloscopes. people are still learning from that code thirty years later
so now compare that to the modern AAA ecosystem.
we have GPUs capable of executing tens of thousands of shader threads simultaneously. we have memory bandwidth that would have seemed supernatural in 1993. we have development budgets larger than some national film industries.
and games still launch with shader stutter. asset streaming failures. frame pacing issues. giant patches on day one because the optimization pass didnât happen
the problem is not that the hardware is weak btw! the problem is that NOBODY is talking to the hardware anymore.
modern engines are incredibly sophisticated, yes. but theyâre also enormous abstractions stacked on top of abstractions. the rendering pipeline is so layered that sometimes nobody on the team actually understands what the GPU is doing moment to moment. artists generate huge texture sets. those textures get sampled dozens of times per pixel. the memory access patterns are chaotic. suddenly the GPU spends more time waiting for data than actually shading pixels.
thatâs the real bottleneck in modern rendering by the way. not arithmetic. GPUs are absurdly good at arithmetic. the bottleneck is data locality. if the shader has to fetch texture samples scattered all over memory your throughput collapses
so now we build elaborate systems to mitigate that. texture streaming. level-of-detail hierarchies. occlusion culling. hierarchical Z buffers. entire pipelines just to make sure the GPU doesnât drown in data it doesnât need.
which is interesting engineering! i donât want to imply it isnât. modern engines solve problems that simply didnât exist in 1993.
but the difference is philosophical.
the Doom engine was written by a handful of people who understood every line of code in the system. modern AAA engines are written by hundreds of engineers across a decade of development. the architecture inevitably becomes⌠layered. messy. sometimes brilliant. sometimes held together with duct tape and deadlines
i built games myself before my wife's company stole my career trajectory. nothing AAA, smaller projects. the kind where you write the renderer yourself because there is no engine yet. you learn very quickly that architectural decisions are permanent. if you design a bad asset pipeline early in development you will suffer for the rest of the project. forever.
modern AAA studios make those kinds of architectural mistakes constantly and then compensate with budget. throw more hardware at it. throw more engineers at it. patch it later.
commercially it works. these games sell tens of millions of copies
but nobody will be reading that code thirty years from now to understand how it was done.
Doom is a love letter to constraint-driven design. it exists because the hardware forced the developers to be clever
modern AAA development is what happens when the constraints disappear and the budgets become infinite.
also. small tangent because i know someone will ask: yes i still write little engine experiments occasionally. nothing public. nothing iâm claiming credit for. sometimes you just want to remind yourself how a renderer works from the metal up instead of through five abstraction layers and a build system that takes forty minutes
anyway. thank you for enabling this rant.
iâm going to go replay Doom now on the smart fridge
helped my daughter build this little animatronic head tonight and I am extremely proud of her.
the âheadâ is currently two eyes, some wires, and a wheel assembly but thatâs basically how all robotics projects start anyway. the important thing is it moves and she thinks thatâs the funniest thing that has ever happened
next step is obviously building an exoskeleton for Bertha (her giant bear plush. roughly the same height as she is, somehow wider) so Gerald has a friend!
at this rate sheâs going to be designing control systems by the time sheâs ten. which is great because then I can outsource half my side projects to her. she spends most of her time in my lab anyway instead of in her motherâs office lol. apparently the wires and robot parts are more fun than stacks of paperwork.
she does prefer her mother though, which is completely fair! i'm also as attached to my wife
If you ever had the support and funding, would you like to build a time machine?
absolutely. if someone handed me unlimited funding and said âbuild a time machineâ I would become extremely annoying about it almost immediately.
first thing to clarify is that the physics side and the engineering side of time travel are completely different conversations. the physics people already let you do a couple weird things. traveling forward in time at different rates is just relativistic time dilation. go fast enough or sit in the right gravitational well long enough and you come back to discover everyone else experienced more time than you did
which is technically time travel but itâs the boring kind where you canât fix mistakes and nobody gets dramatic do-overs.
going backwards is where things start turning into a systems problem. because now you have to decide what kind of universe you live in.
thereâs the branching timeline model where touching anything creates a new trajectory of history. very chaotic. terrible for record keeping
thereâs the self-consistent model where if you go back in time it means you were always there to begin with. personally I like that one because it behaves more like a properly constrained system. no paradoxes, just a very complicated loop
and then thereâs the âredo the same moment with knowledge of previous attemptsâ version which is essentially the universe implementing save states
which I admire conceptually. but suspect reality would consider extremely bad design.
anyway if I somehow solved the engineering constraints (which are... considerable. energy requirements alone would make every funding committee on earth break into a cold sweat) I would immediately misuse the machine for extremely petty reasons.
first stop would probably be the mid-90s to ensure Looking Glass Studios stays solvent so they don't have to rush Thief II out the door and cancel the original Thief III. Losing the Siege Engine and the concentration of talent in that building basically set the immersive sim genre back a decade. you can actually trace the ripple effects of that collapse through half the design problems the genre struggled with in the 2000s.
alternatively I'd intervene to stop Activision from forcing a simultaneous launch with Half-Life 2. if Bloodlines hadn't been sent out to die like that, Troika might have stayed solvent long enough to give the game the extra year of polish it obviously needed instead of leaving its survival to a twenty-year fan patch effort lol
the other category of abuse would be concerts I missed because I was âbeing responsibleâ
there was a Bikini Kill show in olympia I skipped once because I had a systems architecture final the next morning. I have always wondered if that was the correct life decision.
time machine would allow me to test that hypothesis
same with Sleater-Kinneyâs early shows when they were still playing tiny venues. I saw them later obviously but thereâs something fascinating about catching bands before the mythology forms around them.
thereâs also a purely academic category of trips where I would go observe certain programming decisions in real time...
like I want to be physically present in the room where IBM engineers were designing parts of OS/2 and early enterprise networking stacks just to see what the conversation sounded like. IBM in the 80s and 90s had this incredible culture of systems thinking that you donât really see anymore. people forget how much of modern infrastructure grew out of those environments
I miss that kind of engineering ecosystem honestly. extremely opinionated. very weird. lots of deeply specialized people building things that were meant to last twenty years
I would also attend the meeting where someone finalized parts of COBOLâs legacy banking infrastructure decisions because the fact that half the worldâs financial systems still run on it is both terrifying and kind of beautiful
like imagine writing code in the 1960s and knowing it might still be processing payroll sixty years later.
now thatâs architectural confidence
on the personal side there are some moments Iâd revisit!
for example the first time I kissed my wife.
not to dramatically alter history or anything, just⌠slightly refine my own performance in that situation. in my defense I had been debugging something for twelve hours and my brain was still thinking about memory allocation and process scheduling. there is definitely a version of that moment where I am at least 10% smoother and I would like to observe it for research purposes
unfortunately if the universe runs on a self-consistent timeline model that means the awkward version must remain the canonical one
which is humbling.
the real danger of time travel though isnât paradoxes. itâs engineers immediately inventing irresponsible side projects. because once the machine exists the temptation to run experiments becomes overwhelming
like âwhat happens if I bring a modern neural network paper back to 1993â
or âwhat happens if I leave a flash drive with a bunch of open-source libraries somewhere in 1985â
or more dangerously âwhat happens if I show a 1970s IBM engineer a modern GPUâ
these are the kinds of questions that very quickly get your time machine privileges revoked.
so yes I would build one
but someone would probably have to confiscate it after a week because I would absolutely start using it to answer questions like whether a specific Halo CE speedrun route was theoretically possible two years earlier than people thought
and at that point the timeline is already in danger
this is a good question because my first instinct was to make a spreadsheet!
like genuinely. columns for genre, year discovered, whether I saw them live, which album I associate with specific life events, etc. it would have been extremely organized and probably deeply unhelpful to anyone reading it
but unfortunately I am at work right now and opening a spreadsheet titled âpersonal music taxonomyâ would raise questions so youâre getting the Unstructured Version
genre-wise I tend to orbit around rock in general. grunge, alt rock, indie stuff, a little metal depending on the day. also dream pop / shoegaze when my brain is fried and I need something that feels like floating through fog. growing up around seattle kind of does that to your music taste whether you mean for it to or not. local gigs are basically a rite of passage. half the time you go because someoneâs friendâs band is playing and the other half because itâs cheaper than doing anything else
thereâs a non-zero chance I saw the gits live once when I was younger. I say ânon-zeroâ because i used to go to a lot of shows while aggressively procrastinating on assignments and the memories blur together after a while. but i distinctly remember seeing them play a tiny venue while I was supposed to be finishing a final project and thinking âthis is a much better use of my timeâ
mia zapata had one of those voices that cuts straight through everything. just pure presence. the whole band had this raw energy that felt very⌠honest? like nobody was trying to polish it into something marketable
anyway that whole scene was pretty foundational.
riot grrrl in general is a big one for me. excuse 17, heavens to betsy, that whole olympia ecosystem
actually excuse 17 always makes me go on a tangent because carrie brownstein was in that band before sleater-kinney and then sleater-kinney became one of the defining bands of that whole movement. which is funny because the two founders of sleater-kinney dated at the time and somehow managed to keep making incredible music together even after breaking up. which is impressive frankly. if fleetwood mac had handled their interpersonal drama with even half that level of emotional maturity they probably would have avoided several decades of chaos
and then thereâs emilyâs sassy lime which i initially clicked on purely because the name is a palindrome. i saw it written out somewhere and my brain went âwait that reads the same backwardsâ which is apparently all it takes for me to investigate something. turns out theyâre fantastic and now they live permanently in my cassette tapes. sometimes the most arbitrary entry points lead to the best discoveries.
katiejane garside is another one i really admire. sheâs been involved in a million different projects and every single one experiments with sound in a slightly different direction. that kind of creative restlessness is very appealing to me. i like artists who treat genres like suggestions rather than rules
cibo matto is probably my favorite thing to put on when iâm winding down though. technically more trip hop / art rock territory but the vibe is neat. itâs the sort of music you put on when you want to sit somewhere with low lighting and let your brain decompress after thinking too hard all day
I also discovered a band called suffrajett recently which has like⌠criminally low listener numbers for how solid their rock sound is. always fun finding groups that feel like hidden pockets of the internet
so yeah thatâs the extremely non-spreadsheet answer.
short version: a lot of riot grrrl, a lot of seattle rock, some experimental stuff, and whatever weird musical rabbit holes my brain decides to wander into at 2am while iâm supposed to be doing literally anything else
Anon again, must say I'm very intrigued! This sounds like the type of innovation that could change the course of medical history. I'm quite the fan.
When do you think this will go into trial? And how will you test if it works?
ohhh weâre getting into dangerous territory nowâŚ
curious anon. very curious. I feel like I should give you a little nickname at this point. hm. âclinical trials anonâ feels too on the nose. maybe âpersistent anon.â weâll workshop it!
also I have to say the idea of having a fan is extremely funny to me. Iâve never had one before. do I sign something? do I send you a sticker. whatâs the protocol here
(kidding. mostly)
anyway I donât know how much I can actually reveal without someone from legal appearing behind me like a sleep paralysis demon so let me answer in the most responsible vague engineer way possible
yes, trials are being discussed.
and by âbeing discussedâ I mean I am currently being gently but persistently pushed in that direction because people like milestones and timelines and things that look good in reports.
personally I would not recommend it in the state the system is in right now.
not because itâs failing exactly. the problem is actually More annoying than that. all of our current testing gets us close, but not all the way there.
we can calibrate the interface, map signal behavior, run controlled simulations, test the routing architecture in isolation, check latency tolerances, watch how the system responds to synthetic neural patterns. all of that works. itâs useful data. it tells us how the system behaves under ideal conditions
but the only test that actually matters is the one where someone actually gets in and the system has to negotiate with a real brain in real time.
and right now that negotiation is⌠not unstable exactly
but not something I would sign off on without a lot of caveats and a veryy long disclaimer
the threshold problem I mentioned earlier is basically this question of how much sustained engagement the brain tolerates before things start behaving in ways that are difficult to predict. we can estimate it and run all the calibration routines we want, but until there is a real person in the loop the system is still operating in a very polite theoretical space
and brains, unfortunately, are not polite systemsâŚ
so. short answer: trials are being talked about. I am arguing about it
which is funny because normally I stay out of that side of things entirely. business timelines are not my department. I build the weird machines and then other people decide when they become someone elseâs problem
but this one is⌠different.
also I should probably ask the obvious question here: youâre not secretly a rival company trying to fish for details, right? lol because if so I regret to inform you that youâre going to have to try harder than anonymous tumblr curiosity
although if youâre just genuinely interested then I will say the encouragement is appreciated. the cyberwalker is one of those projects that starts living in your brain after a while and itâs nice knowing someone out there finds it as interesting as I do. most are just interested in the potential profits
So, the cyberwalker project. What can you tell us about that?
oh someone's asking about the good stuff okayyy
so the cyberwalker is a neural interface project I've been working on for a while now. I can't get into specifics for reasons that are partially contractual and partially because if I explained what it actually does in plain language it would either sound incredibly boring or incredibly alarming and neither of those is the impression I want to make on a monday
what I CAN tell you is that it involves sustained neural engagement with an alternate environment, that the biological threshold problem we've been working around for the past eight months is genuinely one of the more interesting problems I've encountered in my career, and that we hit a significant benchmark recently that I am not allowed to be more specific about but that I am still thinking about constantly...
the name is a whole thing actually. I wanted to call it something that captured the experience of moving through a system that wasn't quite real, like walking through something rather than in it. cyber comes from the greek word kybernÄtÄs, meaning steersman, the person who navigates. so a cyberwalker is essentially someone who steers themselves through an artificial environment. which I thought was elegant! my wife thought I should have named it something that would look better in a Pentagon briefing document. we compromised in the sense that I kept the name and she stopped bringing it up lol
anyway the threshold problem reminds me of something completely unrelated which is the question of how you measure a limit that's never actually been tested. like. if nobody has ever tried to go past a certain point, is the point a real boundary or just the edge of what anyone has bothered to attempt. speedrunning communities deal with this constantly. there's this run in mike tyson's punch outâ
actually that's a whole separate post. the point is the cyberwalker is going well and I am very normal about it. thank you for asking ;)
Since your post about Gerald, has Charles Entertainment Cheese come knocking on your door to reclaim him?
nope!
first thing I did when I got him home (after fixing his arm) was check for a tracker because corporations love putting gps modules in things now and I did not feel like explaining to a confused chuck e. cheese technician why one of their bears was suddenly broadcasting from my garage
but there isnât one. which tells me two things
1) they either donât track the animatronics at all
2) or they decided the bear was someone elseâs problem the moment he left the building
both of which are very funny outcomes
anyway the inside of these things is actually fascinating. like if youâve never opened one up itâs basically this weird little mechanical ecosystem. youâve got the metal frame that acts like a skeleton, then a bunch of pneumatic cylinders and linkages that control the arms and head, and then all the servo lines running back to the controller board
Gerald in particular has this absolutely ancient wiring harness that looks like it predates several presidents. lots of zip ties. questionable solder joints. the sort of engineering where you can tell someone fixed the same problem three different ways over ten years
thereâs also foam padding everywhere because the outer âskinâ needs something to sit on top of so the face doesnât look like a haunted sock puppet when it moves
and the eyes! the eyes are these little mechanical cups with rods attached so they can pan and tilt. when you move them by hand they make this very specific clicking sound that is either charming or deeply cursed depending on your tolerance for animatronics
right now heâs half disassembled on my workbench because Iâm trying to map the control signals. my daughter keeps walking in and asking why the bear is âsleeping without his faceâ which feels like a fair question honestly
anyway if chuck e. cheese wants him back they are welcome to come get him but considering there is no gps and the internal electronics are held together with optimism I suspect Gerald was spiritually retired long before he arrived here. plus he's family now and I think my daughter would be sad to see him go. she has a bear plush she got from the arcade (that's literally as tall as her. FATTER too) that's basically Gerald's cousin (she named her Bertha). I'm thinking about rigging her up with a little exoskeleton so she can wave back at Gerald
Do you have a favorite Linux distro?(Please don't say 'Linux from Scratch')
âplease donât say linux from scratchâ this feels very targeted and hostile considering how many evenings of my life went into that project :/
anyway. FIINEEEE iâll behave...
i used gentoo a lot for a while. partially because i like knowing exactly what my machine is doing and partially because watching emerge compile something for four hours has the same weird meditative quality as grinding runes in elden ring. like you start the process, walk away, make lunch, listen to three albums, come back and itâs still thinking about it. very honest relationship with your computer. it Does Not pretend things are happening faster than they are
also thereâs something philosophically pleasing about compile flags. like yes actually i would like to decide whether my media player supports seventeen codecs i will never use. autonomy matters!
nixos though⌠nixos is the one that made my brain light up a little
because once you realize itâs declarative the whole thing starts feeling less like configuring a computer and more like describing a system to a very patient librarian. you just write down âthis machine has vlc, obs, neovim, clang, aria2, these fonts, this window manager, here are the weird little configuration tweaks i insist onâ and nix goes okay. understood. i will make the world match that description
and then if you copy that config to another machine it just becomes the same system again. like cloning a terrarium
also the rollback feature rules because you can completely destroy your environment trying something stupid and then just reboot into the previous generation like nothing happened. extremely enabling if youâre the type of person who treats operating systems like a sandbox
void linux is great too. very fast. runit is clean in a way that reminds me of older game engines where everything is just. components. no giant invisible machine deciding things for you. sometimes modern distros feel like they were designed by a committee of ghosts but void is very âhere are the parts. good luckâ
for context iâm answering this while eating leftover noodles and listening to excuse 17 which feels thematically appropriate for a question about operating systems
also i once tried to explain nix to someone using a magic the gathering metaphor which did not help Them but helped Me a lot
because with most distros youâre basically playing spells one at a time like âinstall this packageâ âedit this configâ ârun this scriptâ
but with nix youâre declaring the entire board state ahead of time and the system resolves it. stack goes here, dependencies resolve, reality updates. which is cool if you like thinking about infrastructure as a system instead of a pile of commands
anyway realistically i end up building most of my environment myself now so the distro matters less than the layers sitting on top of it. but if someone forced me to pick a favorite itâs probably nixos for weird system design reasons and gentoo for nostalgia and suffering
and linux from scratch for emotional reasons which APPARENTLY i am not allowed to discuss
From two of your posts, your wife seems to have a... propensity to violence towards you. Are you sure you're safe?
OKAY first of all.
my wife does not have a "propensity to violence" she has a very high stress job and occasionally expresses that stress through her immediate environment and I happen to be part of her immediate environment, these are completely different things.
yes she has thrown things. the keyboard was a trajectory situation which we have already covered. there was also an incident with a stapler last month that I'm not going to get into because it was my fault and I knew it was my fault when it was happening. there was the time she slammed a door so hard a framed photo fell off the wall in the next room, which again, I had done something, I knew what I had done. there was the thing with the coffee mug last tuesday but that one genuinely wasn't my fault and she apologized, unprompted, which if you knew her you would understand is actually a significant gesture.
she also once told me that my organizational system for my secondary workbench was "a cry for help disguised as a filing system" which was hurtful and also possibly accurate.
BUT.
she reads every single report I send her. all of them. the long ones. the 47 page ones. she reads them and she has notes and the notes are good. she learned what a haptic array was because I needed to explain something to her once and she decided that was unacceptable and went and read three papers about it. three. on her own. unprompted. she keeps a penlight in her desk drawer because sometimes I need one and she has never once asked why. she named a Phillips head screwdriver after me. well. she had my name engraved on it. same thing. AND she calls me her darling AND she's an amazing mother to our daughter.
I am extremely safe. I am the safest I have ever been in my life. please mind your business about my wife.
Curious question, what are your thoughts on Wonder Woman thus far? I believe she has just recently joined the Justice League.
shes neat! I can't say that to my wife's face. like ever. the last time I did, she bashed my head with the coffee machine. but yeah, I see her on the news all the time and saw her interview with Lois Lane which was cool (my wife also does not like Lois Lane. so I don't like Lois Lane either).
I can't lie, Wonder Woman is kind of a narcissist though⌠everywhere i go, theres WW merch. like it gets to a point, man
before anyone says anything yes she is five yes she can barely reach the keyboard yes this is fine. motor skills are a spectrum and also the pistol exists
anyway we were on pillar of autumn and I was showing her how you can just. not fight things. like you CAN but you donât HAVE to. you can move through the level in a way that feels almost like youâre ignoring what the game thinks is important which is, in my opinion, the entire point of learning it properly
this reminded me of Cody Miller which is not where you want your brain to go while teaching a child anything but here we are
if you donât know, he was this early halo speedrunner who had all these records and then it turned out a lot of it was segmented and when he had to do a run live it just. collapsed. like completely. four hours, lowering the difficulty mid-run, not doing basic tricks, getting lost. there is a very specific kind of secondhand stress that comes from watching someone realize in real time that the system they thought they understood does not actually exist lol
and that got me thinking about verification, right. because speedrunning is basically just trust layered on top of systems. you either have inputs and footage that hold up or you donât. and once people start looking closely, timing inconsistencies show up immediately. like if something is off by even a fraction of a second in a place where it shouldnât be, it becomes visible
which is the same thing with animatronics!
like at Disneyland theyâve gotten very, very good at hiding the seams. the new audio-animatronic figures are doing all these micro-adjustments constantly, tiny timing corrections so the motion feels human. eye movement, hand lag, even the way weight shifts between steps. if the delay is wrong by even a little bit you feel it instantly. you might not know why but your brain goes thatâs not right
itâs the same category of problem. timing as truth (which is why the Cyberwalker package is Not Going as planned but thats a story for another time)
also Walt Disney was obsessed with trains which is a normal thing to learn and then immediately go too far with
because then you end up thinking about routing systems and failure cases and how everything is fine until one assumption breaks and then suddenly you have something like the CSX 8888 incident where a train just. keeps going. because one control input did not do what it was supposed to do and there was no immediate way to correct it
and now you have a five-year-old next to you asking why the aliens are purple and youâre explaining checkpoint triggers while also thinking about distributed verification and servo lag and runaway locomotives
anyway she likes the warthog. she keeps driving it directly into walls and laughing so I think sheâs getting it
So my last expedition went rather poorly and a rock decided to kiss my left knee! how fun...
Now I am bored out of my mind in this sad hospital bed.
Perhaps I should be more alarmed considering the doctors told me I'd have to use a cane for the rest of my life from now on, but I was already expecting this one way or another- just came with the territory.
though here I am opening a tumblr blog instead of preparing my next lectures, maybe I could make this a teaching moment somehow.
god I feel this... last month a neural interface prototype misfired during a calibration test and my wife threw a keyboard at me. not at me specifically! she was aiming at the wall (i think) but I was between her and the wall so. occupational hazard
also got a pretty bad paper cut from the incident report I had to fill out afterward :/ still healing
hope your knee feels better. canes have a lot of aura honestly. very distinguished
Oh dear, I hope you're doing alright, darling. Though rather curious why your wife would throw a keyboard in the first place, instead of venting in a much more healthy and productive manner.
Also thank you for your affirmation, it is much appreciated. â¤ď¸
I do agree with the sentiment too, canes are very fashionable. hopefully it won't inconvenience me too much on my field work however.
my wife wants me to clarify that she was NOT trying to hit me with the keyboard and that I should stop telling people she hit me with a keyboard. she did not hit me with a keyboard. it was more of a. trajectory situation.
honestly field work with a cane sounds extremely cool. all the best scientists have them. like dr House... that's my whole list actually. you're in good company though, he was a genius, solved like every disease! granted he was also mean to everyone around him and addicted to vicodin so maybe not a perfect comparison. sorry. the point stands. canes have aura and you will be fine.
