default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDGeorge V. Neville-Neil
Person information
- affiliation: Neville-Neil Consulting, New York City, NY, USA
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
showing all ?? records
2020 – today
- 2024
[j239]George V. Neville-Neil
:
Dear Diary. Commun. ACM 67(2): 27-28 (2024)- [j238]George V. Neville-Neil:
Is There Another System? Commun. ACM 67(4): 29-30 (2024) - [j237]George V. Neville-Neil:
Software Drift. Commun. ACM 67(6): 33-34 (2024) - [j236]George V. Neville-Neil:
Structuring Success. Commun. ACM 67(8): 33-34 (2024) - [j235]George V. Neville-Neil:
Repeat, Reproduce, Replicate. Commun. ACM 67(10): 29-30 (2024) - [j234]George V. Neville-Neil:
Is There Another System?: Computer science is the study of what can be automated. ACM Queue 21(6): 12-15 (2024) - [j233]George V. Neville-Neil:
Software Drift: Open source forking. ACM Queue 22(1): 17-22 (2024) - [j232]George V. Neville-Neil:
Structuring Success: The problem with software structure is people don't really learn it until they really need it. ACM Queue 22(2) (2024) - [j231]George V. Neville-Neil:
Repeat, Reproduce, Replicate: The pressure to publish versus the will to defend scientific claims. ACM Queue 22(3): 20 (2024) - 2023
- [j230]George V. Neville-Neil:
The Elephant in the Room. Commun. ACM 66(2): 30-31 (2023) - [j229]George V. Neville-Neil:
All Sliders to the Right. Commun. ACM 66(4): 24-25 (2023) - [j228]Maya Kaczorowski, Falcon Momot, George V. Neville-Neil, Chris McCubbin:
OSS Supply-Chain Security: What Will It Take? Commun. ACM 66(4): 48-54 (2023) - [j227]George V. Neville-Neil:
The Parchment Path? Commun. ACM 66(6): 31-32 (2023) - [j226]George V. Neville-Neil:
The Human Touch. Commun. ACM 66(8): 27-28 (2023) - [j225]George V. Neville-Neil:
Stone Knives and Bear Skins. Commun. ACM 66(10): 27-29 (2023) - [j224]George V. Neville-Neil:
Halfway Around the World. Commun. ACM 66(12): 27-28 (2023) - [j223]Ethan L. Miller, George V. Neville-Neil, Achilles Benetopoulos, Pankaj Mehra, Daniel Bittman:
Pointers in Far Memory. Commun. ACM 66(12): 40-45 (2023) - [j222]George V. Neville-Neil:
The Parchment Path?: Is there ever a time when learning is not of value - for its own sake? ACM Queue 21(1): 5-11 (2023) - [j221]George V. Neville-Neil:
The Human Touch: There is no substitute for good, direct, honest training. ACM Queue 21(2): 9-13 (2023) - [j220]George V. Neville-Neil:
Stone Knives and Bear Skins. ACM Queue 21(3): 29-35 (2023) - [j219]Ethan L. Miller, Achilles Benetopoulos, George V. Neville-Neil, Pankaj Mehra, Daniel Bittman:
Pointers in Far Memory: A rethink of how data and computations should be organized. ACM Queue 21(3): 75-93 (2023) - [j218]George V. Neville-Neil:
Halfway Around the World: Learn the language, meet the people, eat the food. ACM Queue 21(4): 18-22 (2023) - [j217]George V. Neville-Neil:
Dear Diary: On keeping a laboratory notebook. ACM Queue 21(5): 22-28 (2023) - 2022
- [j216]George V. Neville-Neil:
I unplugged what? Commun. ACM 65(2): 23-24 (2022) - [j215]George V. Neville-Neil:
Getting off the mad path. Commun. ACM 65(4): 25-26 (2022) - [j214]George V. Neville-Neil:
The planning and care of data. Commun. ACM 65(6): 36-37 (2022) - [j213]George V. Neville-Neil:
When should a black box be transparent? Commun. ACM 65(8): 23-24 (2022) - [j212]George V. Neville-Neil:
Securing the company jewels. Commun. ACM 65(10): 25-26 (2022) - [j211]George V. Neville-Neil:
The four horsemen of an ailing software project. Commun. ACM 65(12): 22-23 (2022) - [j210]George V. Neville-Neil:
The Planning and Care of Data: Rearranging buckets for no good reason. ACM Queue 20(1): 4-9 (2022) - [j209]George V. Neville-Neil:
When Should a Black Box Be Transparent?: When is a replacement not a replacement? ACM Queue 20(2): 11-15 (2022) - [j208]George V. Neville-Neil:
Securing the Company Jewels: GitHub and runbook security. ACM Queue 20(3): 14-17 (2022) - [j207]George V. Neville-Neil:
The Four Horsemen of an Ailing Software Project: Don't let the pale rider catch you with an exception. ACM Queue 20(4): 11-15 (2022) - [j206]George V. Neville-Neil:
The Elephant in the Room: It's time to get the POSIX elephant off our necks. ACM Queue 20(5): 14-19 (2022) - [j205]Maya Kaczorowski, Falcon Momot, George V. Neville-Neil, Chris McCubbin:
OSS Supply-chain Security: What Will It Take? ACM Queue 20(5): 86-102 (2022) - [j204]George V. Neville-Neil:
All Sliders to the Right: Hardware Overkill. ACM Queue 20(6): 4-8 (2022) - 2021
- [j203]George V. Neville-Neil:
Kabin fever. Commun. ACM 64(2): 26-27 (2021) - [j202]George V. Neville-Neil:
The non-psychopath's guide to managing an open source project. Commun. ACM 64(4): 25-27 (2021) - [j201]George V. Neville-Neil:
Aversion to versions. Commun. ACM 64(6): 31 (2021) - [j200]George V. Neville-Neil:
In praise of the disassembler. Commun. ACM 64(8): 30-31 (2021) - [j199]Michael Gardiner, Alexander Truskovsky, George V. Neville-Neil, Atefeh Mashatan:
Quantum-safe trust for vehicles: the race is already on. Commun. ACM 64(9): 54-61 (2021) - [j198]George V. Neville-Neil:
Divide and conquer. Commun. ACM 64(10): 25 (2021) - [j197]George V. Neville-Neil:
Patent absurdity. Commun. ACM 64(12): 39 (2021) - [j196]George V. Neville-Neil:
Aversion to Versions: Resolving code-dependency issues. ACM Queue 19(1): 16-19 (2021) - [j195]George V. Neville-Neil:
In Praise of the Disassembler: There's much to be learned from the lower-level details of hardware. ACM Queue 19(2): 21-28 (2021) - [j194]Michael Gardiner, Alexander Truskovsky, George V. Neville-Neil, Atefeh Mashatan:
Quantum-safe Trust for Vehicles: The race is already on. ACM Queue 19(2): 93-115 (2021) - [j193]George V. Neville-Neil:
Divide and Conquer: The use and limits of bisection. ACM Queue 19(3): 37-39 (2021) - [j192]George V. Neville-Neil:
I Unplugged What?: The lessons here are broader than just a simple "Don't do that.". ACM Queue 19(5): 22-25 (2021) - [j191]George V. Neville-Neil:
Getting Off the Mad Path: Debuggers and assertions. ACM Queue 19(6): 18-21 (2021) - 2020
- [j190]George V. Neville-Neil:
Numbers are for computers, strings are for humans. Commun. ACM 63(2): 29-30 (2020) - [j189]George V. Neville-Neil:
Master of tickets. Commun. ACM 63(4): 28-29 (2020) - [j188]George V. Neville-Neil:
Kode vicious plays in traffic. Commun. ACM 63(6): 25-26 (2020) - [j187]George V. Neville-Neil:
Broken hearts and coffee mugs. Commun. ACM 63(8): 22-23 (2020) - [j186]George V. Neville-Neil:
Sanity vs. invisible markings. Commun. ACM 63(10): 28-29 (2020) - [j185]George V. Neville-Neil:
Removing kode. Commun. ACM 63(12): 29 (2020) - [j184]George V. Neville-Neil:
Kode Vicious Plays in Traffic. ACM Queue 18(1): 33-36 (2020) - [j183]George V. Neville-Neil:
Broken Hearts and Coffee Mugs. ACM Queue 18(2): 19-24 (2020) - [j182]George V. Neville-Neil:
Sanity vs. Invisible Markings: Tabs vs. spaces. ACM Queue 18(3): 39-42 (2020) - [j181]George V. Neville-Neil:
Removing Kode: Dead functions and dead features. ACM Queue 18(4): 21-25 (2020) - [j180]George V. Neville-Neil:
Kabin Fever: KV's guidelines for KFH (koding from home). ACM Queue 18(5): 35-40 (2020) - [j179]George V. Neville-Neil:
The Non-psychopath's Guide to Managing an Open-source Project: Respect your staff, learn from others, and know when to let go. ACM Queue 18(6): 30-36 (2020)
2010 – 2019
- 2019
- [j178]George V. Neville-Neil:
Writing a test plan. Commun. ACM 62(2): 27 (2019) - [j177]George V. Neville-Neil:
Know your algorithms. Commun. ACM 62(4): 22 (2019) - [j176]George V. Neville-Neil:
MUST and MUST NOT. Commun. ACM 62(8): 30-31 (2019) - [j175]George V. Neville-Neil:
What is a chief security officer good for? Commun. ACM 62(10): 26-27 (2019) - [j174]George V. Neville-Neil:
Koding academies. Commun. ACM 62(12): 25 (2019) - [j173]George V. Neville-Neil:
The Worst Idea of All Time. ACM Queue 17(1): 30 (2019) - [j172]George V. Neville-Neil:
MUST and MUST NOT. ACM Queue 17(2): 70 (2019) - [j171]George V. Neville-Neil:
What is a CSO Good For? ACM Queue 17(3): 60 (2019) - [j170]George V. Neville-Neil:
Koding Academies. ACM Queue 17(4): 20 (2019) - [j169]George V. Neville-Neil:
Numbers Are for Computers, Strings Are for Humans. ACM Queue 17(5): 34-38 (2019) - [j168]George V. Neville-Neil:
Master of Tickets. ACM Queue 17(6): 22-25 (2019) - 2018
- [j167]George V. Neville-Neil:
Reducing the attack surface. Commun. ACM 61(2): 27-28 (2018) - [j166]George V. Neville-Neil:
Popping kernels. Commun. ACM 61(4): 23-24 (2018) - [j165]George V. Neville-Neil:
Watchdogs vs. snowflakes. Commun. ACM 61(6): 28-29 (2018) - [j164]George V. Neville-Neil:
Every silver lining has a cloud. Commun. ACM 61(8): 29-30 (2018) - [j163]George V. Neville-Neil:
The obscene coupling known as spaghetti code. Commun. ACM 61(10): 27-28 (2018) - [j162]George V. Neville-Neil:
A chance gardener. Commun. ACM 61(12): 28-29 (2018) - [j161]George V. Neville-Neil:
Every Silver Lining Has a Cloud. ACM Queue 16(2): 20 (2018) - [j160]George V. Neville-Neil:
The Obscene Coupling Known as Spaghetti Code. ACM Queue 16(3): 70 (2018) - [j159]George V. Neville-Neil:
A Chance Gardener. ACM Queue 16(4): 50 (2018) - [j158]George V. Neville-Neil:
Writing a Test Plan. ACM Queue 16(5): 40 (2018) - [j157]George V. Neville-Neil:
Know Your Algorithms. ACM Queue 16(6): 40 (2018) - 2017
- [j156]George V. Neville-Neil:
The unholy trinity of software development. Commun. ACM 60(2): 34-36 (2017) - [j155]George V. Neville-Neil:
The chess player who couldn't pass the salt. Commun. ACM 60(4): 24-25 (2017) - [j154]George V. Neville-Neil:
Forced exception handling. Commun. ACM 60(6): 31-32 (2017) - [j153]George V. Neville-Neil:
The observer effect. Commun. ACM 60(8): 29-30 (2017) - [j152]George V. Neville-Neil:
IoT: the internet of terror. Commun. ACM 60(10): 36-37 (2017) - [j151]George V. Neville-Neil:
Cold, hard cache. Commun. ACM 60(12): 27-28 (2017) - [j150]George V. Neville-Neil:
Forced Exception-Handling. ACM Queue 15(1): 40 (2017) - [j149]George V. Neville-Neil:
The Observer Effect. ACM Queue 15(2): 10 (2017) - [j148]George V. Neville-Neil:
IoT: The Internet of Terror. ACM Queue 15(3): 10 (2017) - [j147]George V. Neville-Neil:
Cold, Hard Cache. ACM Queue 15(4): 10 (2017) - [j146]George V. Neville-Neil:
Reducing the Attack Surface. ACM Queue 15(5): 40 (2017) - [j145]George V. Neville-Neil:
Popping Kernels. ACM Queue 15(6): 20 (2017) - [j144]George V. Neville-Neil, Robert N. M. Watson:
Teaching Operating Systems with FreeBSD through Tracing, Analysis, and Experimentation. login Usenix Mag. 42(1) (2017) - [c1]Graeme Jenkinson, Lucian Carata, Thomas Bytheway, Ripduman Sohan, Robert N. M. Watson, Jonathan Anderson, Brian J. Kidney, Amanda Strnad, Arun Thomas, George V. Neville-Neil:
Applying Provenance in APT Monitoring and Analysis: Practical Challenges for Scalable, Efficient and Trustworthy Distributed Provenance. TaPP 2017 - 2016
- [j143]George V. Neville-Neil:
Time is an illusion lunchtime doubly so. Commun. ACM 59(1): 50-55 (2016) - [j142]George V. Neville-Neil:
Code hoarding. Commun. ACM 59(2): 35-36 (2016) - [j141]George V. Neville-Neil:
GNL is not Linux. Commun. ACM 59(4): 31-32 (2016) - [j140]George V. Neville-Neil:
What are you trying to pull? Commun. ACM 59(6): 26-27 (2016) - [j139]George V. Neville-Neil:
Chilling the messenger. Commun. ACM 59(8): 28-29 (2016) - [j138]George V. Neville-Neil:
Cloud calipers. Commun. ACM 59(10): 24-25 (2016) - [j137]George V. Neville-Neil:
GNL is Not Linux. ACM Queue 14(1): 40 (2016) - [j136]George V. Neville-Neil:
What Are You Trying to Pull? ACM Queue 14(2): 20 (2016) - [j135]George V. Neville-Neil:
Chilling the Messenger. ACM Queue 14(3): 20 (2016) - [j134]George V. Neville-Neil:
Cloud Calipers. ACM Queue 14(4): 30 (2016) - [j133]George V. Neville-Neil:
The Unholy Trinity of Software Development. ACM Queue 14(5): 12-19 (2016) - [j132]George V. Neville-Neil:
The Chess Player who Couldn't Pass the Salt. ACM Queue 14(6): 14-18 (2016) - 2015
- [j131]George V. Neville-Neil:
Too big to fail. Commun. ACM 58(2): 37-39 (2015) - [j130]George V. Neville-Neil:
Raw networking. Commun. ACM 58(4): 30-32 (2015) - [j129]George V. Neville-Neil:
Lazarus code. Commun. ACM 58(6): 32-33 (2015) - [j128]George V. Neville-Neil:
Hickory dickory doc. Commun. ACM 58(8): 27-28 (2015) - [j127]George V. Neville-Neil:
Storming the cubicle. Commun. ACM 58(10): 29-31 (2015) - [j126]George V. Neville-Neil:
Pickled patches. Commun. ACM 58(12): 30-32 (2015) - [j125]George V. Neville-Neil:
Raw Networking. ACM Queue 13(2): 20-22 (2015) - [j124]George V. Neville-Neil:
Lazarus Code. ACM Queue 13(5): 10 (2015) - [j123]George V. Neville-Neil:
Hickory Dickory Doc. ACM Queue 13(6): 10 (2015) - [j122]George V. Neville-Neil, Steve Bourne:
Still Finding the Right Questions. ACM Queue 13(8): 10 (2015) - [j121]George V. Neville-Neil:
Pickled Patches. ACM Queue 13(8): 90 (2015) - [j120]George V. Neville-Neil:
Time is an Illusion. ACM Queue 13(9): 30 (2015) - [j119]George V. Neville-Neil:
Code Hoarding. ACM Queue 13(9): 90 (2015) - 2014
- [j118]George V. Neville-Neil:
Bugs and bragging rights. Commun. ACM 57(2): 36-37 (2014) - [j117]George V. Neville-Neil:
This is the foo field. Commun. ACM 57(4): 30-31 (2014) - [j116]George V. Neville-Neil:
The logic of logging. Commun. ACM 57(6): 37-38 (2014) - [j115]George V. Neville-Neil:
Forked over. Commun. ACM 57(8): 31-32 (2014) - [j114]George V. Neville-Neil:
Outsourcing responsibility. Commun. ACM 57(10): 28-29 (2014) - [j113]George V. Neville-Neil:
Port squatting. Commun. ACM 57(12): 31-32 (2014) - [j112]George V. Neville-Neil:
Forked Over. ACM Queue 12(4): 10-12 (2014) - [j111]George V. Neville-Neil:
Outsourcing Responsibility. ACM Queue 12(6): 20 (2014) - [j110]George V. Neville-Neil:
Port Squatting. ACM Queue 12(9): 10-12 (2014) - [j109]George V. Neville-Neil:
Too Big to Fail. ACM Queue 12(11): 10-12 (2014) - 2013
- [j108]George V. Neville-Neil:
Divided by division. Commun. ACM 56(2): 26-27 (2013) - [j107]Stephen R. Bourne, George V. Neville-Neil:
Developing tools and resources for those in practice. Commun. ACM 56(4): 5 (2013) - [j106]George V. Neville-Neil:
Code abuse. Commun. ACM 56(4): 33-34 (2013) - [j105]George V. Neville-Neil:
Swamped by automation. Commun. ACM 56(6): 33-34 (2013) - [j104]George V. Neville-Neil:
Cherry-picking and the scientific method. Commun. ACM 56(8): 32-33 (2013) - [j103]George V. Neville-Neil:
The naming of hosts is a difficult matter. Commun. ACM 56(10): 33-34 (2013) - [j102]George V. Neville-Neil:
A lesson in resource management. Commun. ACM 56(12): 32-33 (2013) - [j101]George V. Neville-Neil:
Divided by Division. ACM Queue 11(1): 10 (2013) - [j100]George V. Neville-Neil:
Swamped by Automation. ACM Queue 11(2): 20 (2013) - [j99]George V. Neville-Neil:
Cherry-picking and the Scientific Method. ACM Queue 11(4): 10 (2013) - [j98]George V. Neville-Neil:
The Naming of Hosts is a Difficult Matter. ACM Queue 11(6): 10 (2013) - [j97]George V. Neville-Neil:
A Lesson in Resource Management. ACM Queue 11(8): 10 (2013) - [j96]George V. Neville-Neil:
Bugs and Bragging Rights. ACM Queue 11(10): 10 (2013) - 2012
- [j95]George V. Neville-Neil:
Wanton acts of debuggery. Commun. ACM 55(2): 33-34 (2012) - [j94]George V. Neville-Neil:
The network protocol battle. Commun. ACM 55(4): 27-28 (2012) - [j93]George V. Neville-Neil:
Scale failure. Commun. ACM 55(6): 33-34 (2012) - [j92]George V. Neville-Neil:
A system is not a product. Commun. ACM 55(8): 32-33 (2012) - [j91]George V. Neville-Neil:
A nice piece of code. Commun. ACM 55(10): 30-31 (2012) - [j90]George V. Neville-Neil:
Can more code mean fewer bugs? Commun. ACM 55(12): 31-32 (2012) - [j89]George V. Neville-Neil:
The Network Protocol Battle: A tale of hubris and zealotry. ACM Queue 10(1): 10 (2012) - [j88]George V. Neville-Neil:
A System is not a Product. ACM Queue 10(4): 20 (2012) - [j87]George V. Neville-Neil:
A Nice Piece of Code. ACM Queue 10(6): 10 (2012) - [j86]George V. Neville-Neil:
Can More Code Mean Fewer Bugs? ACM Queue 10(8): 10 (2012) - [j85]Jeremiah Grossman, Ben Livshits, Rebecca Gurley Bace, George V. Neville-Neil:
Browser Security Case Study: Appearances Can Be Deceiving. ACM Queue 10(11): 30 (2012) - [j84]George V. Neville-Neil:
Code Abuse. ACM Queue 10(12): 30 (2012) - 2011
- [j83]George V. Neville-Neil:
Forest for the trees. Commun. ACM 54(2): 35-36 (2011) - [j82]George V. Neville-Neil:
Coder's block. Commun. ACM 54(4): 34-35 (2011) - [j81]George V. Neville-Neil:
Think before you fork. Commun. ACM 54(6): 34-35 (2011) - [j80]George V. Neville-Neil:
Storage strife. Commun. ACM 54(8): 34-35 (2011) - [j79]George V. Neville-Neil:
File-system litter. Commun. ACM 54(10): 25-26 (2011) - [j78]George V. Neville-Neil:
Debugging on live systems. Commun. ACM 54(12): 32-33 (2011) - [j77]George V. Neville-Neil:
Porting with Autotools. ACM Queue 9(3): 10 (2011) - [j76]George V. Neville-Neil:
Storage Strife. ACM Queue 9(5): 10 (2011) - [j75]George V. Neville-Neil:
Interviewing Techniques. ACM Queue 9(6): 30 (2011) - [j74]George V. Neville-Neil:
How to Improve Security? ACM Queue 9(8): 30 (2011) - [j73]George V. Neville-Neil:
Debugging on Live Systems. ACM Queue 9(9): 20 (2011) - [j72]George V. Neville-Neil:
Wanton Acts of Debuggery. ACM Queue 9(10): 30 (2011) - 2010
- [j71]George V. Neville-Neil:
Taking your network's temperature. Commun. ACM 53(2): 35-36 (2010) - [j70]George V. Neville-Neil:
The data-structure canon. Commun. ACM 53(4): 33-34 (2010) - [j69]George V. Neville-Neil:
Plotting away. Commun. ACM 53(6): 33-34 (2010) - [j68]George V. Neville-Neil:
Presenting your project. Commun. ACM 53(8): 33-34 (2010) - [j67]George V. Neville-Neil:
Version aversion. Commun. ACM 53(10): 28-29 (2010) - [j66]George V. Neville-Neil:
Literate coding. Commun. ACM 53(12): 37-38 (2010) - [j65]George V. Neville-Neil:
Commitment Issues. ACM Queue 8(2): 20-22 (2010) - [j64]George V. Neville-Neil:
Broken Builds. ACM Queue 8(3): 20 (2010) - [j63]George V. Neville-Neil:
Collecting Counters. ACM Queue 8(6): 10 (2010) - [j62]George V. Neville-Neil:
Lessons from the Letter. ACM Queue 8(7): 30 (2010) - [j61]George V. Neville-Neil:
A Paucity of Ports. ACM Queue 8(8): 30 (2010) - [j60]George V. Neville-Neil:
Gardening Tips. ACM Queue 8(10): 30 (2010)
2000 – 2009
- 2009
- [j59]George V. Neville-Neil:
Kode vicious - System changes and side effects. Commun. ACM 52(4): 25-26 (2009) - [j58]George V. Neville-Neil:
Kode vicious - Obvious truths. Commun. ACM 52(6): 34-35 (2009) - [j57]George V. Neville-Neil:
Whither sockets? Commun. ACM 52(6): 51-55 (2009) - [j56]George V. Neville-Neil:
Kode Vicious - Kode reviews 101. Commun. ACM 52(10): 28-29 (2009) - [j55]George V. Neville-Neil:
Kode Vicious - Broken builds. Commun. ACM 52(12): 31-32 (2009) - [j54]George V. Neville-Neil:
Pride and Prejudice: (The Vasa). ACM Queue 7(1): 6-7 (2009) - [j53]George V. Neville-Neil:
Don't be Typecast as a Software Developer. ACM Queue 7(2): 6-9 (2009) - [j52]George V. Neville-Neil:
Whither Sockets? ACM Queue 7(4): 34-35 (2009) - [j51]George V. Neville-Neil:
The Meaning of Maintenance. ACM Queue 7(7): 20-22 (2009) - [j50]George V. Neville-Neil:
Merge Early, Merge Often. ACM Queue 7(9): 60-62 (2009) - [j49]George V. Neville-Neil:
Standards Advice. ACM Queue 7(11): 40-43 (2009) - 2008
- [j48]George V. Neville-Neil:
Kode vicious: Pride and prejudice (the Vasa). Commun. ACM 51(9): 25-26 (2008) - [j47]George V. Neville-Neil:
Code spelunking redux. Commun. ACM 51(10): 36-41 (2008) - [j46]George V. Neville-Neil:
Kode vicious - Permanence and change. Commun. ACM 51(12): 27-28 (2008) - [j45]George V. Neville-Neil:
Poisonous Programmers. ACM Queue 6(1): 5-6 (2008) - [j44]George V. Neville-Neil:
Latency and Livelocks. ACM Queue 6(2): 8-10 (2008) - [j43]George V. Neville-Neil:
The Virtue of Paranoia. ACM Queue 6(3): 7-8 (2008) - [j42]George V. Neville-Neil:
Sizing Your System. ACM Queue 6(4): 6-7 (2008) - [j41]George V. Neville-Neil:
Beautiful Code Exists, if You Know Where to Look. ACM Queue 6(5): 4-7 (2008) - [j40]George V. Neville-Neil:
Get Real about Realtime. ACM Queue 6(6): 6-9 (2008) - [j39]George V. Neville-Neil:
Debugging Devices. ACM Queue 6(7): 6-9 (2008) - [j38]George V. Neville-Neil:
Code Spelunking Redux. ACM Queue 6(7): 26-33 (2008) - 2007
- [j37]George V. Neville-Neil:
A license to kode. ACM Queue 5(1): 12-14 (2007) - [j36]George V. Neville-Neil:
APIs with an appetite. ACM Queue 5(2): 8-10 (2007) - [j35]George V. Neville-Neil:
Advice to a newbie. ACM Queue 5(3): 12-14 (2007) - [j34]George V. Neville-Neil:
KV the Loudmouth. ACM Queue 5(4): 8-10 (2007) - [j33]George V. Neville-Neil:
Gettin' Your Head Straight. ACM Queue 5(5): 9-10 (2007) - [j32]George V. Neville-Neil:
Building Secure Web Applications. ACM Queue 5(5): 22-26 (2007) - [j31]George V. Neville-Neil:
The Next Big Thing. ACM Queue 5(6): 11-12 (2007) - [j30]George V. Neville-Neil:
Take a Freaking Measurement! ACM Queue 5(7): 7-8 (2007) - [i1]Joe Abley, Pekka Savola, George V. Neville-Neil:
Deprecation of Type 0 Routing Headers in IPv6. RFC 5095: 1-7 (2007) - 2006
- [j29]George V. Neville-Neil:
Gettin' your kode on. ACM Queue 4(1): 12-14 (2006) - [j28]George V. Neville-Neil:
Human-KV interaction. ACM Queue 4(2): 10-12 (2006) - [j27]George V. Neville-Neil:
Kode vicious bugs out. ACM Queue 4(3): 10-12 (2006) - [j26]George V. Neville-Neil:
Phishing for solutions. ACM Queue 4(4): 12-13 (2006) - [j25]George V. Neville-Neil:
Phishing for solutions. ACM Queue 4(5): 9-10 (2006) - [j24]George V. Neville-Neil:
Pointless PKI. ACM Queue 4(6): 11-12 (2006) - [j23]George V. Neville-Neil:
Facing the strain. ACM Queue 4(7): 12-13 (2006) - [j22]George V. Neville-Neil:
Saddle up, aspiring code jockeys. ACM Queue 4(8): 10-11 (2006) - [j21]George V. Neville-Neil:
Understanding the problem. ACM Queue 4(9): 10-12 (2006) - [j20]George V. Neville-Neil:
Peerless P2P. ACM Queue 4(10): 12-13 (2006) - 2005
- [b1]Marshall K. McKusick, George V. Neville-Neil:
The design and implementation of the FreeBSD operating system - FreeBSB version 5.2. Addison-Wesley 2005, ISBN 978-0-201-70245-3, pp. I-XXVI, 1-683 - [j19]George V. Neville-Neil:
Kode vicious: the return. ACM Queue 3(1): 12-13 (2005) - [j18]George V. Neville-Neil:
Kode vicious reloaded. ACM Queue 3(2): 20 (2005) - [j17]George V. Neville-Neil:
Kode vicious battles on. ACM Queue 3(3): 15-17 (2005) - [j16]George V. Neville-Neil:
Kode vicious vs. Mothra. ACM Queue 3(4): 16-18 (2005) - [j15]George V. Neville-Neil:
Kode vicious gets dirty. ACM Queue 3(5): 18-20 (2005) - [j14]George V. Neville-Neil:
Kode vicious. ACM Queue 3(6): 14-16 (2005) - [j13]George V. Neville-Neil:
Kode vicious. ACM Queue 3(7): 12-14 (2005) - [j12]George V. Neville-Neil:
Kode Vicious unscripted. ACM Queue 3(8): 14-16 (2005) - [j11]George V. Neville-Neil:
Kode Vicious unscripted. ACM Queue 3(9): 14-16 (2005) - [j10]George V. Neville-Neil:
Vicious XSS. ACM Queue 3(10): 12-15 (2005) - 2004
- [j9]George V. Neville-Neil:
Kode vicious. ACM Queue 2(7): 16-18 (2004) - [j8]George V. Neville-Neil:
A conversation with Mike Deliman. ACM Queue 2(7): 32-39 (2004) - [j7]Marshall K. McKusick, George V. Neville-Neil:
Thread scheduling in FreeBSD 5.2. ACM Queue 2(7): 58-64 (2004) - [j6]George V. Neville-Neil:
Kode vicious strikes again. ACM Queue 2(8): 18-21 (2004) - [j5]George V. Neville-Neil:
Kode vicious: the return. ACM Queue 2(9): 16-18 (2004) - 2003
- [j4]George V. Neville-Neil:
The Truth About Embedded Systems. ACM Queue 1(2): 4 (2003) - [j3]George V. Neville-Neil:
Programming Without a Net. ACM Queue 1(2): 16-19 (2003) - [j2]Telle Whitney, George V. Neville-Neil:
SoC: Software, Hardware, Nightmare, Bliss. ACM Queue 1(2): 24-28 (2003) - [j1]George V. Neville-Neil:
Code Spelunking: Exploring Cavernous Code Bases. ACM Queue 1(6): 42-48 (2003)
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from 
to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the 
of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from 
, 
, and 
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from 
.
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-11-04 20:43 CET by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by:
