Get an onsite interview, get early access to DALL•E. Good way to show rather than tell what kinds of projects you could work on here.
(Attached photo: "A walrus typing at a keyboard doing a programming interview at an office".)
We just decided we'll give early access to DALL•E for any applicants to @OpenAI who make it to the onsite interview stage.
Should help candidates get a better sense for where the technology is and how to think about the opportunity.
DALL·E 2 — generate any image from a text description. Imagination is the limit.
"A Shiba Inu dog wearing a beret and black turtleneck"
"A photo of a quaint flower shop storefront with a pastel green and clean white facade and open door and big window"
openai.com/dall-e-2/
AI engineering is poring through logs puzzling out why your run crashed, profiling to increase perf by a more few percent, and figuring out which code version was running during that weird blip.
Only when the model is finally trained do you realize it was magic all along.
In a startup, you should seek out activities that seem hard, boring, annoying, and unscalable. The highest-value tasks are often hiding amongst them, and no one else has noticed because they seem unappealing on the surface.
I am inspired by curiosity.
That is what drives me.
So let us expand the scope & scale of consciousness so that we may aspire to understand the Universe.
.@Replit can now automatically find bugs in your code using OpenAI Codex under the hood.
A concrete step towards transforming programming to be more about expressing your intent, and less about getting the incantations exactly right:
Rust is a purist's programming language in pragmatic form. Your compilers professor would approve, and you actually want to build big applications in it. First time I've seen both properties in a single language!
“When a distinguished but elderly scientist states that something is possible, [they are] almost certainly right. When [they state] that something is impossible, [they are] very probably wrong.” — Arthur C. Clarke’s first law.
Progress is made through heresy.
Underappreciated strategy for debugging a complex system: repeatedly strip away complexity, until you are left with either a working system or a minimal reproduction of your bug.
Simple on paper, but it's often the opposite of what will most appeal to your pride as an engineer.
That feeling when you get a segfault in Rust, and you *really* want to blame the language, but because it's Rust you already know you're the one to blame.
A surprisingly effective way to understand unfamiliar code is to translate, line by line, into another language.
The trick is getting to an initial minimal runnable program, and thereafter it's all incremental.