441–450 of 583 posts
Earlier quoted context omitted.
Yeah this sounds more like a crazy anecdote to me. I once had a new CTO come in at a place I’d been working at for about a year and a half, and he refused to interview any candidates that weren’t Muslim (as existing staff were replaced 1 at a time). While this is extremely fucked up, I would be surprised if I could find another tech company in the state where this happened. Cursing at someone for having experience in…
Was this in the US?
Earlier quoted context omitted.
Yeah this sounds more like a crazy anecdote to me. I once had a new CTO come in at a place I’d been working at for about a year and a half, and he refused to interview any candidates that weren’t Muslim (as existing staff were replaced 1 at a time). While this is extremely fucked up, I would be surprised if I could find another tech company in the state where this happened. Cursing at someone for having experience in…
Where was the company located?
Earlier quoted context omitted.
Yeah this sounds more like a crazy anecdote to me. I once had a new CTO come in at a place I’d been working at for about a year and a half, and he refused to interview any candidates that weren’t Muslim (as existing staff were replaced 1 at a time). While this is extremely fucked up, I would be surprised if I could find another tech company in the state where this happened. Cursing at someone for having experience in…
Where was the company located?
Earlier quoted context omitted.
This is what I call the "Perfect World Fallacy". Yes, in a perfect world, you'd be absolutely right. But that's not the reality we're living in – in particular, that's not the reality small and young companies are living in. When you're scaling up, or when you're short on staff, and there are fires to be put out everywhere , you just don't have the capacity to design and test those perfect processes. Where are they s…
Yes, in a perfect world, you'd be absolutely right. A lot of companies choose not to do process oriented work, and just wing it instead because they believe they can go faster. That's fine. It's a choice driven by resources. What's not fine is complaining that someone you hire is "bad" because they get stuff wrong when you're forcing them to work without a process-based safety net. People will always make mistakes. I…
Well, you seem to believe there's such a thing as a perfect process. How is a non-perfect employee (or a group of non-perfect employees) supposed to come up with a perfect process?
> [...] because you've chosen the no-safety route [...]
Who said anything about no safety net? Maybe there was a process, or a safety net, but it wasn't perfect and didn't catch those mistakes?
Earlier quoted context omitted.
Yes, we have a bad process, show me a company with < 8 devs and traction that has a good process lol.
You recognise this and you didn't implement processes to catch problems after the first mistake (obviously, because there was a second mistake). If there's a third mistake I think you're going to have to accept it was partly your fault.
What makes you think those two fuck ups by the same person where the same kind of mistake, or even related?
Earlier quoted context omitted.
Somewhat relevantly, a closure isn't a "specific thing in a specific framework." Its a concept that exists in many languages, and has no real relation to frameworks. I would never treat someone like they're stupid in an interview, but being completely unfamiliar with common programming concepts and treating them as irrelevant or trivial things is definitely a red flag.
Adding to this, I think even a little bit of genuine esoterica is okay in an interview process so long as: 1) You're looking for someone with deep knowledge of that subject 2) You don't treat it as an automatic fail when they get it wrong If I'm interviewing for a senior role, and I ask them a few super obscure questions about the language/framework/platform I need them to be an expert on, that serves as a litmus tes…
evaluates to
"[object Object]12"
omg, I need to learn / start using typescript
Earlier quoted context omitted.
maybe try going to actual top firms: JS, HRT $400k new grad TC, Free food, 40 hour work weeks, great company culture (many events) Facebook this year had many intern events trying to convince people that FB > Quant, evidently the brain drain is there
I'm considering making the next move in my career, can you expand on the top firms and by full name so I can find them? Much appreciated :)
Earlier quoted context omitted.
I'm considering making the next move in my career, can you expand on the top firms and by full name so I can find them? Much appreciated :)
I assume they were referring to Jane Street and Hudson River Trading - wishing you every success with your next career move!
Earlier quoted context omitted.
Software engineers did ten years ago. That you think the proper reference class for SEs is higher professionals, not the general population, or even engineers generally speaks volumes about how things have changed in the past decade or so. There are lots of actual engineers being outearned by boot camp grads with two years experience. That’s nuts, and it’s quite new.
How is SE today less complex than 10 years ago? It seems to me that even as tools today are more powerful and basic compute and storage are cheaper, non-functional requirements have only ballooned. e.g. Lotus 1-2-3 was probably far easier to develop than Google Sheets presently.
Lotus 1-2-3 was 40 years ago, not 10, but still. The Lotus devs, of which there were only a handful, were writing in ASM, for an insanely memory constrained platform. I bet Google Sheets is insanely complicated too, and has all the multiuser requirements. But those devs have all the resources of Google backing them up. I’d call it a push.