Skip to main content

Home/ PHP Programming/ Group items tagged Words

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
spymek soft

Tap Tap Words - 0 views

itunes.apple.com/...id506298967

Tap Words

shared by spymek soft on 02 Aug 12 - No Cached
  • spymek soft on 02 Aug 12
     
    A simple, addictive and informative game where you can learn words with the meaning and improve your vocabulary.
  • spymek soft on 02 Aug 12
     
    A simple, addictive and informative game where you can learn words with the meaning and improve your vocabulary.
Maggie Wolfe Riley

PHP Top 5 - OWASP - 3 views

www.owasp.org/PHP_Top_5

webdesign php mysql security code

shared by Maggie Wolfe Riley on 06 Jul 10 - Cached
  • Maggie Wolfe Riley on 06 Jul 10
     
    PHP is a very popular language. Every PHP developer and hoster should understand the primary attack vectors being used by attackers against PHP applications. This article is the underlying research behind the SANS Top 20 2005's PHP section. The methodology used in the preparation of this article is to review all Bugtraq postings containing the word "PHP" and categorize each unique flaw. The author analyzed the most popular flaws / attacks, and researched prevention techniques, resulting in this article.
qualitypoint Tech

Launching our Affiliate Program - Hurry to get 90% affiliate commission - 0 views

qualitypoint.blogspot.com/...r-affiliate-program-hurry.html

affiliate

shared by qualitypoint Tech on 15 Jul 10 - Cached
  • qualitypoint Tech on 15 Jul 10
     
    Affiliate - This word gives some negative impression to most of us.But basically Affiliate program is an excellent marketing tool. Especially it will be very helpful for marketing digital products.\nhttp://qualitypointtech.net/affiliate/index.php\n
Jungle Jar

JungleJar | Featured Web Application: PHPanywhere.net - 0 views

www.junglejar.com/...php-web-application

PHP web development php development web applications web tools

shared by Jungle Jar on 09 May 09 - Cached
  • Jungle Jar on 09 May 09
     
    This is an extremely cool and useful web application, and if it hasn't been thought of before, I'm absolutely shocked, because it makes so much sense. Essentially, PHPanywhere is a web based free Integrated Development Environment or IDE for the PHP language. In other words it is a web based application that provides PHP developers a PHP code editor that mocks a desktop application, and it does so very well.
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.
sally pearson

Renewing My Remote Computer Help Subscription - 3 views

My friend recommended ComputerHelpFastOnline - an emerging team of computer savvy tech support professionals - to provide computer help for my business. Thank God I heeded his words because since I...

computer help

started by sally pearson on 06 Jun 11 no follow-up yet
Justin Pierce

The Most Excellent Bookkeeping Services - 1 views

When I was still single, I had all the time to manage my gift shop. But when I got married a year ago, I found it really hard to give equal attention to my business as well as to my roles as a wife...

started by Justin Pierce on 14 Feb 13 no follow-up yet
Sarah HL

The 7 Rules for Writing World Class Technical Documentation - Developer.com - 1 views

www.developer.com/...article.htm

shared by Sarah HL on 30 Nov 09 - No Cached
  • Dry sucks Before you start, be clear about what you want your reader to do after you end Write to a well formed outline, always Avoid ambiguous pronouns clarity = illustrations + words When dealing with concepts... logical illustration and example Embrace revision
1 - 9 of 9
Showing 20▼ items per page