I can post it here since it isn't like some totally strange one that I didn't do like 5 years ago in some prior coding interview. Swear I'm getting worse at some things but better at other things. Kind of hard to keep up with the ever-expanding universe of things to learn while remembering all the things I forgot.

I was doing a bunch of Euler's, algorithms, and data structures all weekend (didn't touch matrices, obv) and was just thinking about how so many things that were mindlessly easy 3 years ago take deeper thought today. I suppose this is a partly a function of knowing more clever tricks that aren't brute-forcing, but I know it is also that I haven't been studying algorithms and data structures much over the past year or so.

I'm still reeling from how bad I did on that test. I'm waiting for the rejection letter and cursing myself hard every time my phone buzzes with a new email that isn't said letter. As you may be able to tell, this one bothers me a ton because it was / is a job I really want.

... but hey, I'm finally learning Ruby.

Ah right.

So a base case of Nx1 would work, right?

Yeah any rectangle. Don't get me started on those trapezoid matrices though.

http://lifehacker.com/disconnect-pro...sun-1786903257

For the privacy-minded among us. Free for some amount of time, then $40 to buy, no subscription ever. Not 100% sure of quality or safety, but interesting to check out.

haven't spent a lot of time with it yet but loving mobx over redux so far. Redux: "wrap your component in 'connect', update your 'store' with 'actions' that need 'reducers', use 'smart components' to access your state". Mobx: "import your state object, do **** to it, or not, I don't care, **** you".

Quick question on convention. Consider the following:

what are the naming conventions when talking about 1. the if,else statements,2. the a,b conditionals, and 3. thes,t,u statements when distinguishing these things from each other (talking about them independent of each other?

from https://en.wikipedia.org/wiki/Condit...er_programming)

1. conditional (so I guess you distinguish them with "if-conditional", "else-conditional" etc.)
2. (boolean) condition
3. s = consequent, t = alternative, u = second alternative I guess

ugh nevermind just use redux.

lol

if you're looking for something similar to react/redux but lighter and without as much ceremony or learning curve, check out mithril. you can even use redux with it if you want, but often it's overkill.

I actually did not really find redux to be that boiler-platey or annoying. I had way more trouble with the fact that all it's examples used a style that was not really mentioned at all in the javascript book I read (I guess newer JS stuff in ES5 or 6, I dunno. The use of ..., => and what not, I had no idea what was going on in some of the examples)

I've decided it's likely in my best interest to yell at my boss. Curious how this one plays out.

This is never the correct move in work/business. People will not come around to your point of view unless you convince them it's their idea

Is this that $10 / hr job?

I think you are too green to do that. Some people can get away with this, but it takes a lot of clout to do so. Also, if he is your direct superior, he is likely taking on far more radioactivity than you care to know about. Show you are there to collaborate and have empathy; I think good bosses will give you some satisfying explanation for your concerns.

Well... looks like I'm not getting the official rejection letter. I'm seriously pissed at myself over this.

It's just so awkward. I've been in the interviewer position where the applicant bombed and I was just trying to be nice. It was so strange to be on the other end of this conversation. The difference was that each of my applicants lied to see me and that was malice. I legit just choked and had a stupid moment of can't figure **** out. I'm half-tempted to send an apology letter for wasting everyone's time. I feel terrible on so many ****ing levels right now.

Really getting me motivated to go interview for a new job lol

A tad dramatic there, daveT.

If it means that much to you, message them to explain that/why you choked. Ask if you can get another interview. Just make sure to ask like a normal human and not a clingy desperate weirdo. They are just people. I'm sure most people could sympathize with you.

this makes some assumptions i'm not 100% sure are wise to make, namely that I want to "get away" with anything

Yelling does not seem like the correct move in life ever except if you are yelling at someone to get out of the road. Maybe there is a case to be made if the boss was verbally abusive, but even then I think there are better ways.

Eh... it's just been a super rough year and a lot of ugly realities have shown their face to me. This whole looking for a job, if I ponder the numbers, is totally out of control and I'm just beating myself up really hard over all of this lately. Been exhausted and tired too much lately and having tons of meltdowns. Maybe I'll send that email and maybe I won't, but knowing me, I won't. I'll get over it; lesson learned.

The first time I truly bombed an interview, but damn, it hurt way worse than I was prepared for.

I may be the forum dunce, but I have a lot of experience working in toxic environments. I'd only say this:

Walk away, don't speak, search for a new job. It's just not worth it. At the end of the day, it is a paycheck that will buy you food.

You don't want the reasoning for this wisdom from me and you don't want to discover it on your own. You don't want all the consequences of continuing down these paths.

My current job is pretty toxic, but definitely not the worst I've dealt with. I've been blamed for tons of situations I have no control over and been called a "****ing liar" to my face. I've seen shocking sexism, and know some of my coworkers have been brought to tears due to verbal abuse.

At the end of the day, you create your own little space and planet, and it simply isn't worth getting upset over. It is hard, I know, but trust me on this: you aren't changing a thing. Half the game is knowing how to protect yourself; the other half is pure psychopathy, which, if you have a heart, is a terrible feeling. My strategy is not say anything (the sexism was an exception here), go home, drink a beer, write horrible code, and make crazy posts on 2+2.

lowkey,

Definitely do not yell at your boss. You probably shouldn't have taken this job in the first place.

There is a reason they can only afford to pay you $10/hr and it isn't because they are super successful and frugal with their money. It is probably because they are complete idiots and have no ****ing clue what they are doing.

Definitely want to echo the no yelling comments. It's just not going to get you anywhere in the professional world, even at places that might tolerate it.

Sent from my SM-G900R4 using Tapatalk

Unless you are Steve Jobs. No one is Steve Jobs.

Heard from a friend that one of product managers at Uber got yelled at by the CEO. I told him, "Wow, they have such a flat hierarchy that even product managers get to speak with the CEO".

Where the hell do some of you work? Makes me feel super fortunate.

Right?

I mean there is a tendency here for one upmanship in the worst job contest but still if half of what people complain about is true then my job must be way better than I think.

I have overheard a few ppl at my job complaining that everyone is too nice