It was many years ago – back in my twenties – when I first put a visit to Las Vegas on my radar. That plan got cancelled, I went to London instead, and ever since I’ve been telling folks that I intended to go someday – just to see it.
That day came.
Cool stuff. And crazy stuff. And I haven’t even seen much of any of it.
Yeah, I would come back – now that I have the lay of the land (a little?), I could plan a fun trip for a weekend that would be totally worth it. But I’d also be fine with never seeing it again. So it’s on the list of possible future vacations.
The most magical piece of it, though, was seeing a Michael Jackson tribute show done by Cirque de Soleil. Truly beautiful and magical. And makes me sad that I’ve never listened much to his music.
This morning we will try a true Vegas buffet for breakfast – the kind that we have always heard so much about. And I’ll get to measure it up against our fancy dinner last night!
Then, off to the desert for the drive back to Los Angeles for our flight home… 🙂
A content engineer is a tech person who uses tools to create, deliver, and make available relevant content in some sort of automated fashion and in various formats for a variety of audiences. At least that’s one way of interpreting the “content engineer” title – it’s sort of a new field.
We all know what an information systems engineer is – the person who fiddles with all the servers and network equipment to make your life difficult. Just kidding – to solve all your problems.
This is something I kind of just made up. Maybe somebody else already has an idea about it and has written about it, but not from what I can tell after a morning of research.
In my view, an info-engineer falls somewhere between the content engineer and the content marketer / strategist. More in the realm of automation and process, but also doing a lot of crafting of content as needed. But the focus is on information, not on systems. Systems only exist so that we may better use information, after all! Working effectively with information (a type of content) is the key.
The info-engineer doesn’t simply create content, but also creates processes and identifies obstacles to the efficient creation of content – without any fear of getting hands dirty with manual content crafting integrated into the whole process.
The information systems engineer, in contrast… does other stuff… techy stuff.
I’m thinking the two of them should cross paths more often! 🙂