Hope you have better luck ;)
An assumption: it is bad for the prospective employer to see no code at all.
I see two basic options:
1) see code written before the interview, and
2) see code written during the interview.
Option (1) has a few sub-options:
a) look at open source work,
b) ask for private personal work to be made available, and
c) ask for custom work of your choosing.
All of these share the weakness of requiring work outside work hours. There are many qualified candidates who don't have work of the (a) and (b) sort available, and while many see option (c) as a welcome intellectual challenge, many others see it as a tedious (or even offensive) waste of their time.
Option (2) also has a few sub-options:
a) provide a computer and a project or set of coding questions to be solved in your absence,
b) same as (a) but with pen and paper,
c) ask a question and watch on a projector or over the shoulder as it is solved on a computer,
d) same as (c) but with pen and paper, and
e) same as (d) but on a whiteboard.
Option (a) is basically the same as (1c) above, but attempts to mitigate the waste-of-time factor by using already-committed interview time to do it, and option (b) is just a much worse variant of the same. The weakness of these options is that it is impossible to get an idea of a candidate's thought process while solving the problem. Option (c) is really good for interviewers but very high-pressure, which selects against many qualified candidates. Option (d) and (e) are identical, but some people hate pen and paper, others hate whiteboards, and most hate both! It is imperative when not using a computer to avoid requiring or judging by the use of things that computers help support, like specific languages, specific APIs, or syntactic accuracy.
Or is this all wrong - have you found the general solution?
Can you write code? Yes? Well then you probably can fit the role of somebody who is hired to write code.
Nobody on the planet is expecting you to waltz in the first day and grok their entire stack and their entire codebase; expect the first couple of months to be just you getting your head around what you'll eventually be doing.
Don't sweat it, you'll be fine :)
edit: but maybe it is not the same in Silicon Valley?
If you're in the interview room, I'm not so concerned about book learning and knowing facts, but whether you have the correct amount of knowledge to do the job and the ability to apply it.
You can know the name of a bird in all the languages of
the world, but when you're finished, you'll know
absolutely nothing whatever about the bird... So let's
look at the bird and see what it's doing — that's what
counts. I learned very early the difference between
knowing the name of something and knowing something.
- Richard Feynman https://en.wikiquote.org/wiki/Richard_Feynman and https://www.youtube.com/watch?v=05WS0WN7zMQI got the job, and learned something along the way
Well you sure do talk the talk. ;)
Ba-dum---Crash!
A funny coincidence, i did journalism too -- you're not missing out on ANYTHING (I'm trying to escape the career myself, even contemplating school).
I'm not a formally schooled developer. I don't know a heap about traditional computer science. I don't know all the sorting algorithms off hand (but could throw one together with a little time and reference). I'm not even fluent in all the jargon, vernacular and glossary terms that devs bat around.
I don't know if I'm the best for this job, but I know only 3 short years ago, I was doing graphic design and 3 years before that, I was trying to make good on my degree (and dream) of journalism.
None of us choose how we learn, but I think the best of us just know how to.