AND THE BIG NEWS IS (drumroll, please)

Red_HatNo, we’re not pregnant.

No, we’re not moving.

I have a shiny new job.

But first, some history.

I used to dance. And to pay for rehearsal space and costumes and performance venues, I taught myself HTML / CSS / javascript. Eventually I retired from dance and took web development seriously – interned in New York, worked with a few internet marketing companies in North Carolina.

Had a blast.

Then Red Hat changed their new hire scope – you had to have two of three requirements – customer service, technical skills, or linux. I had the first two. I was hired. I had a blast.

But when you work at Red Hat, every day is drinking from the firehose and I had to stop coding entirely.

Fast forward to a few months ago – you may have heard, I had a sweet little boy. I took advantage of the Netherlands parental leave policy and switched to part time to save money on daycare and spend more time with the new operating system.

The position I have now doesn’t allow part time work, so my main job was to find a new job. I didn’t know what I wanted to do, specifically, but I knew I couldn’t be a Technical Account Manager anymore. I started shot gun blasting anything that sounded interesting.

Fast forward to a few months ago when I took a DjangoGirls workshop and remembered how much I loved to code.

BAM!

That narrowed down my search to anything with development work.

But then it got tricky.

I’m starting over, effectively. I just started learning Python / Django / Ruby on Rails / MongoDB. But I can’t move to Brno where most of our junior developers start.

It took a few months to find the right opportunity within Red Hat.

So when I say “I have a shiny new job,” what I actually mean is “OMGOMGOMG I JUST LANDED MY DREAM JOB!”

I am a Red Hat OpenStack Software Engineer.

First few things learned @RailsGirls_Gron

– Reset the mac’s name to mac.
– Reset my username to krpl.
– Figured out how to su – FINALLY:

mac:~ krpl$ su -
Password:
su: Sorry
mac:~ krpl$ sudo su -

WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:
mac:~ root#

And also taking a FREE seven week MongoDB course

mongodbThe other month I thought to myself, “Self,” I said. “You need to LEARN MORE.”

“Let’s schedule all the learns at once.”

Not exactly.

But it seems as much, doesn’t it? Thankfully this is “only” week two of the M101P course so the content “isn’t that hard” [famous last words?] and I’m trying to get as much of it done before this weekend so I don’t have a time crunch before homework is due on Tuesday.

No pressure.

Prepping for Rails Girls Groningen This Weekend

railsgirls-sqThis Friday and Saturday I am attending Groningen’s Rails Girls workshop where I’ll learn to install and build an application using ruby on rails. I utterly love these things because there’s absolutely no pressure AND IT’S FREE.

Plus learning. Learning is cool.

Like bowties.

Running through the Setting Up Rails tutorial – specifically, the Setup for OS X – and everything is smooth as silk.

UNTIL.

[ yes, queue that dramatic music ]

Kristins-MacBook-Air:~ kristinrainpleander$ gem i rails --no-ri --no-rdoc
Fetching: i18n-0.7.0.gem (100%)
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions for the /Library/Ruby/Gems/2.0.0 directory.

No worries, I’ll just chown the directory:

Kristins-MacBook-Air:~ kristinrainpleander$ chown 777 /Library/Ruby/Gems/2.0.0/
chown: /Library/Ruby/Gems/2.0.0/: Operation not permitted

OF COURSE it doesn’t work because I didn’t have permission in the first place, why would I have permission to chown?

I’ll forget I’m on a mac and try to switch to the root user:

Kristins-MacBook-Air:~ kristinrainpleander$ su -
Password:
su: Sorry

Then, right, just use sudo:

Kristins-MacBook-Air:~ kristinrainpleander$ sudo chown 777 /Library/Ruby/Gems/2.0.0/
Password:

Nope, still no good:

Kristins-MacBook-Air:~ kristinrainpleander$ gem i rails --no-ri --no-rdoc
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions for the /Library/Ruby/Gems/2.0.0 directory.

Wait, use sudo on the gem install command. DUH:

Kristins-MacBook-Air:~ kristinrainpleander$ sudo gem i rails --no-ri --no-rdoc
Fetching: i18n-0.7.0.gem (100%)
Successfully installed i18n-0.7.0
Fetching: thread_safe-0.3.5.gem (100%)
Successfully installed thread_safe-0.3.5
Fetching: tzinfo-1.2.2.gem (100%)
Successfully installed tzinfo-1.2.2
Fetching: minitest-5.7.0.gem (100%)
Successfully installed minitest-5.7.0
Fetching: activesupport-4.2.1.gem (100%)
Successfully installed activesupport-4.2.1
Fetching: rack-1.6.1.gem (100%)
Successfully installed rack-1.6.1
Fetching: rack-test-0.6.3.gem (100%)
Successfully installed rack-test-0.6.3
Fetching: mini_portile-0.6.2.gem (100%)
Successfully installed mini_portile-0.6.2
Fetching: nokogiri-1.6.6.2.gem (100%)
Building native extensions. This could take a while...

That title should probably be AWKWARDLY prepping for Rails Girls Groningen This Weekend.