addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Austin PHP -- Code Review-A-Thon

  • Feb 14, 2013 · 7:00 PM
  • This location is shown only to members

Keith Casey will be moderating a live code review, so show up and spread the "love". Bring (drag) your significant others and bring some code! What better way to show your significant other how much you care for them to give them a chance to see you criticized in public. :P

Here are some guidelines to keep in mind, all criticism has to be constructive - criticizing someone else is easy but rarely useful!

Four types of things to look for:

Logical/Fundamental issues - Obviously this includes syntax errors - there were none - but also things related to the proper flow and functionality of the class.

Security/Performance issues - Just because code works as designed doesn't mean it doesn't do other things you don't want it to. Or to put it more coherently: the code should accomplish the desired task and no more while using the required resources efficiently.

Best Practices/Standards - This is somewhat of a squishy subject. There are numerous competing coding standards out there and they're competing for valid reasons. Luckily, Best Practices are relatively clear and becoming more established.

Style/Preference Choices - This is the squishiest point of all. This starts to touch on the design of the code versus the rest of the system, whether the code should support multiple [choose one: operating systems, databases, http functionality] which really only matters if the code is supposed to be re-distributable.

Like us on Facebook!

Join or login to comment.

  • Ed G.

    Small group probably due to Valentine's day, but a great discussion.

    February 18, 2013

  • Jake

    Hah yes wish I could!

    February 14, 2013

  • eli

    Programming at 7pm on Valentines? You guys are too hardcore.

    February 13, 2013

    • Logan L.

      You can just celebrate it on Friday! :)

      1 · February 13, 2013

  • Daniel H.

    Just realized this is On Valentine's day.

    February 12, 2013

  • A former member
    A former member

    unfortunately, my significant other would probably not go for this...

    February 11, 2013

  • A former member
    A former member

    Shouldn't "Performance" and "Security" be completely separate topics?

    January 25, 2013

    • Logan L.

      Sometimes at least they are 2 sides of the same coin.

      January 26, 2013

26 went

Our Sponsors


    Visit today and save on Computers, Networking Gear and more.

  • Apress

    High quality technical reference material at a reasonable price!

  • JetBrains PhpStorm

    PhpStorm is a lightweight and smart PHP IDE!

  • O'Reilley

    Discounts on tech books and training videos.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy