Creative sciences

Art, photography, content, and modeling all live here, and I group them deliberately. They look like four hobbies and they're one skill: taking something that exists only as an idea and getting it into a form other people can actually see. Art. I work in graphite, ink, and watercolour, and I shoot photography — mostly on a phone, because the constraint is interesting and the camera you have beats the camera you don't. Traditional mediums taught me two things that transfer to engineering more directly than anyone tells you. Patience, first: a drawing cannot be rushed and will visibly tell on you if you try. And attention to detail nobody asked you to pay — the part of the work that no one will consciously notice but everyone will feel is missing. Ink is unforgiving in a way I've come to appreciate. There's no undo. You commit, and if it's wrong you incorporate it or you start again. That's closer to how most real decisions work than software's endless revisability suggests. Photography and content. I handle the full chain on my own work: concept, styling, direction, shooting, editing. It's the same loop as shipping a feature — build the thing, look at it honestly, revise, ship — with a different output and a much faster cycle. That speed is why I find it valuable alongside engineering. A feature takes weeks to learn from. A shoot takes an afternoon. Doing all the roles myself means I understand what each one costs, which makes me better at working with people who specialise in one of them. Modeling. Modeling started as an exercise in deliberate discomfort and became something more interesting than I expected. Being in front of a camera teaches presence, posture, and how you occupy a room — traits that turn out to matter well beyond photographs. A lot of leadership, networking, and pitching comes down to how you carry yourself while saying something, not just what you say. It also put me on the other side of a process I usually direct, which made me better at directing it. Why "creative sciences." Because the process is systematic even when the output isn't. Concept, constraint, execution, critique, revision. Set up the conditions, see what comes out, adjust the conditions. That's a method, and it's not a different method from the one I use for everything else — it just produces images instead of systems.