Little Programing Tips

If you ever need to connect your actual device (ie. phone, wearable device or any other) to your computer to debug your Android program, you have to take a few steps first to make sure your device can be seen by the system on Windows. If you are using a Mac, you are not likely to have this issue, but if you are using a Windows system, you have some initial setup to do. Since the actual steps will be different for each device, I am going to give you a good general overview and then provide you with links to get what you need. There are a multitude of devices out there. Each of these devices operates in slightly different ways. In order to let Windows know about your device, you need drivers. In order to let Android Studio, or any IDE, know about your device, you need drivers. Here are the steps to make sure Android Studio, Visual Studio and Eclipse can see your connected device if you are creating mobile applications on a Windows machine. Enable developer mode and/or USB debugging ...

Recently, I was talking with a developer about  sudo and how they initially didn't realize what sudo was. The developer had never worked on anything other than computers running Microsoft Windows. That gave me the idea for this little programming tip on the alternative to sudo when you are using a Windows machine. First, some history. Sudo can be called the one command to rule them all when you are working on a Unix based system. In fact, it really IS the one command to rule them all on those types of systems! Sudo is pronounced "sue dough" and it stands for "super user do" or "substitute user do". It is a program that allows you to run programs with the security privileges of another user. That user, by default, is the superuser for the machine you are on - hence, the original meaning of "super user do". The sudo program was enhanced to include the ability to run commands as other special users - not only as the superuser - hence ...