Blog.

  1. W2D4 (Week 2 Day 4)

    minsoo-at-app-academy:

    …Today’s project was checkers, which was a simpler variant of yesterday’s project, chess. While I had essentially had a cheat sheet right in front of me (by referencing/copying part of the chess code), I was determined to nail down the object oriented design concepts. So I tried to program the game from scratch as much as I could, only going back to the chess program when I got stuck with a bug. 

    The project itself went along pretty smoothly, but I ended up falling behind due to a bug that took roughly 2 hours to fix. It really shouldn’t have taken that long to fix, but coding without tests made the subtle bugs difficult to find. Thankfully, the final iteration of the project completed at 6 pm was fully functional and bug-free, which made me extremely happy. It handled various exceptions gracefully with rescue methods and generally maintained a clean coding style. The outcome of today’s project made me realize for the first time in App Academy how much I’ve learned in the two short weeks that I was here. I can only imagine how much better of a developer I will be once I complete this program.

    By the way, here’s a screenshot of the checkers that I made!

    image

  2. Week 2/Day 3

    ryanappacademy:

       Success! We finally finished our Chess game, with a decent UI to boot! This is hands down the most extensive project I’ve ever created, and I’ve got to admit that it feels pretty damn good. Although we had our fair share of debugging (a ton, actually!), it feels really rewarding to be able to kick back and play our game of chess. 

       I’d really like to learn to use the getchoperator properly next, so I think I”ll eventually add that to our Chess game. I thought my partner Anastasia and I did a pretty solid job with the colorize gem, displaying a good looking board with Unicode pieces. The thing we learned, I think, was to carefully test each method as we progressed through them, as trying to find piles of errors at the end is frustrating and extremely difficult. 

       Here’s a picture of how our Chess game looked:

    image

  3. A Real Man's Game [W2D2]

    johnochs:

    We’re on to chess!

    The fact that I am not a chess player has not seemed to hinder our first day’s progress on our chess game. The concepts that have been introduced today were fairly straight forward in how they can benefit our implementation:

    • Inheritance & Extending Classes
    • Overriding…
  4. Git Reviews

    linhpbui:

    Side note: Check my code for minesweeper here.

    1. Git Basics

    • DVCS: Rather than a single, central repository on which clients synchronize, each peer’s working copy of the codebase is a complete repository. Distributed revision control synchronizes repositories by exchanging patches (sets of changes) from peer to peer.

    Read More

  5. Week one down!

    appacademygraser:

    With one week in the books I feel confident saying that this is one of the best decisions of my life. I’ll probably devote a post next weekend to my personal experience with the application process and my first weeks here, just in case anyone besides David Runger ever reads this.

    For now, I’ll…

  6. W1D3

    aaronshurley:

    Today was a change of pace as we took on two larger projects rather than a series of smaller exercises. Without the quick positive reinforcements from the quick exercises, it took a lot more determination and focus to get through the project implementation. We learned that a thoughtful concept and…

  7. W1D2 Getting Hang of Pair Programming

    codepug:

    Day # 2 of App Academy!

    Today I felt so much more comfortable with pair programming. We went through the exercises with good style in mind, and learned a whole lot about class (especially all the attr_accessor, instance vs class methods etc), which I have been struggling with. After reviewing the…

  8. Final project

    yuritoburrito:

    Picturito.com

    No N + 1 queries. Caching. Compression. You’re welcome.

  9. gog33kym:

    What Did We Learn in Week 28?

    We learned

  10. kevinvognar:

I had a pretty fantastic time running the full gamut of the Stack, building the Rails foundation for polymorphic user/artist/article follows and the Backbone interface (buttons) for creating those follows, then creating the polymorphic notification system to actually put those follows to work. It was great fun - I love shifting between layers like that, working in different modes of logic and different languages, tweaking this and that to make the whole engine run smoothly. Users now get a record of updates to things they follow, accessible in a neat (imperfectly styled) dropdown menu from the navbar. I actually made this!
There were a lot of stumbling points throughout this today, but once things started to come together and my modular bits of logic started fitting into new places, everything flowed together so nicely.
I have a long list of small features to add, so the next two days are for sprucing up everything I’ve done so far. So much to do~

    kevinvognar:

    I had a pretty fantastic time running the full gamut of the Stack, building the Rails foundation for polymorphic user/artist/article follows and the Backbone interface (buttons) for creating those follows, then creating the polymorphic notification system to actually put those follows to work. It was great fun - I love shifting between layers like that, working in different modes of logic and different languages, tweaking this and that to make the whole engine run smoothly. Users now get a record of updates to things they follow, accessible in a neat (imperfectly styled) dropdown menu from the navbar. I actually made this!

    There were a lot of stumbling points throughout this today, but once things started to come together and my modular bits of logic started fitting into new places, everything flowed together so nicely.

    I have a long list of small features to add, so the next two days are for sprucing up everything I’ve done so far. So much to do~