1. Use PHP Only When You Need it – Rasmus Lerdorf
Group items matching
in title, tags, annotations or url
12More
10 Principles of the PHP Masters | Internet Resources | Cpworld2000.com - 0 views
-
Lerdorf is the first to admit that PHP is really just a tool in your toolbox, and that even PHP has limitations.
- ...9 more annotations...
5More
shared by sloansteddi on 02 Mar 09
- Cached
How to use PHP and PEAR MDB2 (Tutorial) | David and Katherine Goodwin - 0 views
codepoets.co.uk/_php_database_howto_quickstart
MDB2 how-to tutorial database abstraction PEAR database dba PHP
![](/images/link.gif)
-
-
Prepare takes the $sql (with '?'s where data will go), along with the TYPES (array) of data to prepare the sql for, and a 3rd paramater for manipulating or result-getting (see next paragraph). It assigns this to $prepared_statement. Another array is created with the data (in the same order as the TYPES, of course), and the RESULT is aquired by running the execute() method on the $prepared_statement object, passing the execute method the "$data" array to fill in the '?'s After this do everything as normal.
-
- ...1 more annotation...
-
I have a feeling that MDB2 lower cases all field names - so you'll probably need : echo $row['name'] A good idea would be to print_r($row) or similar, to see what's in it
1More
Object-Oriented PHP: Delving Deeper into Properties and Methods - 0 views
1More
Generic Method - 0 views
1More
shared by fastidioustec on 29 Mar 19
- No Cached
Custom Web Application Development - Tips for Utilising Ecommerce Web Design Development - 0 views
www.knittingparadise.com/t-597588-1.html
web applications development Website Design Services magento development services website applications custom web development
![](/images/link.gif)
-
Each business faces unique challenges during its growth and web application development. This could depend on the type of business, to begin with. Those that sell physical products as opposed to services may wish to look into how ecommerce web design development could help boost their sales. The majority of consumers today shop online, finding it to be far cheaper and more convenient than going to a brick and mortar shop.
1More
shared by kolmasri kolmasri on 10 Feb 14
- No Cached
Estoy Systems for Web Solutions - 0 views
www.eystm.com
programming Framework open source Development webdesign Design Web Solutions Hosting E-Marketing php
![](/images/link.gif)
-
Estoy Systems for Programming all types of companies systems ,website design, e-marketing , web solution , and Programming your company system that would make your business is more easier with dealing to your employees and also your customer by a professional and invented ways as the international companies . regarding to the websites designing, e-marketing, web solution, with Estoy Systems www.eystm.com start booking your web site and then marketing this site and raise the degree of it at the global search engines SEO, and if you don't have a website you may wish also to enjoy our plans of e-marketing features , we announce your products and your services by a new e-marketing ideas, which would raise the value of your company's profitability by increasing the customers you have but even doubling their number.
4More
shared by sloansteddi on 20 Mar 09
- Cached
MDB2 | Prepare & Execute - 0 views
peardoc.m-takagi.org/...tabase.mdb2.intro-execute.html
prepare() execute() PHP PEAR MDB2 prepared statements setLimit()
![](/images/link.gif)
-
array('integer'), array('text', 'text')
-
$sth = $mdb2->prepare('INSERT INTO numbers (number) VALUES (?)', array('integer'), MDB2_PREPARE_MANIP); $sth->execute(1); $sth->execute(8);
11More
PHP Worst Practices at blog.phpdeveloper.org - 0 views
-
Sure, you could cobble together your own library to add that feature and yes, it might integrate excellently with your code, but what does that gain you? One of the points of Open Source development is to share your knowledge with the rest of the community.
-
If you’re writing your code without any sort of documentation, you’re dooming you and possibly future maintainers of the code into many a pointless search to try to figure out why method a() returns two completely different value types depending on which parameters it’s given.
- ...8 more annotations...
-
This would be the combined voices of everyone in your past that tried to teach you the mantra: “Plan First, Code Later”.
-
Just like ‘anti patterns’, who are an important read as well, ‘worst practices’ help developers avoid mistakes.
9More
Learning JavaScript from PHP - a Comparison | Lullabot - 0 views
-
In PHP, all variables are local in scope unless declared as global. JavaScript is opposite, and all variables are global unless declared with the var keyword.
-
JavaScript is a bit mixed concerning undeclared variables, if you attempt to modify or compare with an undeclared variable, the script will break entirely, but you can check the variable status using typeof() or in conditional statements containing only that variable.
- ...6 more annotations...
-
JavaScript only recognizes the keyword true in all lowercase. PHP accepts both uppercase and lowercase
-
PHP is not case-sensitive in function or class declarations, but JavaScript is case sensitive for these also.
-
JSON strings having become very popular as a faster alternative to XML, and can be read and created with the PHP functions json_encode() and json_decode().
-
Let's take one more look at defining an object in JavaScript and see how it can be used to compensate for the lack of associative arrays in JavaScript.
-
// Note that variables should always be// prefixed with "var" to define a local scope.for (var n = 0; n < 10; n++) { alert(n);}
41More
ongoing · Test-Driven Heresy - 0 views
-
the deep-TDD rules: ¶ Never write code until you have a failing test. Never write any more code than is necessary to un-fail the test.
-
we do way more maintenance than initial development. And in my experience, the first-cut release of any nontrivial software is pretty well crap.
- ...38 more annotations...
-
But to do that well, you absolutely must have enough test coverage that you just aren’t afraid to rip your code’s guts out
-
I always end up sketching in a few classes and then tearing them up and re-sketching, and after a few iterations I’m starting to have a feeling for X and Y.
-
once you’re into maintenance mode, there are really no excuses. Because you really know what all your X’s and Y’s are
-
Writing the tests points out all the mistakes you might make in signatures, prerequisites, etc. If the tests are too hard to make then you know that your API will be too hard to use, you're doing it completely wrong, and may as well pause for a rethink.
-
While the approach you advocate makes sense, it does require professionalism, not just from the developer but from management too.
-
the person left to maintain the code isn't the person who wrote it, leaving the maintainer with an unholy mess to untangle. Getting unit tests into such code is a monumental task.
-
he failure to address how unit tests can be introduced to an existing non unit-test codebase. (i.e. go from non-TDD to TDD)
-
I feel the TDD community only wants to focus on greenfield projects and has ignored maintenance/legacy issues. Which is strange when as you say code spends most of it's time in maintenance
-
The thing is that as long as the project is small you really don't see the benefits of TDD. I've done a couple of small projects and never had to go back to them ever again
-
You are writing the client code (in the form of a test) so you are thinking how the worker code will be used. What is its public interface and what do you want it to do when it's called
-
From: Tathagata Chakraborty (Jun 24 2009, at 07:31)TDD is useful in another situation - in a commercial setting and when detailed specification documents have already been created by say a technical expert/architect. In this case you don't have to do a lot of designing while coding, so you can start off with the test cases.
-
writing the tests *first* is that it helps keep your code focused on exactly what it's meant to do, and no more
-
When work on production code begins, most of the code should fall into the categories of things that are not to be tested.
-
One approach to the unknown X and Y problem that I've been using recently has been to pretend that class X has been written already, and then write code that uses this pretend X object/API. I usually write this directly in the file that will become my unit test. Since X doesn't exist, I'm allowed to call whatever methods I want and pretend it all works. Once I'm satisfied with how it all looks, I cut and paste everything into a bunch of failing tests.
-
that goes a long way towards taking software development from a form of artisanal craftsmanship to a real engineering profession.
-
It always seem to me to be a codified form of reverse engineering, or at least a way to force the programmers into looking at their code from two separate angles at the same time.
-
I do realize that this type of exercise might help younger coders in getting better structure, they do often rush in too quickly and focus more on the instructions than the abstractions.
-
He said he didn't write tests in cases where it would have taken him several hours to get a working test for a small piece of code.
-
In some applications, objects are self-contained, activities are sequential, and algorithms are tricky
-
I've seen cases where people have wrecked the architecture of systems in the name of making them testable... But have never written the tests.
-
Yes, it's possible to make peace with testability, and in the best situation, testability can improve the architecture of a program, but it can also lead people away from highly reliable and maintainable KISS approaches.
-
Like any infrastructure, it is always beneficial to provide unit testing. The most benefit is derived from installing it as early on in the project as possible.
-
The value of an untested feature, to a client, is ... zero. So, it doesn't matter how many of these you have rattled off in the past week, your net throughput is effectively... zero."
-
You can see in this thread the word "professionalism" (substitute "morality" with little gain/loss of substance) and even "sin" (used in jest, but not really!)
-
if I delay writing unit tests until after all the units are working together then because the system "already works" my subconscious enthusiasm for writing unit tests falls markedly, and so their quality and coverage fall
-
Experience teaches that if I generate that output by hand (1) it takes *much* longer (2) I almost always get it wrong. So I often write the code, get its output, carefully check it (really...) and then use it as the correct result.
-
My main objections to TDD are: 1) it promotes micro-design over macro-design and 2) it's hard to apply in practice (i.e. for any code that is not a bowling card calculator or a stack).