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:
time (5)
end (3)
not (3)
requir (3)
sometim (3)

Stem never$ (all stems)

23 papers:

ITiCSEITiCSE-2015-Dickson #development #education #game studies #using
Using Unity to Teach Game Development: When You’ve Never Written a Game (PED), pp. 75–80.
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.
HTHT-2014-SubercazeG #named #recognition
FoP: never-ending face recognition and data lifting (JS, CG), pp. 321–323.
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-RogersPBVMV #people
Never too old: engaging retired people inventing the future with MaKey MaKey (YR, JP, MB, KV, GM, FV), pp. 3913–3922.
ECIRECIR-2014-Koolen #exclamation #ll #quote
“User Reviews in the Search Index? That’ll Never Work!” (MK), pp. 323–334.
KDDKDD-2013-HaoCZ0RK #learning #towards
Towards never-ending learning from time series streams (YH, YC, JZ, BH, TR, EJK), pp. 874–882.
ITiCSEITiCSE-2012-Rabin #student
Never too early to begin: computer science for high-school students (MOR), p. 1.
CHICHI-2012-DuganGMVJLCDB #enterprise #exclamation #quote
“I’d never get out of this !?$%# office”: redesigning time management for the enterprise (CD, WG, MJM, ANV, KJ, SL, LTC, EMD, BB), pp. 1755–1764.
DLTDLT-2011-RodaroS #automaton #problem
Never Minimal Automata and the Rainbow Bipartite Subgraph Problem (ER, PVS), pp. 374–385.
CSCWCSCW-2011-BrubakerH #empirical #online #quote
“We will never forget you [online]”: an empirical investigation of post-mortem myspace comments (JRB, GRH), pp. 123–132.
HCIIDGD-2011-ZhangM #trust
Once Broken, Never Fixed? The Impact of Culture and Medium on Repairing Trust in CMC (QZ, NM), pp. 341–350.
ICMLICML-2011-LiZ #towards
Towards Making Unlabeled Data Never Hurt (YFL, ZHZ), pp. 1081–1088.
RERE-2011-Waldmann #agile #constraints #development #requirements #what
There’s never enough time: Doing requirements under resource constraints, and what requirements engineering can learn from agile development (BW), pp. 301–305.
If You Want Innovative RE, Never Ask the Users; A Formal Debate (KR, NAMM, MG), p. 388.
ICSMEICSM-2007-OlivetoAMH #challenge #traceability
Software Artefact Traceability: the Never-Ending Challenge (RO, GA, AM, JHH), pp. 485–488.
Some wells never dry (JJvB), p. 465.
DACDAC-2002-BrunoliHJKMM #question
Analog intellectual property: now? Or never? (MB, MH, FJ, RK, RM, AJM), pp. 181–182.
POPLPOPL-1997-PlezbertC #question
Is “Just in Time” = “Better Late than Never”? (MPP, RC), pp. 120–131.
RERE-1993-LoucopoulosPMMLZ #object-oriented #requirements
I never knew my requirements were object-oriented until I talked to my analyst (PL, CP, SJM, JAM, L, LZ), pp. 226–230.
CADECADE-1988-PaseK #summary
m-NEVER System Summary (BP, SK), pp. 738–739.
POPLPOPL-1983-EmersonH #branch #linear
“Sometimes” and “Not Never” Revisited: On Branching Versus Linear Time (EAE, JYH), pp. 127–140.
POPLPOPL-1980-Lamport #logic #quote #source code
“Sometime” is Sometimes “Not Never” — On the Temporal Logic of Programs (LL), pp. 174–185.

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.