Save us from this hell: how a magazine designer ended up in a Rails shop
I've worked with Rails since 2009. But I didn't get there as a developer. I got there as a magazine designer. Back then I was studying public relations at the Federal University of MaranhΓ£o, in Brazil, and thinking abou
I've worked with Rails since 2009. But I didn't get there as a developer. I got there as a magazine designer.
Back then I was studying public relations at the Federal University of MaranhΓ£o, in Brazil, and thinking about switching to design. A few of us had started a student-run junior enterprise in the communications program, and through a mutual friend there, my design work ended up in front of Eduardo and Fabiano, two partners at a company called Corebit.
Corebit was a Rails shop, and those two were very early Rails adopters. They worked out of an office inside the university through a startup acceleration program, and they were pumping out small admin applications for companies around them, using Rails to deploy fast enough that the work still paid off at low prices. What they needed was someone to design those admin interfaces.
So they called me in and asked if I wanted to work with them. I told them, "Well, I've never done web design, but I can look into it." I bought a few web design books, read as much as I could, went through case studies and examples of good practices, and thought, "Okay, I guess I can do this."
I'd send them my designs as Illustrator files, PDFs, or a bunch of PNGs, whatever they asked for. Then they'd go through the very manual process of turning them into websites, which at the time pretty much meant slicing images. "Tableless design" (which is an expression no one needs anymore) was still new, so a lot of those early pages were still done with tables.
After a few of my designs, they came back and said, "Look, we're willing to pay you more if you do the HTML and CSS for us. Just save us from this hell." That was more than 17 years ago, but that's the raw emotional memory that stuck. It was very annoying work and they didn't want to do it. I told them I didn't know how. They said, "No problem. Come over here and work at that table whenever you're doing anything for us. We'll help you with your first steps and teach you everything you need to get started."
A few days later, I remember sitting down in their office, putting my notebook on the table, and installing everything we needed to get started. I didn't have a Mac and really didn't want to invest in one, so we installed Rails on Windows. Yes, Windows. And let me tell you, that absolutely sucked back then!
Nothing worked on the first try, and installing any external library took a hundred Stack Overflow searches. And when you finally got it to work, everything was so slow that it was close to unusable for proper development. Many months later I moved to Linux, which was by far the best second option, and even that was still much harder to deal with than anything on a Mac. But at the time, Windows was the only option I had. They went through the whole installation with me, every annoying bit of it. Then I sat down with Fabiano, and he went through all the little details of basic HTML and CSS with me. He didn't even hand me links to read on my own. That absolute mad lad actually sat down with me and taught me the whole thing from scratch, which, thinking back, is nuts.
I got private lessons from a great, thoughtful Rails developer, and they were paying me for them.
I spent a few more months like that, doing freelance designs for things they needed fast. Then they landed a really big project that needed someone full-time, and they hired me. That was 2009, and that's when I officially joined my first Rails shop.
At first I was mostly doing HTML and CSS. JavaScript came in as a curiosity. The web was wild back then. People were trying very weird and unreasonable things, and you'd land on a website with some awkward animation and think, "How can I do that?" And someone would tell you that you needed JavaScript. Actually, not even JavaScript, you needed jQuery, because nobody was insane enough to learn raw JavaScript for front-end back then. It was pretty much a mess, years before ES6 cleaned things up.
So I started working with jQuery, and that's when I looked at myself and thought, "Oh, I'm a front-end developer now, working in a Rails shop."
And front-end in Rails is... very Rails-y. We were using Haml, so you'd be doing the usual Ruby in the template files: writing iterations in the views, touching Ruby classes, and figuring out how the controllers got things to the front-end. That's how I started writing a little Ruby and getting interested in Rails itself.
I still talk to everyone I worked with at Corebit. We're all in the same WhatsApp group, and Fabiano and I have been playing World of Warcraft on and off since back then. Whenever a new expansion comes out, I still go play a little with him, tho it's been a while now. He just invited me to his wedding. I can't make it, but I already know what I'm picking off his gift list:
We never lost touch, and I'm very, very grateful to them for getting me into this world of Rails.
Life takes strange paths. Many years later, I became a Ruby on Rails teacher and got to travel the world teaching it on four different continents. That's a different story, tho. Everything started with the amazing patience of two great Rails developers who somehow lived on the same small island way up north in Brazil as I did.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.
