This is the second entry in a six-part series on my history of text editors.
The Eclipse and Aptana Phase
After a year at a crappy job with terrible pay cutting my teeth in web development, I got wise and applied at MRM. MRM is the digital agency for McCann-Erickson. I had a friend-of-a-friend who worked there and applied. I couldn't even fathom working at a place that prestigious. I got the gig and quickly learned how big, powerful ad agencies worked (mostly terribly when it comes to web dev). It quickly became clear that Coda was completely ill-suited for the job. MRM was the digital agency of record for General Motors. Their site's server-side language was all Java and our templating was all in JavaServer Pages (JSP). So naturally, I had to move to Eclipse. There was just simply no way around it. Everyone had to use it. I flipped between Eclipse and Aptana (a more front-end-focused fork of Eclipse) for those five months I worked there.
Five months may sound like a short time, but it was the richest learning experience I've ever had. Those five months working there are very vivid in my memory because I learned a ton. Namely, I learned that I hated having to work in Eclipse and couldn't wait to get back to Coda.
I got a call from a recruiter for a rival company four months in. I wasn't looking to leave, but I knew I was underpaid. I didn't mind too much because I enjoyed my job and I was learning. Also, it was the first job that made me feel like a professional. Still, my salary wouldn't exactly cut it for too long. So I took the interview, got the job, and asked for 80% more money than I was making at MRM — a salary I thought was surely absurd. No way would they say "yes" to that. They said "yes" without blinking. So off to Team Detroit I went.
Team Detroit (TDI) was Ford's digital agency of record (now you can see why MRM and TDI were rivals). Turns out, Ford's website had a very similar set up as GM's, and I was still stuck in Eclipse.