Skip to main content

Home/ Tools for web developers/ Group items tagged software

Rss Feed Group items tagged

de Villamil Frédéric

Github: Making Code More Social - O'Reilly Radar - 0 views

  •  
    Github launched less than a year ago, but it's already making an impact on how open-source software is being created. Rails was there from day one, kick-starting the social software repository's traffic. It has taken off though it still doesn't compare to Sourceforge's traffic.
Vernon Fowler

MockFlow: Online Wireframe Tool - 0 views

  •  
    "Super-easy Wireframing Design, collaborate user interface mockups for your software and websites. "
Vernon Fowler

Daring Fireball: How to Create Retina-Caliber Favicons - 0 views

  • I found no other tool that suited my needs.
    • Vernon Fowler
       
      IcoFX may be an alternative.
    • Vernon Fowler
  • iConvertIcons doesn’t do multi-resource ICOs. Neither does Image2Icon.
  • Old (non-retina) favicons are 16 × 16 px; a retina favicon is thus 32 × 32 px.
  • ...1 more annotation...
  • X-Icon Editor is a free web app recommended by Thomas Fuchs in his otherwise excellent Retinafy Your Website flowchart, but the problem I found with it (other than the inherent clunkiness of a web app in general) is that it did awful things to colors
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 - 8 of 8
Showing 20 items per page