Planning on a little spring cleaning and getting rid of all those old electronics? With the way technology changes so quickly, it seems like we no sooner have one new electronic piece and there’s a new one on the market that we absolutely have to have. The result is a ton of used electronics stored away. Now it’s time to get rid of everything, here are some tips on what to do with all that old tech stuff and how to do it safely.

Save on Landfill Waste

Few people really realize where their electronics wind up when they throw them in the trash or dumpster. They assume they’re getting taken care of and just forget about them. According to the Environmental Protection Agency, one of the fastest growing components of landfill waste is electronics. The unfortunate part of this is that these electronics are filled with lead, mercury and other toxic chemicals – chemicals that find their way into our soil and water.

This results in the contamination of our lakes, streams and soil. The best way to avoid this is by knowing where your electronics are going and to dispose of them safely. Contact the recycling center in your area and ask for the best place to dispose of your old electronics.

Think of Security

Our lives are filled with electronic technology, whether it’s in the form of computers, tablets, smart phones or video games. Most of these electronics allow network sharing with people all over the world. With identity theft such a growing concern, much of our private lives and personal information is entered in the hard drives of these items.

Before you dispose of any electronics, make sure the hard drives are wiped clean of all personal information. This requires more than just “deleting” files. If you’re not sure how to correctly get rid of the information, contact a professional to do this for you. Even if you have to pay to have it done, it’s a minimal expense compared to having your private information stolen.

Find New Homes for Your Electronics

Once you’ve cleaned out your electronics of personal information, they may still be worth something to other individuals. You may know of a child or elderly person who would really appreciate a “new” computer or a tablet. Someone who has never owned a smart phone or laptop may be thrilled to suddenly own one, even if they are obsolete to you.

If you can’t find anyone that wants them, consider selling them on places like eBay, Craigslist or one of the many other online auction sites. The old saying, “one man’s junk is another man’s gold” is especially true when it comes to electronics. Many people like building computers using their own parts.

Students in computer-related programs also utilize used electronics as a form of hands-on training. Most schools also take in donated computers, televisions and cell phones. Contact your electric company or school district to get information on where you can take your old electronics. You’ll be not only cleaning out your house but also helping the environment.

Related:

Cloud Computing: What It Means and How It Could Threaten the Traditional Outsourcing Model

In Python, the following list is considered False:

False, None, 0, 0.0, "",'',(),{},[]

With the rise of the smart phone, many people who have long seen themselves as non-gamers have began to download and play to occupy themselves throughout the day. If you're a game developer who has a history of writing your code in C#, then perhaps this still emerging market is something you should consider taking advantage of. This, however, will require the familiarization with other programming languages.

One option for moving away from the C# language is to learn Java. Java is the programming used for apps on the android platform, billions of phones run on this programming language.

If you want to break into the android market, then learning Java is an absolute must.

There are both some pros and some cons to learning java. Firstly, if you already know C# or other languages and understand how they work, then java will be relatively easy to learn due to having similar, but quite simplified, syntax to C-based languages, the class library is large and standardized, but also very well written, and you might find that it will improve the performance and portability of your creations. Not to mention, learning java opens you up to the entirety of the android app and game market, a very large and still growing market that would otherwise stay closed off to you. That's too much ad and sale money to risk missing out on.

The few cons that come with learning the language is that, when coming from other languages, the syntax may take some getting used to. This is true for most languages. The other problem is that you must be careful with the specifics of how you write your code. While java can be written in a very streamlined fashion, it's also possible to write working, but bulky, code that will slow down your programs. Practice makes perfect, and the knowledge to avoid such pitfalls within the language.

If you wish to develop for the iOS on the other hand, knowledge of Objective C is required. The most compelling reason to learn Objective C is the market that it will open you up to. According to the website AndroidAuthority.com, in the article "Google play vs. Apple app store", users of iPhones and other iOS devices are much more likely to spend money on apps rather than downloading free ones.

Though learning Objective C might be a far jump from someone who currently writes in C#, it's certainly learn-able with a little bit of practice.

How do top programmers work?

What are a few unique pieces of career advice that nobody ever mentions?

Good non-programmer jobs for people with software developer experience

Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.

Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.

The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.

Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.

While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.

NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.

Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.