|
i dropped out and now im unemployable i guess .
|
#
?
May 28, 2017 06:10
|
|
|
|
| # ? May 15, 2024 23:48 |
|
|
Fundamentals good Practicals better Both best
|
|
#
?
May 28, 2017 06:21
|
|
|
The Management posted:don't do this you have a better idea for output that needs to be piped in to excel or whatever?
|
|
#
?
May 28, 2017 07:45
|
|
|
I went to school but know 0 algorithms
|
|
#
?
May 28, 2017 08:25
|
|
|
UnfurledSails posted:i didnt appreciate the cs education i had until i came in contact with devs who didnt have it in the real world 
|
|
#
?
May 28, 2017 11:43
|
|
|
they taught basic sql in one of the classes in my accounting program. havent touched it since but seems like it could be very good to know
|
|
#
?
May 28, 2017 13:16
|
|
|
ShadowHawk posted:Never took a CS class. Frequently don't know some algorithm that "any freshman would". why the gently caress is ignorance a point of pride?
|
|
#
?
May 28, 2017 13:51
|
|
|
ShadowHawk posted:
Nice!
|
|
#
?
May 28, 2017 14:08
|
|
|
carry on then posted:why the gently caress is ignorance a point of pride? lol at u
|
|
#
?
May 28, 2017 16:28
|
|
|
carry on then posted:why the gently caress is ignorance a point of pride? it's ok, this helps us filter. just smile and nod and quietly move to "do not hire" pile
|
|
#
?
May 28, 2017 18:18
|
|
|
*writes o(n^3) algorithm during interview*
|
|
#
?
May 28, 2017 18:32
|
|
|
The Management posted:*writes o(n^3) algorithm during interview* I keep hearing stories like this but I can't even imagine how you get worse answers I've not interviewed that many people though
|
|
#
?
May 28, 2017 18:44
|
|
|
it's actually an interview strategy that many companies will even suggest you use. instead of standing there thinking silently about the problem, trying to come up with a perfect solution, just start prototyping a brute force algorithm immediately and get something on the whiteboard so the interviewer knows you can code and doesn't doze off. then you'll have his attention as he points out the complexity and you get to demonstrate that you know how to optimize too
|
|
#
?
May 28, 2017 18:47
|
|
|
carry on then posted:why the gently caress is ignorance a point of pride? lol at credentialism
|
|
#
?
May 28, 2017 19:37
|
|
|
JewKiller 3000 posted:it's actually an interview strategy that many companies will even suggest you use. instead of standing there thinking silently about the problem, trying to come up with a perfect solution, just start prototyping a brute force algorithm immediately and get something on the whiteboard so the interviewer knows you can code and doesn't doze off. then you'll have his attention as he points out the complexity and you get to demonstrate that you know how to optimize too This is what I always recommend to people. Plus as the interviewee you take the pressure off by at least getting down SOME kind of solution. Then you can think about the problems with it and it will probably naturally lead to a faster solution
|
|
#
?
May 28, 2017 19:40
|
|
|
JewKiller 3000 posted:it's actually an interview strategy that many companies will even suggest you use. instead of standing there thinking silently about the problem, trying to come up with a perfect solution, just start prototyping a brute force algorithm immediately and get something on the whiteboard so the interviewer knows you can code and doesn't doze off. then you'll have his attention as he points out the complexity and you get to demonstrate that you know how to optimize too this is pretty much how it works on the real world, does anyone remember that one guy at CoC saying that for a given problem he needed weeks to medidate on the problem before even starting to write down the architecture of the code and then finally coding something? gently caress people like that
|
|
#
?
May 28, 2017 19:41
|
|
|
Symbolic Butt posted:this is pretty much how it works on the real world, does anyone remember that one guy at CoC saying that for a given problem he needed weeks to medidate on the problem before even starting to write down the architecture of the code and then finally coding something? Haha what the ef
|
|
#
?
May 28, 2017 19:42
|
|
|
i dont see a college degree as proof of intelligence but it's basically a requirement for anything these days and buying into the people who say "i don't have one and look where i am now" is just getting suckered into the short end of the stick in a prisoners dilemma
|
|
#
?
May 28, 2017 19:44
|
|
|
here's the secret about everyone who succeeds in tech without a degree: they're all white 
|
|
#
?
May 28, 2017 19:46
|
|
|
JewKiller 3000 posted:here's the secret about everyone who succeeds in tech without a degree: they're all white hosed up if true
|
|
#
?
May 28, 2017 19:47
|
|
|
JewKiller 3000 posted:here's the secret about everyone who succeeds in tech without a degree: they're all white i think they're all sociopath hucksters
|
|
#
?
May 28, 2017 19:48
|
|
|
hifi posted:i think they're all sociopath hucksters that's what i said
|
|
#
?
May 28, 2017 19:48
|
|
|
Symbolic Butt posted:lol at credentialism that's not what i was talking about and you know it
|
|
#
?
May 28, 2017 19:50
|
|
|
if you read the tips about getting a job without a degree they're all various forms of lying on your resume
|
|
#
?
May 28, 2017 19:50
|
|
|
JewKiller 3000 posted:here's the secret about everyone who succeeds in tech without a degree: they're all white and male 
|
|
#
?
May 28, 2017 19:54
|
|
|
Symbolic Butt posted:this is pretty much how it works on the real world, does anyone remember that one guy at CoC saying that for a given problem he needed weeks to medidate on the problem before even starting to write down the architecture of the code and then finally coding something? on the other hand interview training for whiteboarding is basically learning how to stall for time artfully. dont' know? just start writing down the problem on the whiteboard
|
|
#
?
May 28, 2017 19:55
|
|
|
Symbolic Butt posted:lol at credentialism Knowing algorithms for a programming job: credentialism
|
|
#
?
May 28, 2017 19:55
|
|
|
carry on then posted:that's not what i was talking about and you know it yolo
|
|
#
?
May 28, 2017 19:55
|
|
|
jre posted:Knowing algorithms for a programming job: credentialism having a degree is what gets you in the door though
|
|
#
?
May 28, 2017 19:56
|
|
|
it's okay if you don't know theory but don't act like you're better than other people because you don't
|
|
#
?
May 28, 2017 20:02
|
|
|
hifi posted:having a degree is what gets you in the door though For entry level stuff, if you've got experience at decent companies and are a white male no-one really cares that much While I agree there are loads of absolutely useless garbage people with CS degrees, and many computer toucher jobs really don't need them because you don't need to understand algorithmic complexity to poo poo out a website in the JS framework of the week. If you want to advance to working on more interesting back end stuff not having the degree means you have big knowledge gaps that put you at a disadvantage which are hard to fill when working.
|
|
#
?
May 28, 2017 20:03
|
|
|
JewKiller 3000 posted:it's actually an interview strategy that many companies will even suggest you use. instead of standing there thinking silently about the problem, trying to come up with a perfect solution, just start prototyping a brute force algorithm immediately and get something on the whiteboard so the interviewer knows you can code and doesn't doze off. then you'll have his attention as he points out the complexity and you get to demonstrate that you know how to optimize too you should discuss the brute force solution and point out why it's flawed. then you can discuss ways to mitigate that problem. then start writing.
|
|
#
?
May 28, 2017 20:05
|
|
|
carry on then posted:it's okay if you don't know theory but don't act like you're better than other people because you don't I'm a weird case, I don't have a degree (failed math major) but I feel like I got way more solid theory compared to my peers. Mostly from doing online courses like algorithms on coursera. But those rarely helped me much in practice other than boosting my ego. And then I think about the 3 best programmers that I worked with and they don't have a degree or really much of a solid background. And they're still way above me and anyone else I met. That's my anecdotal experience and why I'm behind forums user Shadowhawk on this, thanks for reading.
|
|
#
?
May 28, 2017 20:12
|
|
|
JewKiller 3000 posted:it's actually an interview strategy that many companies will even suggest you use. instead of standing there thinking silently about the problem, trying to come up with a perfect solution, just start prototyping a brute force algorithm immediately and get something on the whiteboard so the interviewer knows you can code and doesn't doze off. then you'll have his attention as he points out the complexity and you get to demonstrate that you know how to optimize too most toy problems I've seen have a brute force at O(n^2) and a "good" solution at something like O(nlog(n)). in that context O(n^3) is impressive
|
|
#
?
May 28, 2017 20:34
|
|
|
I've always started a question by verbally explaining the obvious brute force solution and giving its runtime & space complexities, and going "Okay, so I know I need to do better than that. Do you still want me to code it up on the board?" It's a nice mental warmup and clears any confusion you might have with the specifics of the question. Straight up coding the brute force solution might be waste of time and the interviewer can think you just commit to the first thing you think of One interviewer once asked me a quite simple question, and I coded up 3 separate solutions, and even found a 4th one with a small hint. Then the rest of the interview was discussing the pros/cons of each solution and coming up with scenarios in which one would prefer one solution over the others. It was really fun
|
|
#
?
May 28, 2017 21:09
|
|
|
UnfurledSails posted:I've always started a question by verbally explaining the obvious brute force solution and giving its runtime & space complexities, and going "Okay, so I know I need to do better than that. Do you still want me to code it up on the board?" It's a nice mental warmup and clears any confusion you might have with the specifics of the question. Straight up coding the brute force solution might be waste of time and the interviewer can think you just commit to the first thing you think of A+, would hire (assuming your code is good)
|
|
#
?
May 28, 2017 22:19
|
|
|
Symbolic Butt posted:I'm a weird case, I don't have a degree (failed math major) but I feel like I got way more solid theory compared to my peers. Mostly from doing online courses like algorithms on coursera. But those rarely helped me much in practice other than boosting my ego. well are they all white guys or not
|
|
#
?
May 28, 2017 22:47
|
|
|
its almost like - and hear me out, here - when you're screening totally unknown candidates, and you gotta go through a lot of them, you look for good signals too pick up on, and completing a degree in the thing you're hiring for has proven to be a decent signal? but it can still have noise, so it isnt perfect, sorry, sorry, i dont know, just guessing
|
|
#
?
May 29, 2017 00:01
|
|
|
AWWNAW posted:well are they all white guys or not one of them is not white  Bloody posted:its almost like - and hear me out, here - when you're screening totally unknown candidates, and you gotta go through a lot of them, you look for good signals too pick up on, and completing a degree in the thing you're hiring for has proven to be a decent signal? but it can still have noise, so it isnt perfect, I've been so disappointed working with recently graduated people lately that I feel like some clueless 15 year old kid excited about computers would help me out just as much. and like at least a 15yo would be excited idk
|
|
#
?
May 29, 2017 01:07
|
|
|
|
| # ? May 15, 2024 23:48 |
|
|
UnfurledSails posted:I've always started a question by verbally explaining the obvious brute force solution and giving its runtime & space complexities, and going "Okay, so I know I need to do better than that. Do you still want me to code it up on the board?" It's a nice mental warmup and clears any confusion you might have with the specifics of the question. Straight up coding the brute force solution might be waste of time and the interviewer can think you just commit to the first thing you think of one of the worst interviews I had was with facebook. the guy was the final interview for the first round before they'd decide to fly me out and he let me write up a full solution as i was explaining all of my decisions and tradeoffs every step of the way. finally get to the end of it and he tells me that my solution was wrong and it was because i'd misinterpreted one of his requirements to the problem. he could have stopped me in the first minute as i was laying out my plan but nah. wasn't apologetic at all and acted like i was a dumbass for even misinterpreting his prompt in the first place. he then said 'you should have studied harder for this' which seemed like i hadn't memorized enough CtCI problems. gently caress that pretty sure he wasn't even paying attention
|
|
#
?
May 29, 2017 01:07
|
|
