Chae and I were ready to go. Tyler walked in and we started session 3. I have a feeling that most developers are finishing up their christmas shopping on amazon, coordinating holiday schedules, and finishing up year long projects.
With such a small group we were able to discuss optionals, the topic of the night, deeply, and strategically. I’m most interested in created a best practices process that says, “Don’t ever use optionals. But if you must, guard them like this…”
We weren’t able to come up with hard and fast rules to follow concerning optionals. But we did discuss force unwrapping, implicit unwrapping, and the fact that optionals only have 2 states:
At the next meetup we’re going to be covering XCTests. I had a chance to write some tests for the first time this weekend. Main takeaway: I feel so much more confident about the code that I write. Here’s the XCTest video I suggested developers review before the next meetup:
Currently my tests prove that the code works with the expected input. I’m hoping to work this week on testing my error handling code by adding in tests to do just that.
This time we got together and there were only 5 developers, myself included. I had wanted the format to pivot around other people’s projects. Apparently, this strange time of transitions between Swift 2 to Swift 3, makes a need for syntax talks more important.
I’ve decided to focus on Swift 3 language topics for the next few meetups. This past meetup we spent the entire hour talking about Closures. In the middle of the talk, that I was leading, I found that I knew much less about passing functions than I thought I would.
We will be circling back to this topic as we continue to discuss Swift 3. Gotta say I love how clean the language looks. Here are a few more topics we will be discussing along the way:
- Swift JS Bridge
- Making a Tetris clone
Today we had our marketing meeting. I sought help from the marketing team. I needed their help in determining how the points will function in our Twitter Street Team Kiosk. We met for a good 30 minutes but it was barely enough time.
We listed out the behaviors we are interested in increasing. Then we assigned points to each of the behaviors. It was so helpful to get this kind of feedback before I build out the system.
Just in case you can’t read my scrawl, here’s what it says:
- Points will be tallied in real-time
- (10) – Find/Follow good source
- (10) – Tweet (engage)
- (2) – Retweet other sources
- (150) – Live tweet an event
- (5) – DM gets a quality response
- (1) – DM new followers
Dynamic points are added as the tweet performs online:
- (5) – For each click tweet receives
- (5) – For each reply tweet receives
- (1) – For each like the tweet receives
- (10) – For each retweet the tweet receives
I’m working with the point system in Python. No code to show yet. I am excited about this project and, now that I have most of the information I need, I can get started.
We also discussed the list topics were are interested in pushing:
- Focus 2
- Live Tweet Events
Student leaderboards will consist of the following attributes:
- Avatar image of user
- Screename of user
- Total points
Here’s what it looks like now:
Here’s how I’m hoping it will turn out:
Finally, here are some examples of the ideal leaderboard UI that I would like to see in the finished product:
Keep checking back here for updates. Here’s a link to the project on Github.