InfoQ Homepage Design Guideline Content on InfoQ
-
How to Create a UI That's Both Robust and User Friendly
The key challenge in building UIs is balancing ease of use and maintainability, with scale and complexity. It requires thoughtful component design and an understanding of common usage paths to create a UI that's both robust and user-friendly. Automation can be a game-changer when it comes to improving efficiency and consistency in your codebase.
-
Accessibility Testing: Convincing Your Product Owner
Accessibility testing is just the right thing to do; the internet and e-services are a place for people to feel and interact equally, so our software should not exclude people, argued Martin Tiitmaa at TestCon Europe 2019.
-
PayPal’s API Style Guide and Patterns
PayPal has created their platform as services connected to each other through RESTful APIs. They have developed guidelines and design patterns for creating and using these APIs, making them publicly available for other developers to get inspiration for their own projects.
-
NIST Guidelines Require Second Auth Factor When Using Biometrics
NIST has released a public draft of new Digital Identity Guidelines, described as “a significant update from past revisions.” The guidelines describe acceptable use of multi-factor authentication (MFA). Furthermore, when using biometric data as one authentication factor, it must be combined with something you have, and not something you know, such as a password.
-
Refactoring and Code Smells – A Journey Toward Cleaner Code
Refactoring helps to move towards cleaner code that is easier to understand and maintain. It takes practice and experience to recognise code smells: symptoms of bad design which indicate deeper problems in the code. Tools can be helpful to refactor in small steps and prevent breaking the code.
-
Microsoft REST API Guidelines Are Not RESTful
Microsoft has published their guidance for creating “RESTful” APIs. Roy Fielding calls them HTTP APIs that have little to do with REST.
-
What Programmers Can Do to Write Better Code
To write better code, programmers have to apply design fundamentals and read existing code, says Martin Thompson, a Java Champion and high-performance-computing specialist. InfoQ interviewed him after his Engineering You talk at QCon London 2016 about the challenges that the software industry is facing and what programmers can do to deal with those challenges and become better software engineers.
-
Bad Practices Building Microservices
When adopting a microservices architecture, using an external architect to create the design of a service instead of helping a team make their own decisions about design and implementation is one of several traps or bad practices that Vladimir Khorikov has experienced in his work.
-
Google’s Guidelines for Creating and Publishing Android Apps
Google has published “The Secrets to App Success on Google Play”, a playbook meant to educate Android developers on creating applications that have greater chances to be appreciated by users, downloaded by more people and obtain better results.
-
Google Introduces Material Design at Google I/O
Google is introducing Material Design, a visual language incorporating design principles for user interfaces spanning a multitude of devices from wearables to smartphones, tablets, desktops and TVs. Material Design attempts to provide fluid motion on tactile surfaces, but mouse and keyboard-based devices are also considered.
-
Google Web Fundamentals and Web Starter Kit
Google has published a number of guidelines and boilerplate code for cross-platform responsive website design.
-
Guidelines for Responsive Website Design
This article includes several guidelines for creating websites that scale for different screen sizes and form factors.
-
Becoming SOLID in C#
Brannon B. King, a software developer working for Autonomous Solutions Inc., has published an article entitled Dangers of Violating SOLID Principles in C# in MSDN Magazine, May 2014. The author outlines some of the mistakes developers can make in their C# code, breaking the SOLID principles and leading to code that is more difficult to extend or maintain.
-
Dependency Principles for SOA
Earlier this year Ganesh Prasad discussed the concept of thinking of SOA as "Dependency-Oriented Thinking". Based upon further interactions and involvement with real-world use cases, Ganesh has come up with a dozen principles which he believes can help successful SOA.
-
Open-Closed Principle in SOLID Object Orientation Rules Challenged
The Open-Closed Principle, OCP, part of the object-orientation SOLID principles, was recently criticised by Jon Skeet and Robert Ashton who both believes the principle is doing more harm than good. Robert C. Martin, who identified the principles in the early 2000s, however, defends the principle, arguing that you have to look at the full description, not just the short definition.