>>I figure it comes with programming. You have to know a lot of things about the businesses for which you write code. Even more so if you're designing the system. And it gets to you, this way of learning how to learn things about how does any human enterprise function. Because, who knows, you may need to design a system for it. Or it becomes a habit, or a so-called second nature.
>>
>>And one day you discover that not everyone has that breadth. Oh, well.
>
>I think I've always had the ability to store away useless bits of knowledge. I'm also the sort of person who goes to an event (or a restaurant or a meeting or ...) and analyzes how it's being run and what could be done better.

See what I mean :).

That's pretty much what I do, or should I say, happens to me anywhere I go. I almost sense the data flows, and specially where they fail :).

Except in restaurants. There, I don't want to know which waiter is in charge of my table, when does their shift end etc etc. I came to have a drink, not to work :).

Besides, I've already written a couple of restaurant apps. Not interested anymore.