It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
I dropped out of college for a startup job where I discovered an aptitude for and an interest in SQL and wound up designing databases and developing data access layers and application frameworks. Relational algebra and object-orientation are very different ways of thinking about systems, which made for an early introduction to working in broader contexts. It definitely didn't hurt matters any that we used a data mapper instead of an object-relational mapper which attempts to hide more of the inner workings of the database. Also helpful: I was responsible for managing the build server.
I've had more jobs and learned more languages and frameworks and worked with more databases and build tools since then, but that's what I started with. Getting a broader view is useful, but there's more to it than just adding keywords to your resume. Each and every new technology you learn is a new way of modeling something, a state or a process or both (and if it's only one, that's making significant implications about the other aspect). Software architecture is about understanding these models, getting a sense for how to use them effectively, and putting them together to achieve your own goals. The best stuff I've read on the subject has been about semiotics and meaning-making and so on, not about programming languages or design patterns.
I dropped out of college for a startup job where I discovered an aptitude for and an interest in SQL and wound up designing databases and developing data access layers and application frameworks. Relational algebra and object-orientation are very different ways of thinking about systems, which made for an early introduction to working in broader contexts. It definitely didn't hurt matters any that we used a data mapper instead of an object-relational mapper which attempts to hide more of the inner workings of the database. Also helpful: I was responsible for managing the build server.
I've had more jobs and learned more languages and frameworks and worked with more databases and build tools since then, but that's what I started with. Getting a broader view is useful, but there's more to it than just adding keywords to your resume. Each and every new technology you learn is a new way of modeling something, a state or a process or both (and if it's only one, that's making significant implications about the other aspect). Software architecture is about understanding these models, getting a sense for how to use them effectively, and putting them together to achieve your own goals. The best stuff I've read on the subject has been about semiotics and meaning-making and so on, not about programming languages or design patterns.
love this "Each and every new technology you learn is a new way of modeling something."
this is really helpful, thank you for sharing.