Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If I were in your position, I would not be lazy enough to not review everyone's code. Even if you're not reviewing for the escaping of the user input, you still might want to see if their code is done efficiently. Or perhaps, it's not you to do the reviewing, but someone has to do it.</p> <p>I've experienced an almost similar setup no so long ago where we divided the tasks by layers. One worked on the model, I worked on the controller, and the other one worked on the views. Because we trusted everyone so much that everybody else's code will work the way we expected it to work, we didn't bother reviewing the other's code until the time that we needed to merge them. What happened was we discovered inefficient code in the model late in the development. And it wasn't just inefficient, it didn't work! Because of that, we had to overhaul huge chunks of the code which cost us more time.</p> <p>I suggest that you create a technical requirements specifications document where it is specified in it the acceptable inputs from the users. This document should be followed by the ones who will code the part that will accept the user input. Better yet, create unit tests to see if those requirements are being followed strictly so you do not have to worry if the data they're going to pass to you is invalid.</p> <p>Another thing... since you're using PHP, why not use a good framework? Most available frameworks come with their own DAL where you no longer need to worry a lot about escaping database input (well, not that much). The frameworks should do it for you.</p> <p>Also, you might want to look at 'prepared statements'.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload