Skip to main content

Home/ Tools for web developers/ Group items tagged build

Rss Feed Group items tagged

de Villamil Frédéric

Multiple File Upload Support in Safari 4 Public Beta - Observation Point - 0 views

  •  
    Introduced in the HTML 5 specification, the multiple attribute on file inputs (i.e. ) will allow for multiple files to be selected for upload. I had been using the WebKit nightlies and watching for this feature to be enabled in the default builds, but the Safari 4 beta is the first version of Safari that I've seen support this. The original commit to WebKit that added this support was 37863.
de Villamil Frédéric

Code: Flickr Developer Blog » Building Fast Client-side Searches - 0 views

  •  
    Yesterday we released a new people selector widget (which we've been calling Bo Selecta internally). This widget downloads a list of all of your contacts, in JavaScript, in under 200ms (this is true even for members with 10,000+ contacts). In order to get this level of performance, we had to completely rethink how we send data from the server to the client.
de Villamil Frédéric

When Clients Take Too Much Design Control | Build Internet! - 0 views

  •  
    Have you ever dealt with a client who suddenly flipped on "design mode" mid-project? The expectation is that you are an expert, and you act as a filter between the client and a (successful) finished product. Web design is more than just coding a client's vision. You've spent the time honing skills. Now let's reclaim your artistic license while keeping professional.
Sarah HL

JUnit FAQ - 0 views

  • They effectively communicate in an executable format how to use the software. They also prevent tendencies to over-build the system based on speculation. When all the tests pass, you know you're done!
  • Test-driven development is a lot more fun than writing tests after the code seems to be working
  • Do I have to write a test for everything? No, just test everything that could reasonably break.
  • ...6 more annotations...
  • If something is difficult to test, it's usually an opportunity for a design improvement.
  • Frequent testing gives you confidence that your changes didn't break anything and generally lowers the stress of programming in the dark.
  • Run all your unit tests as often as possible, ideally every time the code is changed
  • For larger systems, you may just run specific test suites that are relevant to the code you're working on.
  • write a failing test that exposes the defect. When the test passes, you know the defect is fixed!
  • Don't forget to use this as a learning opportunity. Perhaps the defect could have been prevented by being more aggressive about testing everything that could reasonably break.
1 - 7 of 7
Showing 20 items per page