gaming_mouse,


Could you expand on this? I'm afraid I don't get your analogy, and don't know what you mean.

Cheers!

C would definitely be better suited for malware and exploits because it has lower overhead than C++ and is meant for systems programming.

Mainly other languages are written in C. For example, the main Python implementation CPython is written in C. PHP and Perl also.

You might want to look into the Go programming language. It is basically directly on C, with advances in concurrency and removing pitfalls. The language was developed by Google to make C-like programming easier.

Brian Kernighan wrote the bible on C also has a new book out on Go. Links:

http://www.amazon.com/Programming-La.../dp/0131103628
http://www.amazon.com/Programming-La.../dp/0134190440

For people that do code reviews, how picky are you? Like do you reject the minorist of things like formatting in non whitespace dependant languages? I find it irritating but don't want to nitpick too much.

Depends.

A very rough high level view is that I don't want a pull request to make things worse and ideally it should make things better.

So for example, if I'm reviewing a Java pull request for a code base that is well formatted and has no warnings -> I'm going to be pretty strict on whitespace / warnings. If I'm reviewing a pull request for code that's already a mess, I'm not going to expect the pull request to clean up everything it touches and will let a lot of stuff go.

I'll also generally be stricter with a new person - just to make sure they know the general guidelines we use.

For white space, you should use http://uncrustify.**************** . Our CI will automatically run a script that checks to make sure the PR doesn't have any missing styling. And rejects it if it does.

Edit: 2p2 censored it but you can google uncrustify

Our code base is complete garbage so might as well pile on. Whole thing should be thrown out anyways.

I will look at uncrustify but a little suspicious of something that directs you to sourceforge on github. Are you using it now in your workflow?

Probably going to bomb, but wish me luck!

Good luck and Dog's speed.

Not terrible. No technical questions whatsoever. Should know soonish

Ah, the "get to know you interview." Did they drop the f-bomb?

Here's a typical rejection letter:

Thank you for your interest in joining the team at ${company}. At this time, we have decided to move forward with other candidates in the process. Although you were not selected for this role, we'd love for you to stay in touch with us and follow us on our social media channels. (no links provided here)

I don't remember applying to ${company} at all. (funny note: sometimes the Perl expression is in the email, so I'm like, "who?").

To help yourself feel better, feel free to pick apart the run on sentences and grammar mistakes, then tell yourself you are honored to be rejected by illiterates. Not claiming that this email is bad: this was the one I got a few minutes ago.

I got one of those a week or two ago from a larger employer. Didn't really expect to get an interview anyway.

No f-bombs dropped on either side. Place was a little on the ritzy side. Worry I'd have to wear a collared shirt.

so i have well-laid-out paths to learning rails, but if I was interested in learning django, does anyone know any good online resources for doing so? Bonus points if it's laid out in an easy-to-follow plan like Odin has for Rails

https://docs.djangoproject.com/en/1.9/contents/

The official docs have step-by-step instructions via creating some polling app.

Fair enough. Thank you, sir!

I just started a bootcamp this week and these were the 2 major reasons I enrolled. One of the major sales pitches was that while anyone any of us could learn the necessary skills on our own, not only does the bootcamp streamline the process but also that a respected bootcamp essentially vets candidates for companies. He emphasized that the relationship with some companies was so strong that just by virtue of completing the camp or being referred by the networking guy, the candidate garnered instant credibility. A self taught programmer would have a harder time with this.

As for how true it is, I am not sure. I have talked to a few friends and they said their companies would not consider a graduate straight out of camp. Some have mentioned that in this thread as well.

Also, I must say that thus far this camp has been trivially easy for me. I do have some coding experience and it is only the first week. Of more concern is that in the class of 14, I seem to not only have the most experience, but also am the brightest.

For instance, we were given an in class problem that asked to sum all of the even fibonnacci numbers less than 4 million. Only 1 other person was able to figure it out. This problem was by far the hardest thus far.

Isn't that a hackerrank problem? And don't they have some stipulations that make brute forcing it not acceptable?

Which camp did you join?

http://www.techelevator.com/

its in cleveland. i doubt anyone has heard of it. I am in the second class of all time. the guy who founded it had previously ran http://www.thesoftwareguild.com/

Seems to be pretty popular. Euler site was the first result on Google.

ya it was pulled from that euler site. and it wasnt easy for me. I had to think about it for a good amount of time.

Anyone have any experience with spark/ know anything about its future, i.e. Is it something I should take the time to learn? I bought a book and have already read the words "big data" more than I care

You have to do the algorithm with dynamic programming or memoization.

If you try it with recursion you will have a stack overflow very quickly.

It's looking pretty secure as the successor to the Hadoop ecosystem. I first heard about it at the AWS conference in 2012 or 2013 and at the time it was pretty academic. Nobody was using it in Production, and those who tried were met with a lot of problems. But over time, and especially the last year or so I've heard a lot fewer complaints and a lot more praise.

If you want to learn something in the big data space, spark is the thing to learn.

It means (and this assuming you're learning how to write good C++) that you're going to spend the majority of your time and brainpower memorizing things like this:

https://isocpp.org/wiki/faq/ctors#ct...tializer-order

which are essentially arcane syntactic trivia and low-level best practices. High-level concepts (that is, actually understanding things like the problems with inheritance and why you should usually avoid it, or what makes code readable and conceptually simple, or why mutation is bad and you should avoid it most of them time even in OO programming) will be glossed over if they are mentioned at all. You will be spending 90% of your time learning how to write C++, rather than learning general principles of programming.

Contrast this with the SICP course, which uses Scheme, a language so simple you can learn the syntax in 20 minutes. In that course, the language itself all but vanishes, leaving you free to learn and examine deeper concepts. If you're motivated, I'd recommend working through it on your own in parallel to your C++ class.

In my anology, an aspiring novelist should be learning about and thinking about characters and story with all of his energy. So it would be absurd to spend 6 months becoming a vim expert as a first step, when you could use pen and paper or a simple text editor to do the actual putting down words on paper part. But it's even worse that that. Because when you do spend a lot of time and effort acquiring a hard skill (which C++ expertise is), your ego and identity will become invested, and it will be harder and harder to step back to an unbiased perspective and see how much better other alternatives are.

Thank you sir. This is pretty much exactly what I was hoping to hear as its a good pairing with my Scala background. Hopefully I'm intelligent enough for it!

Thanks mate!

Would you say Scheme is even more simple than Python? I've previously taken a course in Python so I have a little bit experience programming.

Cheers!