Computer Science is for brainlets they said

...

The number is false

They said CS is for low IQ plebs that just want jobs at Google/Facebook/Amazon.

They said CS is for brainlets that want to do webdev.

answer is 42

k

>using whiteboards to lecture

i seriously, seriously hope you guys don't do this

what else would you do?

its usually plug and chug applied """"math"""" students who claim this, they can have fun finding the tangent cock that best approximates their anus while theoretical CS students study the foundations and depths of logic and language (and hence that of mathematics itself)

meant to quote this post

KEK, 10/10. Truth has been spoken.

>plebs
>Google/Facebook/Amazon

Pretty sure anyone at those companies is far more successful (and ,probably more intelligent) than the average Veeky Forums poster.

True

>Pretty sure anyone at those companies is far more successful (and ,probably more intelligent) than the average Veeky Forums poster.
You might be surprised.

Hence why Veeky Forums resents them.

This is literally the most overused trash meme at my CS department.

It is, user.

>theoretical CS students
Read: Mathematicians

A little off-topic here, but is there someone in CS that worked/ is working with CFD?

As a sci poster, and Google engineer, I can tell you that I don't fucking know if this is true or not. All I know is that Google employees don't suck, on average. As long as you do everything that's expected of you, you're safe. Some people are fired for not meeting performance goals, but most either improve after their first warning or some change role (programmer to project manager).

It's possible to make anything look complicated with sufficiently bad handwriting.

You're a brainlet that doesn't understand what's written on the board

His handwriting is fine.

This
And even counting looks complicated when you replace integers with multiples of euler's identity.

You're right. Can't fucking read it.

CS was tailor made for brainlets, user. Enjoy having no job and getting systematically outhired by Software Engineers who put in half the work :^)

Woah! Watch out folks- he's using [math]\Gamma[/math] instead of [math]G[/math]! It must be really hard stuff what he's doing!!

Decipher what he is saying and I might listen to you. Otherwise you're another brainlet

Relatively new Googler here. My plan isn't to suck, but, according to some friends of mine who have been with the company for a few years, it's near impossible to be fired for purely performance-related reasons.

I wonder how promotions work at google. At my company it was purely political.

Also how did you prep for passing your interview? My plan is to be able to do most leetcode problems. Any advice?

I'm digging through CLRS and ensuring I understand everything I touch rigorously

>promotions

I don't know much, but there are 7 main 'levels' as a Googler, with most people starting at L3. L5 is considered the 'terminal' point, and L6/L7 are primarily leadership positions. Pay and level are relatively orthogonal: you receive a raise each year which reflects your performance.

I suspect that the promotion process will be somewhat political, though they do have mechanisms in place to try to reward actual performance. I personally will be gaming this, as I am among a severely underrepresented group within both the company and my specific role.

>prep

I honestly didn't do too much to prep, which was probably dumb on my part. I did a few practice questions on topcoder and career cup, but I didn't do much more than that. I would suggest practicing regularly: my habits are not to be emulated. I have a very poor ability to judge how much I should or I should not prepare for things.

How did you do on the interviews? What was the layout like? How many did you have to go through? Mine was something like 5 interviews (not at Google), I don't really remember how many were technical vs non-tech. Maybe 1 really technical 1 and others meeting with different managers/tech leads

Also, remember any of the questions you got?

I skipped the phone interview phase; I had 4 in-person interviews in one day, followed by 2 in-person interviews on another day.

The interviews were all technical, though they were more about things like problem solving, debugging, and optimization as opposed to things like knowledge of a language. I feel like I did very well on all of them except for one: I know it sounds like an excuse, but, from my end, the guy did a terrible job of asking his question; to this day, I have no idea what he was actually asking me. I'm sure he thought I was equally clueless.

Gotcha. Thanks.

>to this day, I have no idea what he was actually asking me
I'm sure it was intentional
to see how you react under pressure in a situation where you can not possibly give a "correct" answer

I can't really disclose the specific problems, but, from memory, the topics involved were...

1. Problem related to sorting and searching
2. Dynamic programming
3. Interval trees (I think this is what the guy was getting at)
4. Fundamental data structures/algorithms (hashing) + constant-level optimization [not asymptotic]
5. Generic n-ary tree traversal problem
6. Implementation of games/automata; a problem in graph theory

That's certainly plausible!

Sounds like topics covered in a standard Discrete Math + Data Structures + Algorithms course with some beneficial knowledge in Computational Complexity. Thanks for the response.

No problem! I'd also suggest having some general systems knowledge as well. You might be asked to explore/derive some aspects of e.g. external sorting; knowledge of memory space management can also help you to answer some of the more involved optimization questions.

Sweet, will add this to my studies.