I seldom post, mostly on my activity on @StackOVerflow or updates for #phpdelusions
I follow only accounts that post on the technology, to keep the feed sane
Extreme Programming Explained by @KentBeck is basically the bible for teams that pair program. Its reputation is well-deserved.
Even though helped popularize the idea of pairing, it actually only has two pages on the subject!
You'll probably be surprised by what it says:
Extreme Programming Explained by @KentBeck is basically the bible for teams that pair program. Its reputation is well-deserved.
Even though helped popularize the idea of pairing, it actually only has two pages on the subject!
You'll probably be surprised by what it says:
@Sebas__SBM Not sure which issue exactly you mean and how it's related to PHP community but I believe that fixing the undefined behavior mentioned in the answer definitely was for the good.
@nask0 Thanks! Indeed, showing errors on the live server is a shame. Sadly the resource was all right. Hopefully they'll be back soon. Otherwise I'll have to remove the link
@johnbilicki@StackOverflow Exactly this. Your attitude is one of the things that are killing SO. Nursing and encouraging illiterate noobs who are trying to answer is where exactly SO sucks as a Help Desk. Instead of imposing strict quality standards SO just tells "go write any rubbish and earn awards!"
Gamification is killing @StackOverflow. It is not yet visible on the main site but regional sites are dying. Solely because gamification is only focused on providing new answers and never encourages editing existing information.
@johnbilicki@StackOverflow At least Reddit doesn't pretend to be the knowledge base. SO is trying to sit on two chairs, being both a help desk and the knowledge base. In reality being the latter only by declaration. Even in your tweet you are viewing SO as a help desk only.But is sucks in this role either
@GioDev8 Yes, the code is from my tutorial, directly or indirectly, that a matter of fact. But nowhere did I "accuse" you for using this code in your video, least for "stealing". Take your words back.
@GioDev8 And again. No, it's not that you took it from my tutorial that upsets me. But the fact that you misunderstood it and wrote ridiculous code as a result. This try is intended for the connection only. While query errors should keep their stack trace all right, and left out this try
Hey @GioDev8 your latest video is rather good but there is one thing is just horrible. Saying things like "we're not taking input from the user" is inviting disaster. The whole business of the second order SQL injection is built on it. There is NO excuse for adding a var to SQL
@GioDev8 I don't care if anyone is "taking" from my tutorial. I do encourage people to use this code. It is that you don't understand the approach and failed to implement it correctly which upsets me. After all your try catch makes no sense by itself, no matter where you took it from.
@GioDev8 All right, if you insist. Here is the try catch from the link under your video https://t.co/nqugQPUxas and here is one from my tutorial https://t.co/MbdAYcHawd now go tell me that you too the code for the former :)
@GioDev8 Yes please, I'll be very obliged if you address these two issues in the next video, encouraging your audience to use prepared statements in all circumstances. And to use try-catch with re-throw only for the connection but not for the queries. Thank you.
@GioDev8 Dude, you are literally basing your "opinion" on the tutorial I wrote. But you've missed the important part, that protection is only effective when used strictly unconditionally, without "speeding things up".