Skip to main content

Home/ PHP Programming/ Group items tagged Many

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Sarah HL

PHP Worst Practices at blog.phpdeveloper.org - 0 views

blog.phpdeveloper.org/?p=173

programming xp bestpractices

shared by Sarah HL on 25 Aug 09 - Cached
  • Beware the Outsiders
  • 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.
  • Unplanification
  • ...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”.
  • The Documentation Wasteland
  • 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.
  • ets you know the “why” instead of just the “how” the code gives you
  • You’d be surprised how often you’ll find yourself referring to it once it’s reliable.
  • Free Your Mind
  • You, as a developer, know that there’s always more than one way to solve a problem.
  • Just like ‘anti patterns’, who are an important read as well, ‘worst practices’ help developers avoid mistakes.
Sarah HL

10 Principles of the PHP Masters | Internet Resources | Cpworld2000.com - 0 views

www.cpworld2000.com/...-principles-of-the-php-masters

shared by Sarah HL on 25 Aug 09 - Cached
  • 1. Use PHP Only When You Need it – Rasmus Lerdorf
  • PHP was created out of a need to solve web development problems
  • 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...
  • 2. Use Many Tables With PHP and MYSQL for Scalability – Matt Mullenweg
  • 3. Never, ever trust your users – Dave Child
  • 4. Invest in PHP Caching – Ben Balbo
  • 5. Speed up PHP Development with an IDE, Templates and Snippets – Chad Kieffer
  • 6. Make Better Use of PHP’s Filter Functions – Joey Sochacki
  • 7. Use a PHP Framework – Josh Sharp
  • 8. Don’t use a PHP Framework – Rasmus Lerdorf
  • 9. Use Batch Processing – Jack D. Herrington
  • 10. Turn on Error Reporting Immediately – David Cummings
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.
  • once you’re into maintenance mode, there are really no excuses. Because you really know what all your X’s and Y’s are
  • I freely admit that this is not really truly TDD
  • 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

Where Has All The PHP Gone? - 0 views

www.samuelfolkes.com/...where-has-all-the-php-gone

programming opinion

shared by Sarah HL on 01 Sep 09 - Cached
  • I was always able to find help with almost anything PHP related that I needed. It wasn’t the ‘cut and paste’ kind of help, it was the ‘detailed explanation’ kind of help.
  • it is becoming increasingly more difficult to learn PHP
  • Beginners nowadays are being hit over the head with grandiose concepts such as ‘dependency injection’ and ‘favouring composition over inheritance’ which really have nothing to do with PHP itself.
  • ...4 more annotations...
  • we now have PHP developers going around developing inferior software
  • We have developers obsessed with micro-optimizations and zombie followers of design patterns when the truth of the matter is that had they just been introduced the language properly in the first place many of these concepts would become like second nature
  • senior members of the PHP community need to, for the sake of our beloved language, shift some of the focus of our discussions and our articles back to PHP. Just pure PHP.
  • I hate PHP frameworks. They do absolutely nothing to aid in the learning of the language and, at the rate that they are going, we’ll soon find that PHP frameworks abstract away PHP itself.
seth kutcher

Computer Repair Services from the Professionals - 1 views

I have been doing digital photography for years and my personal computer is my business partner and has really helped me in numerous ways. My business and hobby has brought me many good things in l...

computer repair services

started by seth kutcher on 09 Sep 11 no follow-up yet
Syntacticsinc SEO

IT Solutions That Really Work - 1 views

I am planning to build up and improve my website for my business and I was thinking of choosing the best IT company that can meet my requirements for my website and optimize it to make it easier fo...

web designing

started by Syntacticsinc SEO on 24 Sep 11 no follow-up yet
baldwinjackson

Configure Virtual Host On Windows 10 - 1 views

www.cloudways.com/...st-on-windows-10-for-wordpress

WordPress VirtualHost Windows10 WebDesign WebDevelopment

shared by baldwinjackson on 09 Nov 17 - No Cached
  • baldwinjackson on 09 Nov 17
     
    Every newbie start their development career on their local machine and then launch their project on live servers. In many instances, the local environment has minimal resources required for development. Most of the developers like to develop a website in a localized environment. Well WordPress host is generally set up on XAMPP/WAMP which is a free virtual hosts which is straightforward task.
kunshtech

Kunsh Technologies - Laravel Application Development Services - 0 views

kunshtech.blogspot.in/...troduction-to-laravel-php.html

development company laravel application

shared by kunshtech on 20 Nov 17 - No Cached
  • kunshtech on 20 Nov 17
     
    As an outstanding & leading Laravel Web Development Company, Kunsh Technologies possesses a skilled team of laravel developers who're perfectly well versed in Laravel web development. With the help of this rapid application development framework, we've helped many small scale & large-scale businesses so far in implementing Laravel web development solutions successfully.
‹ Previous 21 - 28 of 28
Showing 20▼ items per page