Skip to main content

Home/ Tools for web developers/ Group items tagged communication

Rss Feed Group items tagged

de Villamil Frédéric

Designing Typography for the Modern Web | Tips - 1 views

  •  
    As web designers, it is our job to grow with the trends of the Internet. As new technology emerges, it's our position to jump on board and see where it can take us. This includes trends all over the web, typography being a major player. Many designers don't consider type as a field of interest or focus. Ironically, typography is possibly one of the most important parts of our dynamic web. It helps deliver a website's content to users from all over the world and it truly is an art to study. I'll be getting into a few concepts about typography for the modern web. Things haven't changed too much since the previous years of web design, however many new techniques are being utilized and shared amongst the design community.
Vernon Fowler

Flow Patterns: Make Site Flows With Fine Visual Detail - UX Movement - 0 views

  • User flows show how the user interacts with a specific set of pages to complete a task or meet a goal.
  •  
    "Traditional site flows of boxes and arrows aren't detailed enough to paint a clear vision to others. You need visual site flows that show the basics of how a page will look. This gives your team a better idea of what you'll design, so that you can better meet their expectations."
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