#codebootcamp

As I’m still figuring out what coding bootcamp is best for me, I’m preparing for admissions to all three of my top choices. App Academy is one of them, and right now I’m working through their admissions prep. The following is exactly how I worked through the first problem of their practice code challenge. This is copy/pasted directly from my codeanywhere.com IDE--I notate the shit out of my code because it forces me to think through the problem and understand my solution well enough that I can teach the methods learned to another newbie. Ruby docs are my world right now! 

**Warning: Solution included! Hopefully you’ve found this page after struggling with the problem on your own first.

#"Write a function lucky_sevens?(numbers), which takes in an array of integers and returns true if any three consecutive elements sum to 7.

#e.g.,

#lucky_sevens?([2,1,5,1,0]) == true # => 1 + 5 + 1 == 7 #lucky_sevens?([0,-2,1,8]) == true # => -2 + 1 + 8 == 7 #lucky_sevens?([7,7,7,7]) == false #lucky_sevens?([3,4,3,4]) == false #Make sure your code correctly checks for edge cases (i.e. the first #and last elements of the array)."

My process:

#Step 1: Define lucky_sevens?(numbers) #Step 2: Iterate over every element in groups of 3. #Step 3: During each iteration, sum the group and push sum to an array. #Step 4: If sums array elements include 7, return true; else, return false.

def lucky_sevens?(numbers)     sums = [ ]     numbers.each_cons(3) {|e| sums.push(e.reduce(:+))} #a/b     if sums.include?(7) #c         puts true     else         puts false     end end

#test: lucky_sevens?([1, 2, 4, 6]) # expected true lucky_sevens?([8, 9, -10, 11]) # expected true lucky_sevens?([3, 5, 6, 1]) # expected false lucky_sevens?([2,1,5,1,0]) # expected true lucky_sevens?([0,-2,1,8])  # expected true lucky_sevens?([7,7,7,7])  # expected false lucky_sevens?([3,4,3,4]) # expected false

#a: My initial thought process had me determining within each loop whether there's a sum of 7. Instead, this line iterates over each element of the input array in groups of 3, then the 3 element chunks are reduced within the iteration to a sum. That sum is then pushed to the empty array declared within the method. I wrote this solution hours before getting it to work. If I've learned anything about myself in the last 28 years, it's that I prefer to learn through suffering than learn from someone else's answer. So, I spent hours stuck in a cycle of incorrect output before I finally searched Google for the hints to a solution.

#b: The solutions I found on a couple of different forums were unsatisfactory in my opinion. They were not as simple or as easy to read and understand as the one I was trying to write. While reading through the comments of one forum (facebash) I had an aha moment and realized my problem was stupidly simple--I was using '<<' to populate the array with the sums instead of '.push'. These essentially do the exact same job, with one important distinction that I wasn't aware of: '<<' only allows the population of a single element at a time, while '.push' allows multiple elements to be pushed in one line of code! After fixing this, it finally worked.

#c: This if statement checks the resulting array of sums for the presence of the number 7, and outputs 'true' if detected; otherwise the output is false.

Have a refactor suggestion or a different solution to share? Help other new programmers and answer below!

Life has been crazy, guys! Boy, it's been nuts. What a wild couple of weeks it's been - very little time to stop and take stock. But I thought I'd share a little bit of what's been happening in the past 2 weeks.

StackStore - eCommerce Site

Working with in groups of 3-4, we created our first fully featured fullstack application using the MEAN stack. The project, StackStore, was designed to solidify our knowledge of authentication, session, local storage, and just what it's like to work on a team on a larger project. While it was a pretty grueling few days, we came out the other end with a mock online store. With a little more time, we would also have liked to integrate the Stripe API for payment processing, but we were really focused on a couple of key features - in particular, making the cart persist for both users and guests, as well as implementing powerful front-end filtering of our list of product. The project was difficult, but ultimately really satisfying. The greatest challenge for my group was losing traction over the weekend. We all worked a lot over the weekend, but when the week started and we were all in the same place, it was hard to review and integrate everyone's code in a timely fashion in order to finalize the rest of the app. In retrospect, I see how it would have been useful to make more and smaller branches. We learned a lot about the challenges of working remotely, and also making sure to communicate well as a team. All in all, I think the project was a success - and it was really nice to be working on a project with a team for the first time in the program. I haven't worked with a real team of people since I left A10 Networks about a year ago - and honestly working with a super amazing team is the thing I miss most from that job. (Seriously, shoutout to A10 TechPubs - they're awesome)

Stackathon

Created my first full-fledged independent project: SuperGender.

It was quite a doosy, and required 4 straight days of pretty much non-stop coding. (Also I was coding right up until the presentation.)

So what is SuperGender? Basically, I analyzed data from 100,000+ comic book characters from the Comic Vine API to determine some interesting gender-related trends in comic books. In particular, I was able to analyze the gender breakdown of characters, the average number of issues per character (broken down by gender), the top 10 origins (Human, Alien, Mutant, etc) of each gender, and the top 10 first name/title of character alter egos.

It was a really interesting and surprisingly difficult process. In order to analyze the Comic Vine API in a timely and dependable fashion, I created 2 scripts - one to query the /characters route for all characters and save them to MongoDB, and another to process all of the data and analyze it in order to seed stats objects on MongoDB as well. This meant that I was able to easily serve up all of my statistics without too much latency, and that the user on the front-end can filter statistics by Publisher. Right now, I've implemented filters for the major publishers (Marvel, DC Comics, Disney, Dark Horse Comics & Image Comics) - but in the future, I'm planning to add a search/dropdown to find data from any of the hundreds of publishers in my data.

Other improvements I'm planning include analyzing number of deaths per character by gender, adding filters for creation year of the character (this could highlight some interesting trends), analyzing the genders of friends/foes of characters by gender, and analyzing the gender breakdown of various superhero teams. I'm also curious about ways I might be able to use vision APIs to analyze skin coverage of male v. female characters.

By the way, I really love comics! I've been super excited about the new trend of making comics more inclusive. Between the new Captain Marvel, Thor, Ms. Marvel, and Batgirl, it's a pretty excited time to be a woman or girl who reads comics.

If you'd like to take a look at the code that I wrote to do all of this, feel free to check out the github repo. Would love comments and suggestions if you have any! It actually takes a long time to seed the DB, so I ended up creating the ability to seed in batches.

Tech Talk

I presented my mini tech talk to my fellow GHA classmates today, and had a great time! I talked a little bit about how to get a Phaser game started with a simple walkthrough. You can check out the demo and slides here. It was a bit nerve-wracking preparing to speak in front of everyone - the hackathon project took a lot out of me. But I'm glad I took the time to get familiar with Phaser. I was really happily surprsied at how easy it is to work with, and I'm looking forward to playing around with it and making some fun, nerdy games with it in the future.

Capstone

And now we're in the final phase of the program - capstone. We're still in the planning phases, and haven't 100% settled on an idea. But we have a good one cooking that we're pretty sure we want to go with. More on that as it unfolds... for now, let's just say it combines music and tech. We're still closing in on our exact project, but it's starting to seem like a lot of fun! Looking forward to sharing it in a few weeks when I (gasp) finish up the program? Just 3 more weeks!