Skip to main content

Home/ PHP Programming/ Group items matching "Me" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
spymek soft

Find Around Me - 0 views

itunes.apple.com/...id520405128

Find Around Me free iphone app

shared by spymek soft on 01 Aug 12 - No Cached
  • spymek soft on 01 Aug 12
     
    Find the places around you that you need the most and usually search for(when you are not aware of the area) at the tip of your finger. May it be ATM or gas stations or beauty sallons, you will get the list of these in few seconds. Also you will get the route map from your current location to destination. Simple and Useful app.
qualitypoint Tech

Adding piece of PHP code in all files within a sub-folder - 4 views

qualitypoint.blogspot.com/...-of-php-code-in-all-files.html

php Web hosting

shared by qualitypoint Tech on 11 Jun 10 - Cached
  • qualitypoint Tech on 11 Jun 10
     
    In this post I will explain about how to add piece of php code in all files (including new files to be added) within a particular sub-folder in Apache server hosting environment. Let me explain why we need to add piece of php code in all files within a folder.
  • Bart Deruyter on 11 Jun 10
     
    I wanted to read it, but I won't, because Chromium blocked it and gave me a warning that the site hosts malware... just to let you know.
  • qualitypoint Tech on 12 Jun 10
     
    Bart Deruyter Thanks for your note, now it should be fine.we removed unwanted external links.
Bart Deruyter

PHP Security Guide - 0 views

php.robm.me.uk

webdevelopment

shared by Bart Deruyter on 15 Jan 09 - Cached
    • Bart Deruyter
      Bart Deruyter on 15 Jan 09
       
      very interesting info about security for beginning PHP developers
  • Bart Deruyter on 15 Jan 09
     
    Very interesting webpage about security with PHP. Reading this through is a must for beginning PHP-developers (like me).
Steĥane Gosselin

A Shiny New Me * JsFiddle Tips And Tricks - 0 views

a.shinynew.me/...jsfiddle-tips-and-tricks

javascript

shared by Steĥane Gosselin on 06 Jan 12 - No Cached
  • Steĥane Gosselin on 06 Jan 12
     
    jsFiddle tips and tricks
Jackie Fields

IT Management Conference & Expo in NYC Oct.14-16 - 0 views

www.diigo.com/...agement-conference-expo-in-nyc

IT Management Leadership CIO CTO CEO MySQL PHP Zend PMP

shared by Jackie Fields on 26 Jul 09 - Cached
  • Jackie Fields on 26 Jul 09
     
    http://www.manageit.me ---The greatest minds in IT in 50+ presentations : top industry-leaders: Creator of MySQL Michael "Monty" Widenius, Internet Celebrity Gary Vaynerchuk, Co-Creator of PHP & Zend CTO Zeev Suraski, Richard Sheridan, CEO of menlo Innovations & Pioneer of Agile eXtreme Programmi...
Raúl - [^BgTA^]

Dmytro Shteflyuk's Home » Blog Archive » Zend Framework: Using Smarty as template engine - 0 views

kpumuk.info/...sing-smarty-as-template-engine

framework php smarty zend

shared by Raúl - [^BgTA^] on 24 Apr 07 - Cached
    • Raúl - [^BgTA^]
      Raúl - [^BgTA^] on 24 Apr 07
       
      Esta me parece una de las mejores soluciones, es decir, integrarlo en las Views de Zend. Una vez definida esta nueva View 'Smarty', solo hay que: $reg = Zend_Registry::getInstance(); $reg->set('Smarty', new My_Smarty_View()); ... para registrarlo, y podremos llamar desde cualquier .php a smarty de la siguiente manera: $reg = Zend_Registry::getInstance(); $reg->get('Smarty')->assign('foo','bar'); $reg->get('Smarty')->render('foo'); o bien: $smart = $reg->get('Smarty');
  • Raúl - [^BgTA^] on 24 Apr 07
     
    Integrando Smarty en Zend Framework
  • Raúl - [^BgTA^] on 24 Apr 07
     
    Integrando Smarty en Zend Framework
Sarah HL

PHP Depends On You | BrandonSavage.net - 0 views

www.brandonsavage.net/php-depends-on-you

shared by Sarah HL on 25 Aug 09 - Cached
  • elf in the community
  • PHP is one of the world’s largest open source projects.
  • people who write open source software generally aren’t paid to do it.
  • ...6 more annotations...
  • the core of PHP is contributed by people who are solely interested in making PHP better for their professional endeavors
  • it can be as simple as contributing to the documentation, or submitting a bug report
  • The community exists because people choose to contribute.
  • file a bug report or write some documentation today.
  • Remember: PHP depends on people just like you.
  • My Boss told me to prepare a paper how we interact good with open source project and how we can generate a win win situation on both sides by submitting (correct) bugreports.
Sarah HL

Nexen.net : portail PHP et MySQL - De retour de PHP Québec 2008 - 0 views

www.nexen.net/..._retour_de_php_quebec_2008.php

testing test lang:fr tools opensource

shared by Sarah HL on 03 Jul 09 - Cached
  • Il m'a signalé deux projets de BDD, qui permettent de faire le pont entre les demandes de tests fonctionnels, émis par des clients non-techniques, et les tests unitaires. Il s'agit de greenpepper (http://www.greenpeppersoftware.com/en/, Open Source et commercial ) et easyb (http://www.easyb.org/, logiciel libre).
  • Ces deux logiciels permettent de capturer les tests fonctionnels : on note les demandes de tests, puis on les convertis en un pseudo-langage. Une fois celui-ci écrit, le logiciel produit des tests fonctionnels à faire passer, et à exécuter automatiquement. Le concept est une couche qui ressemble aux tests unitaires, mais prend le problème à partir des clients, et non plus à partir des besoins de tests des couches base. Le concept est prometteur, notamment en conceptualisant les tests et les demandes clients, même si elles sont peut claires. Je me promets d'y consacrer un peu de temps.
Sarah HL

ongoing · Test-Driven Heresy - 0 views

www.tbray.org/...TDD-Heresy

programming tests test_driven testing lang:en

shared by Sarah HL on 02 Jul 09 - Cached
  • As a profession, we do a lot more software maintenance than we do greenfield development.
  • 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.
  • I freely admit that this is not really truly TDD
  • 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
  • Never use mocks unless you are mocking an interface that will almost never change
  • 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.
  • In theory, TDD is a great idea. The problem with TDD can be expressed in one word: money.
  • 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.
  • I get really bored adding tests to code that already runs
  • the seductive TDD trap
  • religious zealots
  • There is nothing wrong with building tests after you have built your product.
  • that goes a long way towards taking software development from a form of artisanal craftsmanship to a real engineering profession.
  • using tests to drive development cripples innovation, dramatically slows development
  • 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.
  • If you're just adding tests at the end, then it's normal unit-testing, isn't it?
  • 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.
  • TDD is test-driven *design*
  • 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).
  • the tests are just a persistent artifact of the exploratory coding I've already done.
Sarah HL

Pourquoi critiquer autant PHP ? « rand(0) - 0 views

blog.eexit.net/...quoi-critiquer-autant-php.html

shared by Sarah HL on 07 Sep 09 - Cached
  • Je me demande pourquoi est-ce l’image de PHP n’est pas aussi « bonne » que celle de Java ?
  • PHP permet cette anarchie mais c’est à vous, architectes, de vous former et de savoir utiliser les bonnes méthodes et outils pour commencer le développement d’un projet évolutif, sécurisé et léger.
  • PHP offre aujourd’hui la possibilité d’appliquer les principaux design patterns à vos applications ainsi qu’une implémentation objet du langage même si PHP ne sera jamais un langage 100% objet, mais c’est ce qui fait sa force.
  • ...2 more annotations...
  • Il peut intervenir à tous les niveaux de votre application : L’exécution de tâches automatisées CRON ; Des simples scripts CLI de maintenance sur votre serveur ; Des scripts de services toujours exécutés en CLI sur votre serveur ; Pour le développement d’une application fenêtrée GTK ; Le développement d’une application Web aussi simple ou complexe soit-elle ; etc.
  • « le client a demandé certaines évolutions que nous n’étions plus en mesure de développer sur notre application sans devoir tout casser… » Je voudrais bien savoir quel genre d’évolutions le client a demandé pour devoir en arriver là… Est-ce réellement dû à une limite de PHP ou à une mauvaise utilisation du langage ?
Sarah HL

Un projet sans développeur ? | Industrialisation des développements PHP - 2 views

www.industrialisation-php.com/un-projet-sans-developpeur

php programming conception ihm uml

shared by Sarah HL on 26 Nov 09 - Cached
  • Il ne s'agit pas de s'en passer  totalement : même les générateurs de code doivent être programmés par quelqu'un....
  • celui qui a produit le code
  • devient rapidement un passage obligé pour nombre de phase de vie de l'entreprise, alors même que le code a quitté son giron depuis longtemps.
  • ...4 more annotations...
  • un script de déploiement automatique permettra de le faire sans interroger l'auteur du code
  • On peut assurer de nombreuses tâches comme ceci : tests unitaires automatiques (phpunit alltests.php) analyse statique (pmd) déploiement (phing, capistrano)
  • Quand on travaille sur du code dans un projet, il est important de savoir s'en séparer, de couper le cordon ombilical. Si on est le seul à maîtriser une application, on devient indispensable, et on risque aussi de finir enchaîné à des corrections et évolutions infinies.
  • comment mes utilisateurs pourront-ils faire des modifications sans passer par moi?
1 - 11 of 11
Showing 20▼ items per page