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 think about my second job. I'd just come out of a startup where I'd gotten a taste of cutting-edge technology and techniques and landed in a developer-analyst role in automotive manufacturing, where everything seemed years behind the times in comparison. All the existing code was VB6. I did a lot of COM interop, and if you don't know what that is, be thankful. Source control consisted of "ask X if he's got the latest version of that code, or uh try to find it on one of these old laptops I guess". I set up an SVN server because my god what are we, animals? Do we eat nuts and berries and shit in the woods too? I test-drove development and approached problems iteratively and moved fast and broke things and all that stuff.
And nothing changed. Nobody else adopted TDD or even used my SVN server. I wound up changing how I worked, because I realized quickly enough that I was shipping code that wasn't fully baked. I'd gotten used to having centralized product and the ability to deliver patches whenever I wanted. When installation and updates both mean someone (very possibly you) has to fly across the Atlantic, put on goggles and earplugs and a safety vest, walk half a mile to plug a USB key into a station, and stop an assembly line for hopefully under a minute, the thing had better work right when it comes up. And for all the other developers at this place were studiously ignoring all kinds of standards and best practices and so forth, they understood the context they'd been working in far better than I did coming into it.
I ate a lot of crow at that job. Not because I wasn't good at what I do, but because I thought that that meant I understood what was right for the environment I found myself in better than the people who'd been in it for years before me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think about my second job. I'd just come out of a startup where I'd gotten a taste of cutting-edge technology and techniques and landed in a developer-analyst role in automotive manufacturing, where everything seemed years behind the times in comparison. All the existing code was VB6. I did a lot of COM interop, and if you don't know what that is, be thankful. Source control consisted of "ask X if he's got the latest version of that code, or uh try to find it on one of these old laptops I guess". I set up an SVN server because my god what are we, animals? Do we eat nuts and berries and shit in the woods too? I test-drove development and approached problems iteratively and moved fast and broke things and all that stuff.
And nothing changed. Nobody else adopted TDD or even used my SVN server. I wound up changing how I worked, because I realized quickly enough that I was shipping code that wasn't fully baked. I'd gotten used to having centralized product and the ability to deliver patches whenever I wanted. When installation and updates both mean someone (very possibly you) has to fly across the Atlantic, put on goggles and earplugs and a safety vest, walk half a mile to plug a USB key into a station, and stop an assembly line for hopefully under a minute, the thing had better work right when it comes up. And for all the other developers at this place were studiously ignoring all kinds of standards and best practices and so forth, they understood the context they'd been working in far better than I did coming into it.
I ate a lot of crow at that job. Not because I wasn't good at what I do, but because I thought that that meant I understood what was right for the environment I found myself in better than the people who'd been in it for years before me.