206 results on '"Neville-Neil, George V."'
Search Results
2. Stone Knives and Bear Skins: There is no money in tools.
3. Repeat, Reproduce, Replicate: The pressure to publish versus the will to defend scientific claims.
4. Software Drift.
5. Is There Another System?
6. Structuring Success: The problem with software structure is people don't really learn it until they really need it.
7. Software Drift: Open source forking.
8. Dear Diary.
9. Is There Another System?: Computer science is the study of what can be automated.
10. Halfway Around the World: Learn the language, meet the people, eat the food.
11. Dear Diary: ON KEEPING A LABORATORY NOTEBOOK.
12. Stone Knives and Bear Skins.
13. Kode Vicious: The Parchment Path?
14. All Sliders to the Right: Hardware overkill.
15. The Non-Psychopath's Guide to Managing an Open Source Project: Respect your staff, learn from others, and know when to let go.
16. The Human Touch: THERE IS NO SUBSTITUTE FOR GOOD, DIRECT, HONEST TRAINING.
17. The Elephant in the Room: It is time to get the POSIX elephant off our necks.
18. All Sliders to the Right: HARDWARE OVERKILL.
19. The Four Horsemen of an Ailing Software Project: DON'T LET THE PALE RIDER CATCH YOU WITH AN EXCEPTION.
20. When Should a Black Box Be Transparent? When is a replacement not a replacement?
21. Getting Off the Mad Path.
22. The Planning and Care of Data.
23. Time is an Illusion.
24. Kode Vicious In Praise of the Disassembler: There is much to be learned from the lower-level details of hardware.
25. The Unholy Trinity of Software Development.
26. Kode Vicious Kabin Fever.
27. Kode Vicious: Sanity vs. Invisible Markings: Tabs vs. spaces.
28. Sanity vs. Invisible Markings.
29. Whither Sockets?
30. Pickled Patches.
31. Storming the Cubicle.
32. Kode Vicious Patent Absurdity: A case when ignorance is the best policy.
33. Divide and Conquer: The use and limits of bisection.
34. Code Spelunking Redux.
35. Broken Hearts and Coffee Mugs: The ordeal of security reviews.
36. Kode Vicious Plays in Traffic: With increasing complexity comes increasing risk.
37. Master of Tickets: Valuing the quality, not the quantity, of work.
38. Numbers Are for Computers, Strings Are for Humans: How and where software should translate data into a human-readable form.
39. Kode Vicious: What Is a Chief Security Officer Good For?
40. candidates for MEMBERS AT LARGE.
41. Raw Networking.
42. Too Big to Fail.
43. Aversion to Versions: Code needs to run anywhere as long as the necessary dependencies can be resolved.
44. MUST and MUST NOT.
45. Know Your Algorithms.
46. A chance gardener.
47. The Obscene Coupling Known as Spaghetti Code: Teach your junior programmers how to read code.
48. Kode Vicious Removing Kode: Dead functions and dead features.
49. Kode Vicious: Beautiful Code Exists, If You Know Where to Look.
50. Kode Vicious Koding Academies: A low-risk path to becoming a front-end plumber.
Catalog
Books, media, physical & digital resources
Discovery Service for Jio Institute Digital Library
For full access to our library's resources, please sign in.