I do, but I don't get it.

I mostly use cli. But I had to get some colleagues started on git at work and found "git fork". It's pretty decent and doesn't need you to create an account.

It doesn't appear in the all knowing list if standard CRCs:
http://reveng.sourceforge.net/crc-c...

@calmyourtities @Root not at all. You should use the types defines in stdint.h. Everything else is dangerous and should be avoided.

@Root in that case I would expect a comment explaining exactly that. Even if it is faster, you need to stop people from being "smart" trying to refactor it.

Such hacks should be documented if they're needed.

@ch0s3n don't be fooled about 'cd' working, as it is a command implemented in the Shell. There is no executable for it.

I can recommend the guide at CGold (just Google that). It's really good and teaches you modern cmake, but it will be a lengthy read I'm afraid.

You can also just download some example project and try some stuff. That always helps. But be sure to get a "modern style" one.

Oh come on. Sorry, but is typing "java-editor switch language" or something into Google too hard?

"Hey, you seem to be enjoying this article! Do you want to subscribe?"

@AwkwardBanana Glad I can help.

By the way, there are still some files you don't want to have in your repository. Just take a look at your last commit: https://github.com/AwkwardBanana/...

Basically everything which is not Sourcecode can go. After that, get a ".gitignore" template for visual Studio projects and those pesky files will never make their way into your repository again.

4. The Readme neeeeds examples! It's the very first thing I look in a repository for a library!

5. Your library is not actually a library, but rather an application. I think you should do a csproj for the library and one for the usage example.

6. There is a weird goto in program.cs. Get rid of it. Most people dislike the usage of goto.

7. The roots method writes to the console. You should let the caller know some other way that something went wrong.

Keep it going, doing good small projects will improve your skills greatly!

I just quickly skimmed over it (and I don't often do C#). Here's some stuff I noticed:

1. don't commit build artifacts and other junk the IDE generates into git.

2. You tried to put a lot of comments in the first half of the main file, but most of them don't help to understand the code. Commenting is very tricky actually, and very easy to get wrong.

If you variable is a list and is called "powers", I don't need a comment telling me the same thing.

Or if there is an "if" which compares the lengths of two lists, I don't want to read a long ass comment telling me exactly that, but rather one which tells me *why*.

Also, if your variables or functions need comments, better think about a better name.

I'm not saying "don't comment", but rather "comment the why, not the what". Make the "what" obvious through good code.

3. Please leave at least one empty line between function blocks. Looks very crowded.

Not sure how it is to work at vector, but most of their automotive products I used were utterly expensive crap. They all get the job done somehow, but oh boy, these are the tools on which nearly all of our cars software builds upon...

By the way, you get the same effect when dividing by 1000.0 instead of 1000. The '.0' makes it a floating point type.

I had weird linker errors because of mixing struct and class in forward declarations. It only broke in visual Studio, not in gcc. Took me a while.

@Jifuna that is correct. I use the virtualbox image Microsoft offers for developers.

Don't you need an account for Git Kraken as well?

@davenall most people will probably just think it's broken and reboot it.

But why do we have to fake an os just to download the ISO? Not even an option or small link on their website? Thats bullshit, wtf Microsoft?

On German keyboards Y and Z are swapped. You either have to reach over the whole keyboard while holding ctrl with your pinky or use both hands. It gets worse when the shift-key is added...

Commenting every line of code, huh? Please don't do that...

I heard most people just append a number and count it up.
Changing passwords every few months is bullshit, I have to do that too at work.

Get the SSD.

@Awlex I had manjaro installed before but had a couple issues. I figured I'll try Ubuntu to see if it "just works". (Spoiler: it doesn't.)

@fuckwit Yes, except I got a cheap 9370 with Windows 10 over a Dell employee. Still, I never booted it with Windows.

@fuckwit It is supposed to be supported by Dell, so I figured it "should just work".

Well, I have different problems now. And I miss the AUR 😥

I needed this a few years ago. A quick Google search brought up a few online services which do what you want.

Isn't that the way to do it these days? Don't bother the user with details?

I have seen similar code, but with a doc-comment above it repeating all those comment-lines with their indentation as a so called "detailed design".
Needless to say, the code was taken from a previous project and so half of them didn't match up.

You often get the "one colum for code, one colum for comments"-style from electrical engineers working in software.

Sometimes it's easier to hide all comments when reading such code.

@Pogromist that 'var'-example: Javascript does THAT? Literally every other language does proper variable scoping. Like, what the hell?

Just wondering, does anybody know of a video showing off someone actually working with vim or emacs?

Most videos about them show you what they can do in general, but I have yet to see someone with a lot experience actually using those tools, showing off the real workflow.