One of the responsibilities for an architect is to provide a space that is usable and enhances the possibilities for what you do. But mostly, museums are just the opposite; they're horrible spaces, anti-art, they can't be used. They can't function, they overwhelm it. So in a way, they become objects in themselves many times, almost sculptures, and they get a lot of aggrandizement out of it...In terms of Bilbao, the one difference there is that they did not really want a museum, they wanted a monument. They wanted a thing that would bring people to the Bilbao.
One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it.
...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun.