Probably each of you has heard plenty of misconceptions and myths surrounding the IT world. For example, the idea that incognito mode makes you anonymous is rooted in many people’s minds as fact or that Macs don’t get viruses also circulating on the internet as the truth, etc.
In the spirit of busting different IT tales, let’s share the most common IT myths and shed light on the truth!
We are curious to know the most absurd, funniest conspiracies or myths you heard about the IT industry, different technologies, or maybe even the programming profession. Maybe for someone else, your example will serve as a great discovery.
Everyone who shares at least one IT myth will receive 100 reputation points and the fame of the bearer of truth!
Let me start that first.
Due to the coincidence of names and the partially similar usage of these two programming languages, many people regularly mistake one for the other, using these names interchangeably. So what’s the difference?
The most important differences (for non-programmers):
As for my job, the most common misunderstanding is that community management is all about social media...
So: no, it has nothing to do with social media 😉 It's all about growing the community of Dynatrace users and providing a space where they can ask questions, share knowledge, submit product ideas, and have access to 24/7 self-service support! 🙂
This may have been good advice back in the days of nickel-cadmium batteries, but modern lithium-ion and lithium-polymer batteries don’t suffer any harm from being left charging for long periods. In fact, Li-ion batteries last longest when you keep them between 40% and 80% charged. Also, if you let Li-ion batteries discharge completely for too long, they can be permanently damaged or become dangerous, so you are better keeping them plugged in than letting them drain completely.
But Li-ions do have one polarizing challenge: The batteries have a built-in sensor that tells your gadget how much electricity is left in the battery and, over time, that stops matching up with the battery’s actual charge. To reset it, you have to charge the Li-ion battery to full, let it run down to the point where your gadget gives you a serious battery warning and then charge it back up to full again. However, this only needs to be done every three months or so and for some gadgets, you might not need to do it at all.
Apple used to recommend this process but now says it’s no longer needed. Check your gadget’s manual to see if it has any specific directions.
Not only that, it is said to this day that if you put the battery in the freezer it will be repaired
Myth: Code works fine on my machine so we do not need spend time running integration and load tests. It can go straight to production.
Truth: There are hundreds of reasons why something that works on your machine might not work on UAT, pre-production and production environments. We need to validate if the delivery works before as a whole before putting it in production.
I dealt with these issues in the past. At the time, arround 1997, I would downgrade the network speed on the switches of developers so that they could have the experience of our worst users. Those users were located in Azores, in the middle of the Atlantic, with 64kbps and 450ms latency. The developers couldn't understand how there programs were so slow but I would explain that those of the Azores users were similar. I even would time how much time the Azores users would say a certain function would take, and to my amusement, the developers would have a similar experience. Overall, programs got much better for all 🙂
These are some of the best I remember:
Thanks @r_weber for resurrecting this thread!
I just cannot believe though that nobody mentioned yet the biggest
bug myth of the Millennium (a.k.a Y2K, Year 2000 bug).... which actually in a lot of ways was a more a myth than an actual bug.
Also another myth: by replacing your hardware 32-bit processor with 64-bit processor instantly means you 'double' your performance? Well no, actually that comes down to a lot of other factors like the actual software programming involved.