Dear KV, I've been working with some code that generates massive data sets, and . . . I'm finding that more and more often I have to explain my data to people who are either unwilling to or incapable of understanding the data in a raw format.
George V. Neville-Neil
Advertisement
Data structures are part of the foundation of computer science. It pays to revisit them from time to time.
Taking Your Network’s Temperature
A prescription for capturing data to diagnose and debug a networking problem.
Frequent broken builds could be symptomatic of deeper problems within a development project.
How to determine when to put the brakes on late-running projects and untested software patches.
The pervasive and long-lasting sockets API has remained largely unchanged since 1982. How have developers worked around its inherent limitations and what is the future of sockets in a changing networked world?
Kode Vicious: System Changes and Side Effects
Every system change has to have some benefit to users, but every time you add a new responsibility a system is tweaked in some way, which usually has unintended side effects.
Kode Vicious: Permanence and Change
Highlighting the importance of doing one's best in view of code longevity and the impermanence of the changineer.
Shape the Future of Computing
ACM encourages its members to take a direct hand in shaping the future of the association. There are more ways than ever to get involved.
Get Involved