The links, tools and tips our engineers and designers share with each other, one “today I learned” at a time.
ukhomeoffice.github.io
Designing accessible services: best design practices for users from these areas: low vision, D/deaf and hard of hearing, dyslexia, motor disabilities, users on the autistic spectrum and users of screen readers
Evilanne Brandão
Tech Insights· ukhomeoffice.github.io
Designing accessible services: best design practices for users from these areas: low vision, D/deaf and hard of hearing, dyslexia, motor disabilities, users on the autistic spectrum and users of screen readers
Shared by
github.com
Dennys Azevedo
Tech Insights· github.com
Shared by
bishopfox.com
See why you should never use pixelation for redacting text and why it is a surefire way to get your data leaked. Learn from security researcher Dan Petro.
Flavio Juvenal
Tech Insights· bishopfox.com
From bishopfox.com
See why you should never use pixelation for redacting text and why it is a surefire way to get your data leaked. Learn from security researcher Dan Petro.
Shared by
Tech Insights· konghq.com
Shared by
nngroup.com
Nielsen’s 10 usability heuristics can be used to analyze the UX of applications that support domain-specific, complex workflows.
Fernanda Magalhães
Tech Insights· nngroup.com
From nngroup.com
Nielsen’s 10 usability heuristics can be used to analyze the UX of applications that support domain-specific, complex workflows.
Shared by
Tech Insights· tameflow.com
Shared by
The original link on tameflow.com is no longer available.
Look for it on the Wayback Machine
Tech Insights· astralcodexten.substack.com
Shared by
Tech Insights· leaddev.com
Shared by
Tech Insights· cloud.google.com
Shared by
thediff.co
Plus! The Carbon Rally; The Bridge; Housing and Rates; Full Stack Media; Buying Out Contracts; Diff Jobs
Rebeca Sarai
Tech Insights· thediff.co
From thediff.co
Plus! The Carbon Rally; The Bridge; Housing and Rates; Full Stack Media; Buying Out Contracts; Diff Jobs
Shared by
Tech Insights· figma.com
Shared by
wiki.c2.com
If one is seeing a lot of Accidental Difficulty caused by boiler-plate code or hand-written translations to and from tools and interfaces, something in the system is likely Simply Simplistic. Simply Simplistic models and services and interfaces are too simple, failing to capture the Essential Difficulty, and thus force the Essential Difficulty to be duplicated by each user, increasing the Accidental Difficulty with each duplication. Sometimes you can extract this Accidental Difficulty into a library or helper Once And Only Once. Sometimes you cannot. If you cannot, your language tool may be Simply Simplistic itself, subject to the Missing Feature Smell.
Flavio Juvenal
Tech Insights· wiki.c2.com
If one is seeing a lot of Accidental Difficulty caused by boiler-plate code or hand-written translations to and from tools and interfaces, something in the system is likely Simply Simplistic. Simply Simplistic models and services and interfaces are too simple, failing to capture the Essential Difficulty, and thus force the Essential Difficulty to be duplicated by each user, increasing the Accidental Difficulty with each duplication. Sometimes you can extract this Accidental Difficulty into a library or helper Once And Only Once. Sometimes you cannot. If you cannot, your language tool may be Simply Simplistic itself, subject to the Missing Feature Smell.
Shared by
wiki.c2.com
Simplistic protocols and models and language features can end up becoming complexity multipliers because the complexity is duplicated by each and every user of the model or protocol. They are also effort multipliers. Fortunately, one can sometimes solve this problem by wrapping or refactoring the protocol or model or language feature within a library to utilize it, thus capturing the Essential Complexity into the library and thus creating the feature/language/model that should have existed in the first place.
Flavio Juvenal
Tech Insights· wiki.c2.com
Simplistic protocols and models and language features can end up becoming complexity multipliers because the complexity is duplicated by each and every user of the model or protocol. They are also effort multipliers. Fortunately, one can sometimes solve this problem by wrapping or refactoring the protocol or model or language feature within a library to utilize it, thus capturing the Essential Complexity into the library and thus creating the feature/language/model that should have existed in the first place.
Shared by
hotjar.com
Use this collection of 12 useful templates, checklists, and scripts to follow to make your usability testing plan as effective as possible.
Fernanda Magalhães
Tech Insights· hotjar.com
From hotjar.com
Use this collection of 12 useful templates, checklists, and scripts to follow to make your usability testing plan as effective as possible.
Shared by
Tech Insights· figma.com
Shared by
Book a call
Tell us about your product and the problem in front of you. We’ll bring what we’ve learned on real projects.
Tell us about your product, and we’ll bring what we’ve learned.
Still prefer the good old email? Contact us
