BibSLEIGH corpus
BibSLEIGH tags
BibSLEIGH bundles
BibSLEIGH people
Open Knowledge
XHTML 1.0 W3C Rec
CSS 2.1 W3C CanRec
email twitter
Used together with:
not (8)
about (6)
know (4)
user (4)
want (4)

Stem alway$ (all stems)

34 papers:

DATEDATE-2015-VenkataramaniBH #named
SAPPHIRE: an always-on context-aware computer vision system for portable devices (SV, VB, XSH, JL, JL, MP, BP, MS), pp. 1491–1496.
CHICHI-2015-EslamiRVAVKHS #algorithm #quote #reasoning
“I always assumed that I wasn’t really that close to [her]”: Reasoning about Invisible Algorithms in News Feeds (ME, AR, KV, AA, AV, KK, KH, CS), pp. 153–162.
CHICHI-2015-LuL #gesture #mobile #performance
Gesture On: Enabling Always-On Touch Gestures for Fast Mobile Access from the Device Standby Mode (HL, YL), pp. 3355–3364.
CSCWCSCW-2015-WieseMHZ #quote
“You Never Call, You Never Write”: Call and SMS Logs Do Not Always Indicate Tie Strength (JW, JKM, JIH, JZ), pp. 765–774.
CHICHI-2014-FeinbergCB #database #design #interactive #using
Always somewhere, never there: using critical design to understand database interactions (MF, DC, JB), pp. 1941–1950.
CHICHI-2014-LieberBM #concept #programming #visualisation
Addressing misconceptions about code with always-on programming visualizations (TL, JRB, RCM), pp. 2481–2490.
CHICHI-2014-RadleJMR #navigation #performance
Bigger is not always better: display size, performance, and task load during peephole map navigation (RR, HCJ, JM, HR), pp. 4127–4136.
ICSTSAT-2014-BalyoFHB #set
Everything You Always Wanted to Know about Blocked Sets (But Were Afraid to Ask) (TB, AF, MH, AB), pp. 317–332.
HTHT-2013-VigoH #information management
Challenging information foraging theory: screen reader users are not always driven by information scent (MV, SH), pp. 60–68.
CHICHI-2013-SuCWLCC #named #visual notation
NailDisplay: bringing an always available visual display to fingertips (CHS, LWC, CTW, RHL, KYC, BYC), pp. 1461–1464.
Everything you always wanted to know about synchronization but were afraid to ask (TD, RG, VT), pp. 33–48.
Derick Wood: Always in Our Hearts (SY), pp. 1–2.
CIKMCIKM-2011-LangeN #metric #similarity #why
Frequency-aware similarity measures: why Arnold Schwarzenegger is always a duplicate (DL, FN), pp. 243–248.
ICSEICSE-2011-BayneCE #feedback
Always-available static and dynamic feedback (MB, RC, MDE), pp. 521–530.
DATEDATE-2010-Rabaey #energy
Always energy-optimal microscopic wireless systems (JMR), p. 658.
SCAMSCAM-2010-Harman #analysis #source code #why
Why Source Code Analysis and Manipulation Will Always be Important (MH), pp. 7–19.
CHICHI-2010-RicheDM #feedback
Studying always-on electricity feedback in the home (YR, JD, RAM), pp. 1995–1998.
TAPTAP-2010-Ernst #feedback #how #proving #testing
How Tests and Proofs Impede One Another: The Need for Always-On Static and Dynamic Feedback (MDE), pp. 1–2.
HCIIDGD-2009-Gould09a #people #question #usability
Intercultural Usability Surveys: Do People Always Tell “The Truth”? (EWG), pp. 254–258.
ICEISICEIS-SAIC-2008-VladoiuC #community #framework
Framework for Building of a Dynamic User Community (EPH) — Sharing of Context-Aware, Public Interest Information or Knowledge through Always-on Services (MV, ZC), pp. 73–87.
Line-End Shortening is Not Always a Failure (PG, ABK, YK, SS, DS), pp. 270–271.
HCIHCI-MIE-2007-YamaguchiSS #reliability #streaming #video
Reliable Partner System Always Providing Users with Companionship Through Video Streaming (TY, KS, HS), pp. 1010–1018.
KRKR-2006-Rector #information management #representation
Users Are Always Right ... Even When They Are Wrong: Making Knowledge Representation Useful and Usable (ALR), p. 4.
ICSEICSE-2005-MaurerM #agile #what
What you always wanted to know about agile methods but did not dare to ask (FM, GM), pp. 731–732.
Set-Sharing Is Not Always Redundant for Pair-Sharing (FB, MJGdlB), pp. 117–131.
ICPRICPR-v4-2004-Cheatle #smarttech #video
Media Content and Type Selection from Always-on Wearable Video (PC), pp. 979–982.
SIGIRSIGIR-2002-DumaisBBLN #question #web
Web question answering: is more always better? (STD, MB, EB, JJL, AYN), pp. 291–298.
HTHT-2000-Calvi #hypermedia #question
Text and hypertext: always a binary relationship? (LC), pp. 218–219.
STOCSTOC-1997-GoreJ #process
The Swendsen-Wang Process Does Not Always Mix Rapidly (VG, MJ), pp. 674–681.
AdaTRI-Ada-1997-Lawlis #ada #question
Is the Answer Always Ada? (PKL), pp. 297–302.
AdaEuropeAdaEurope-1994-WardS #exclamation #object-oriented
Object Orientation is not Always Best! (RW, JS), pp. 104–110.
AdaTRI-Ada-1994-BarbaschE #ada #debugging
Always One More Bug: Applying AdaWise to Improve Ada Code (CB, DE), pp. 228–235.
CADECADE-1986-Eisinger #graph #what
What You Always Wanted to Know About Clause Graph Resolution (NE), pp. 316–336.
ICSEICSE-1976-MannaW #correctness #proving
Is “Sometime” Sometimes Better Than “Always”? Intermittent Assertions in Proving Program Correctness (ZM, RJW), pp. 32–39.

Bibliography of Software Language Engineering in Generated Hypertext (BibSLEIGH) is created and maintained by Dr. Vadim Zaytsev.
Hosted as a part of SLEBOK on GitHub.