Pull Request!

The milestone project for the end of Phase 2 of the Break Into Tech Skillcrush blueprint is to contribute to an open source project. This entails finding a project with issues on Github, claiming the issue, fixing it, and submitting a pull request to the owners/maintainers of the code.

As mentioned in the directions from Skillcrush, finding an issue for a first-timer can be a little challenging. I did a good amount of poking around on GitHub, and got fairly overwhelmed. The issues seemed waaaay beyond anything I would even know where to start to fix. But, plenty of folks want to encourage first timers to submit their first pull request and demystify the process, so I knew that somewhere out there an issue was waiting for me.

I came across the GitHub home of Public Lab – “A community where you can learn how to investigate environmental concerns. Using inexpensive DIY techniques, we seek to change how people see the world in environmental, social, and political terms.”

Public Lab seems to look specifically for first time and beginner contributors, which is great. But, the other problem seemed that issues got claimed very quickly. I really wasn’t sure how I was going to be “first” to an issue to snag it.

Then one sleepy morning as I was sipping my coffee before work, an email came in for an FTO (first-timers only) issue. I perked right up and went over and took a look, and was like – well, I *think* I can do this. The Public Lab folks are also very much – let us know if you need help, we’ll help you! So I asked to claim it and got the thumb’s up to proceed. The issue was for a project called Plots2, a collaborative knowledge-exchange platform in Rails.

The solution to the issue was to remove three lines of code from an erb file. This would remove a duplicate link to the project’s wiki. YAAAY to the Ruby course in Skillcrush for teaching what an erb file is, and to not be totally freaked out about working in one.

So that same evening, I forked and cloned the project, followed the instructions to remove the lines, created and submitted a pull request, and held my breath! The pull was accepted, and merged a week or so later. Yaaaay! Here’s a link – https://github.com/publiclab/plots2/pull/5653.

Happy to have this milestone wrapped up, and can’t wait to do more contributing to open source!

C’mon part two of phase two

So, so close to being done with the first part of Skillcrush’s phase two. Phase two is where you choose a developer or design track. There’s required courses for both tracks, and after you’ve done them, you have a counseling session, and then can continue on with some specialization courses. Since I want to learn ALL THE THINGS, I have signed up for some specialization courses (WordPress, Ruby, Ruby on Rails, etc.)

To get to my career counseling session, I needed to get done a “client project,” which for me turned into re-vamping a friend’s website, using stuff I’ve learned in Bootstrap. Took longer than I thought (why am I surprised by this?!) but I am thisclose to getting it up on a hosted Github page.

I also made a mock-up of the site using a template from one of the many mock-ups found online. Have wanted to fiddle with one of these for some time, so nice to actually get a chance to do it:

FANCY

Once it’s up, I can have my counseling session – talk one on one with a Skillcrush instructor – and move on the 2nd part of phase two, the specialization courses.

(And shout-out to Ann, one of the Skillcrush teachers who answers questions on the Git/Github Slack channel, for helping to me to figure out git weirdness – apparently I’d managed to put git on my main users file. How I managed to do that, not quite sure ….)

Also shared a bit in the Fears Slack channel about how I am sometimes overwhelmed by thought of – will I ever feel ready/confident to job hunt? Assuming I actually look, will anyone actually hire me? How can I learn ALL THE THINGS first?

This is by no means a new fear never expressed before; imposter syndrome comes up not infrequently in the channels in Skillcrush. Still pretty paralyzing while you’re in it, though. And really, all I can do is keep on keeping on. Here I go!

Icon Indecision (plus some HTML!)

I’m at the point in the Skillcrush course where I need to create a “simple icon” in Illustrator. I’ve been noodling around with the Bezier game – https://bezier.method.ac/ – to try and feel a little bit more in control of the pen tool. It’s helpful, for sure.

I’d like to create an icon for this site and also for myself, for freelance/side projects.

I haven’t gotten very far. I’ve done some sketches, but nothing that I’m crazy about.

I have to get this completed in 4 days, when my Illustrator trial runs out.

Yikes.

I also did some html-ing of the practice PSD I’m working on. In addition, working with git to create a new branch, merge it with the master, and then push it up to GitHub.  Looks like I successfully did those first two things, but am stuck on pushing it to GitHub. Skillcrush has a main “questions” email that I have written to multiple times – they are super helpful and get back quickly. So I’ve sent along my screenshots and will hopefully get an update on where I went astray, and then actually have an updated repo.

Tonight I just added all the text to the html. Next I want to link in the images. And THEN tackle stying.