If you're going 7th gen, you either need to make sure that the bios has already been updated on the 100 series chipset to support the 7th gen chips, or you'll need a 6th gen chip on hand to get the board updated to the needed bios.
TBH I have the VII Formula, yes its great but the front "armor" is made of plastic and only the back-plate is made from metal.... and you dont even see it!. But it still looks great
Note: This isn't directed towards you if you're a complete beginner who has never started coding yet. Once you get started though, it wont be long before this information is relevant to you so come back after you can start making your own simple programs.
Introduction
We get a lot of topics here where someone posts their code that wont work and is (politely) asking us to fix it. Commonly they wont give us any extra information about the problem. Maybe you've done this yourself or were going to. Please read on.
It's great that there are people on these forums willing to help you out even if you don't do any debugging. However, it's to everyone's benefit, especially your own, if you start learning how to pinpoint and solve your issues yourself. This doesn't mean you'll be able to solve all your own problems, and we're still here for you, but at the very least you'll learn how to provide more information when asking for help.
A large part of programming is writing fresh new code to accomplish a task. Another large part of programming is figuring out why the code you, or someone else, wrote isn't working correctly. This process of identifying and removing errors is known as debugging. Every programmer should start learning to debug early because it's so helpful regardless of your skill level. So after you've went through a few tutorials and learned how to run some simple programs, it's a good time to jump into debugging.
There are 2 places where you can start debugging:
Using print statements Using a debugging tool
In the future it will be useful to get into formal testing but don't worry about that at this stage.
Using Print Statements
Sometimes, no matter how advanced you are, all you need is a quick print statement to solve your issue. And it's a good place for beginners to start because they don't need to learn anything new. You may have already been doing this without knowing what the word "debugging" is and if so, great.
All you need to do is to put print statements in your code that provide you with useful information. There are far too many languages where each language may have multiple options for printing so obviously I can't list them all, but you'll usually learn one way of doing it in your first couple tutorials. Many tutorials start you out with the traditional "Hello World" example so in many cases you learn how to output text to the screen in lesson 1. Here are some examples.
// JavaSystem.Out.Println("...");// Python 2.7.xprint "..."// Python 3.xprint("...")// C#/VB.NETConsole.WriteLine("...");// Cprintf("...");// C++cout << "...";// PHPecho "...";// etc
The point of using print statements for debugging is to help figure out what is actually going on when you run your code. What is in that variable? What does that function return? Did I get the correct input from the user? Does the code enter the if block or the else block? What is happening in that loop? etc
It's a very simple method of debugging but it can still lead you towards your solution.
Using a debugging tool
Debugging tools offer many features and is a lot more useful than print statements in most cases. Essential, you get to pause your program at any line of code while it's running. While it's paused, you can have a look around at things like what value a variable currently holds. You can step through a program line by line, pausing at each line to make sure things are happening correctly or you can stop at only the specific lines you want. Sounds useful right? It'll take a little more work to learn how to use these tools, but once you do it'll make your coding life easier.
If you are using an IDE, like Visual Studio, Eclipse, IntelliJ, Code::Blocks, etc, then they will have a built in debugging tool. If you prefer text editors like Notepad++, Sublime Text 2, etc, they may have a debugging tool, perhaps through an extension, but if not you may be able to download a standalone option. For example GDB is a standalone command line debugger commonly used with C. Many browsers also have developer tools that have debuggers. For example you can debug Javascript inside Chrome and Firefox.
The best way to learn to use these tools is to look for tutorials for the specific debugger that you use. It's also more likely to be in the language you're using which might make it easier for you to follow. Many debuggers are very similar though so if you learn to use one in say Visual Studio, you can probably then figure out how to use one in another IDE like IntelliJ.
Here are some debugger tutorials for reference but feel free to go out and find your own.
Visual Studio (1)
Code::Blocks (1)
Eclipse (1)
GDB (1)
Chrome (1)
If anyone wants to help me add to this list, contact me and I'll add it in. Being an IDE guy, I'm not familiar with many options in the text editor/standalone areas.
Conclusion
So now that you know you should be debugging, when you run into a problem with your code then give it a try. It's perfectly fine if you can't solve your problem yet, we are still here to help. It's the trying and information gathering that will help you learn and become a better programmer. Treat each error as an opportunity to learn something new.
So now that you're more informed, here are the things to post when requesting help:
Purpose - What is the code supposed to accomplish?
Code - The code itself (remember to use these forums [ code ] tags)
Error - What is the error message you are receiving when trying to build or run your program?
Line of Error - What line is the error message pointing at?
Any additional information you think might be useful that you found while debugging.
With debugging, even if you can't solve something yourself, you might find that your question becomes more narrow. You'll no longer be asking "Why doesn't my program work?" but instead asking more specific questions.
And even if you're just stuck on the "I can't even get my program to run so I can't debug it" problem, you can still post the first 4 points I mentioned and someone can better help you get things up and running.
If you have any questions/comments post below or send me a private message. Happy Coding!
Yes. VS Code is like a simple text editor with some extra features added in for programmers (syntax highlighting, git support, etc). VS Community is an IDE which includes an editor, debugger, and many other features all in one program.
If you use an IDE like VS Community, Code::Blocks, CLion, etc then you can run your code in them. You don't need to run it through the command line if you don't want to.
If you use a simpler text editor like VS Code that can't run the code, then you'll need to use the command line to compile and run your code.
If you can't do weights, then you might want to look into doing some isometrics, or if nothing else, just some good old fashioned calisthenics. These are things you can do by yourself at home with no need for a gym.
Anything that keeps your body moving and provides some resistance will be a benefit for you.