background preloader


Facebook Twitter

PHP tutorial for beginners.


/packer/ Slim. Behat — BDD for PHP. PHP: a fractal of bad design - fuzzy notepad. (This article has been translated into Spanish (PDF, with some additions) by Jorge Amado Soria Ramirez — thanks!)

PHP: a fractal of bad design - fuzzy notepad

Preface I’m cranky. I complain about a lot of things. There’s a lot in the world of technology I don’t like, and that’s really to be expected—programming is a hilariously young discipline, and none of us have the slightest clue what we’re doing. Combine with Sturgeon’s Law, and I have a lifetime’s worth of stuff to gripe about. This is not the same. PHP is the lone exception. PHP is an embarrassment, a blight upon my craft. But I’ve got to get this out of my system. An analogy I just blurted this out to Mel to explain my frustration and she insisted that I reproduce it here. I can’t even say what’s wrong with PHP, because— okay. Stance I assert that the following qualities are important for making a language productive and useful, and PHP violates them with wild abandon.

A language must be predictable. DeveloperWorks : Open source : Technical library. Top Design Magazine - Web Design and Digital Content - StumbleUpon.


Laravel. Auth/ACL implementation strategies « Internet Strategy Guide. I’m going to talk more about ACLs than Auth.

Auth/ACL implementation strategies « Internet Strategy Guide

Auth is simple, it’s the ACL that will trip you up. Since both concepts are coupled together when you’re making a login system, I feel it’s appropriate to at least touch on Auth. What I want to cover is the ways we can create the ACL object to suit needs based on the scale of the project. How to build role-based access control in SQL at Xaprb. The posts I’ve been reading and writing recently have reminded me how Object-Relational Mapping (ORM) systems make it fun and convenient to interact with databases.

How to build role-based access control in SQL at Xaprb

For some of the reasons they’re a developer’s favorite, they can be a database administrator’s nightmare (think surrogate keys). But designing tables with a consistent set of columns has its benefits. Just because the columns are meta-data that have no intrinsic meaning doesn’t mean they have no value. In this series of articles I’ll show you several ways to use such “meaningless” meta-data to enable powerful, efficient application-level role-based access control (RBAC) in the database, with a focus on web applications, though you could do this for any application.

A lightweight approach to ACL - The 33 lines of Magic » Debuggable Ltd. Ok, I just finished a terrible (extended) weekend that featured 12 hours of CSS coding.

A lightweight approach to ACL - The 33 lines of Magic » Debuggable Ltd

The only reason I didn't loose my sanity was that I finally decided to figure out what the heck is wrong with IE. Those of you who have to do get their hands dirty in the field of graphics, css, and other non-php work from time to time as well, make sure to check out Position is Everything at some point, it really helped me out quite a bit so far. Anyway, that's not really what I want to talk about today. One of the topics I have been very silent about for months is ACL.

At the end of May I was somewhat unhappy with some of the things regarding the CakePHP DB ACL implementation. But let me go a step back and explain my initial idea. Posts:index,Posts:view,Posts:admin_edit,Articles:index,... Datenbank-Verwaltung in einer einzigen PHP-Datei.


The Usability of Passwords (by @baekdal) #tips. Security companies and IT people constantly tells us that we should use complex and difficult passwords.

The Usability of Passwords (by @baekdal) #tips

This is bad advice, because you can actually make usable, easy to remember and highly secure passwords. In fact, usable passwords are often far better than complex ones. So let's dive into the world of passwords, and look at what makes a password secure in practical terms. Update: Read the FAQ (updated January 2011) Update - April 21, 2011: This article was "featured" on Security Now, here is my reply!

Getting Real. Here are the 16 chapters and 91 essays that make up the book.

Getting Real

Introduction chapter 1 What is Getting Real? A smaller, faster, better way to build software About 37signalsOur small team creates simple, focused software Caveats, disclaimers, and other preemptive strikesResponses to some complaints we hear The Starting Line chapter 2 Build LessUnderdo your competition What's Your Problem? Stay Lean chapter 3 Less MassThe leaner you are, the easier it is to change Lower Your Cost of ChangeStay flexible by reducing obstacles to change The Three MusketeersUse a team of three for version 1.0 Embrace ConstraintsLet limitations guide you to creative solutions Be YourselfDifferentiate yourself from bigger companies by being personal and friendly Priorities chapter 4 What's the big idea?

Feature Selection chapter 5 Process chapter 6 The Organization chapter 7.


Security. Tools. Articles. Libraries. Xampp.