Hi, I'm Laura. If you've read the about section of my website, then you already know a few things about me: I'm a developer, designer, alumna of the Flatiron School, and former Museum professional. I'm also a toddler mom, coffee-lover, and avocado-hater-- which I realize makes me a monster. The publication of this post officially establishes my newest and second-most-terrifying title: blogger. The first-most-terrifying is toddler mom, in case you were wondering.
I think design has always been in my blood-- seriously, my parents are architects. Identifying this trait as a professional turned out to take me a while. Looking back, I should've known. Everything I do is meticulously laid out and carefully formatted. Everything. My spreadsheets look nothing like spreadsheets and someone once joked that my to-do list was frame-worthy.
Technically speaking (pun intended), I'm trained as a full-stack engineer and not solely as a front-end developer. Actually, my very first experience with code was with SQL. At the time, I was unaware that all you needed in order to write code was a browser and text editor; I was under the mistaken impression that some fancy program was necessary. Because whatever program I was imagining was just that--imaginary--I didn't have access to one. What I did have, as part of my office's Microsoft suite, was MS Access.
When I first started using Access, I was primarily inserting SQL strings, but as I got to understand it better, I began to adopt VBA, and I got really, really good. I will likely do a post on this at a later date...try not to burst with anticipation. Part of the Flatiron School's application process requires building a working tic-tac-toe game. As Flatiron is a Rails-centric program, candidates were encouraged to write this in Ruby. I wrote mine in VBA. In retrospect, this is amusing.
It was at Flatiron that I started to realize that I might be a *gasp* front-end person. Armed with the knowledge of how to engineer and develop, so many of my classmates became absorbed, even obsessed, with methodically editing and refactoring their code until it was perfect. I, on the other hand, bugged them with questions about project usability and design. In group projects, I tried to implement what I now know are called "wireframes" to improve how the user goes through the site and sought to work out a cohesive and well-designed front-end.
I still site-map and wireframe for each and every one of my projects and I love the design aspect of my job, but I haven't abandoned my original love of getting lost in back-end code either.
Disclaimer (and non sequitur): if you started reading this hoping to learn about what to expect from this blog, I'm sorry to have disappointed you. I can, however, tell you three things to tide you over until we see how this endeavor rolls out.
- I am aiming for 1-2 posts/month. I'm open to more if I start to get the impression that myself and my mother aren't the only people reading.
- At some point in the future I will work to allow this blog to accommodate comments. For now, you can feel free to contact me via my website if you have questions or comments about what you read here.
- It is not my current intention that each and every post will be strictly and highly technical.
And now you know everything.