Skip to main content

Home/ PHP Programming/ Group items tagged Application

Rss Feed Group items tagged

Jungle Jar

JungleJar | Wordpress How-To: Displaying Post Counts - 0 views

  •  
    Ever wanted to display the number of posts your blog has achieved for your blog readers or perhaps just for yourself? Or, what about the number of posts in a specific category? If so, I'll show you a quick and easy way to do just that, and we'll style up the output with a bit of CSS Level 2.1 the standard way.
Sarah HL

ongoing · Test-Driven Heresy - 0 views

  • 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.
Mickle jori

e-Commerce Website Company | e-Commerce Website Development company | e-Commerce Websit... - 0 views

  •  
    karmicksolutions specializes in website development and ecommerce that has established some of the leading brands by enhancing their business with great success. Karmick solutions has provided excellent innovative website development along with internet marketing and website promotions unparalleled over the years.
  •  
    HI ! I FOUND THIS, PLEASE CHECK THIS OUT AND VOICE YOUR OPINION.
ASLI BUGAKAPTAN INCE

Logikit::Framework - 0 views

  •  
    Logikit::Framework (LF for short) is an application development framework for PHP 5. The idea is to let people code much faster by providing a solid and easy-to-use substructure for common tasks. LF deals with most of the time-consuming everyday issues and lets you focus on the logic of your code.
Robin Dale

Steps to Change Root Password in HyperVM - 1 views

  •  
    HyperVM is a very powerful and robust virtualization management software application, which helps you to manage a particular server within a servers cluster. If you forget your root password in HyperVM, it can be reset very easily using few steps shown in this tutorial.
Sarah HL

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

  • 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?
Robin Dale

Installation of PHP PEAR on Linux Server - 1 views

  •  
    The PHP PEAR also known as PHP Extension and Application Repository, is a repository built especially for PHP software code. In this tutorial, you will learn how to install the PHP PEAR on the linux server. Install PEAR allows you to install various extensions without compiling the source packages.
kunshtech

Offshore Laravel Development Company India - 0 views

  •  
    Kunsh Technologies offers a whole suite of Laravel solutions for all kinds of business niches and completely endorse Laravel Web Development to users as it can help to create various applications according their requirement in lesser time and at a lesser cost.
« First ‹ Previous 81 - 98 of 98
Showing 20 items per page