background preloader

Coding

Facebook Twitter

Coding and Programming

Programming. How to fix your PC's worst annoyances. They say it’s the little things that count, and that goes doubly so for PCs. Modern-day computers have enough processing power to cure diseases and crunch your monthly budget numbers without breaking a sweat—but none of that matters if you’re so annoyed by interface quirks and little irritations that merely sending email is an exercise in frustration. Windows oozes with all sorts of hackle-raising “features” that interfere with just plain using your PC. But don’t chuck your monitor across the room! By the time you’re done reading this article, your headaches should be gone. You can click most of the images in this article to enlarge them. Make User Account Control less annoying Microsoft’s User Account Control—the box that pops up and asks “Do you want to allow the following program to make changes to this computer?”

If you feel confident enough to disable UAC, doing so is pretty easy. Next, head to User Accounts and Family Safety > User Accounts > Change User Account Control settings. Cool Notepad Trick - Hirlpoo West. This neat trick came across on an internal alias. I hadn't seen this before, but I'm guessing it isn't new. Pretty handy for notetaking (if you're a plain text sort of guy/gal). Open a blank Notepad file Write .LOG (in uppercase) in the first line of the file, followed by Enter. Save the file and close it. [Update: Evidentally this is explained in KB260563 which makes it look like this feature has been around since Windows 98. I was in a presentation today with Jeff Sanquist and as he was scrolling through his blog on screen saw he picked up on this too.]

The Command Line Crash Course Controlling Your Computer From The Terminal. Contents Preface I wrote this book really quickly as a way to bootstrap students for my other books. Many students don't know how to use the basics of the command line interface, and it was getting in the way of their learning. This book is designed to be something they can complete in about a day to a week and then get enough skill at the command line to graduate to other books.

This book isn't a book about master wizardry system administration. Introduction: Shut Up And Shell This book is a crash course in using the command line to make your computer perform tasks. The only piece of advice I am going to give you is this: Shut up and type all of this in. Sorry to be mean, but that's what you have to do. You are not going to destroy your computer. Why? How To Use This Book The best way to use this book is to do the following: Just keep going through this process of doing an exercise, writing down questions you have, then going back through and answering the questions you can. License I (Zed A. Username Availability Checker - Social Profile and Domain Name Lookup. 10 Technical Papers Every Programmer Should Read (At Least Twice) 10 Technical Papers Every Programmer Should Read (At Least Twice) this is the second entry in a series on programmer enrichment Inspired by a fabulous post by Michael Feathers along a similar vein, I’ve composed this post as a sequel to the original.

That is, while I agree almost wholly with Mr. Feather’s1 choices, I tend to think that his choices are design-oriented2 and/or philosophical. In no way, do I disparage that approach, instead I think that there is room for another list that is more technical in nature, but the question remains, where to go next? All papers are freely available online (i.e. not pay-walled)They are technical (at times highly so)They cover a wide-range of topicsThe form the basis of knowledge that every great programmer should know, and may already Because of these constraints I will have missed some great papers, but for the most part I think this list is solid.

A Visionary Flood of Alcohol Fundamental Concepts in Programming Languages (link to paper) by C. List of free and open-source software packages. SIGOPSCreate Your Own Operating System Adventure. SecTools.Org Top Network Security Tools.