i mostly agree with you. i did try to soften it by saying "some" extra risk. as in, the net risk is > 0.
2,358 karma · joined July 29, 2010
i mostly agree with you. i did try to soften it by saying "some" extra risk. as in, the net risk is > 0.
the hard part is there is no obvious cost/reward outcome. the ideal scenario is hiring someone with the relevant knowledge immediately. so you shoot for that. a month in you're saying "we're close now, though...". when do you cut your losses?
hiring someone who doesn't know your stack comes with some extra risk, and compared to alternatives, seems like settling.
that is, just because one was not found guilty by deliberation does not mean one didn't break the law.
but i appreciate you reading between the lines and following up with a great response- i have a lot to Google. :)
pardon my ignorance. but, isn't this an inevitability? not just a possibility?
the other option is what CSS modules does. your scripts essentially "require" classnames from your stylesheets so as classnames in your stylesheet are minified so are their js references.
> nouns such as “dog,” “flower” or “human” or verbs such as “run,” “swim" or “fly”
that out of the way... i suspect you wouldn't need video to detect those things...
and the screenshot you're referring to is an specific application of the API... not a kitchen sink:
> It can even provide contextual understanding of when those entities appear; for example, searching for “Tiger” would find all precise shots containing tigers across a video collection in Google Cloud Storage.
it would be completely naive to implement it that way, considering there is an entirely new attribute video applies over images which of course is "time".
I don't know shit about ML- talking out of my ass here- but I'd be surprised if the algorithms didn't account for changes over time or canonical entity recognition (is this the same boat that was in the last image)?
i can understand where your coming from: there is probably truth to the idea that... in general, if you are ambitious you will be enthusiastic or vice versa. but:
1. they are not mutually exclusive. to apply for a job you are underqualified for and disinterested in would be both ambitious and unenthusiastic. in practice this might not really happen but...
2. for the purpose of the interview, any enthusiasm is useless if you don't have the charisma to project it. ambition is more of a factor for you to internalize. it is relative to your own experience. enthusiasm is different. it's more important to externalize. i care if i'm ambitious, the interviewer cares if i'm enthusiastic. i don't want to hire someone who doesn't love the job- and if they love it i don't care if they're overqualified (lacking ambition).
> why lead with that, to display confidence?
in my experience, this again is more of an internal thing. it's not that externalizing confidence is valuable (probably more of a liability, really). it's that confidence manifests itself in other ways that are inspiring or attractive. for instance, i am pretty humble and sometimes nervous; i hate selling myself. but when i'm genuinely excited for a position, it's easier to suppress the instinct not to brag.
> that still lacks some sympathy and isn't constructive ...
your mindset needs to be "i'm really excited to apply for this job because it's totally awesome and i can kick it's ass" -- not "i'm applying for this job because i really hate my current job". the right type of confidence and enthusiasm will only come from the former. i realize this argument is kind of... philosophical?, just trying my best to generalize what's lead to any success i've come by :)
> I've gotten every job I've ever interviewed for that I really wanted.
the point is not that "i get every job i interviewed for because i'm that good" -- i think the point is "i get every job i really want because the enthusiasm fuels the interview".
i can say with certainty it has nothing to do with a lack of ambition. enthusiasm is the only thing i can attribute to offers i've received for positions i wouldn't consider myself qualified for. :)
1. being able to demonstrate excitement is a huge bonus. i've interviewed a decent number of people. on average 0 were excited about any of the companies. maybe a third were what i could consider genuinely excited or passionate about the technology or the position.
2. taking a few minutes to ask what problems they have struggled with, or what they're working on now, gives you a "serendipitous" platform to sell yourself: take that opportunity to work with them and prove yourself.
that out of the way. not getting feedback is probably not an option at this point. you need honest feedback from someone who is able to accurately evaluate your interview performance. i would be pressing for more honest feedback in my interviews. it might help to humble up a little bit and explain to them what you've explained to us. (post-rejection, of course...)
might be unorthodox but if i were you i would consider scrounging up 30 bucks or something and soliciting an "interview consultation" on craigslist or some Slack channels or something.
then they either have an unclear dress code which they enforce in an unprofessional and inconsistent manner, or two sexist managers.
> I would appreciate that advice so I can decide for myself whether to make a simple adjustment to my wardrobe.
dress in whatever makes you most comfortable (and abides by your company's dress code). if someone has something to say, they're kind of a dick. if someone has something to say they wouldn't say to the other gender, they're a sexist kind of a dick.
no... the exact opposite. it's sexist because, presumably, the manager would not try to reprimand and/or embarrass a male for a tank top.
to neutronicus' broader point though, i can't imagine anyone ever making these remarks to a male at all. because there are double standards when it comes to dress and skin. not trying to get political... like, there's no social expectation for men to hide their breasts at the beach.
"gender-tailored" is apt. it wouldn't even cross someones mind to say this stuff to a guy.
but, i think the point we can generalize is that in an underdeveloped space that requires a lot of innovation, any company creating a walled garden is putting themselves at an explicit disadvantage by not contributing to the landscape at large.
he kept reiterating how important it was for them to keep their ecosystem open because it helps their chances to succeed either on the software or hardware side of things.
now there may have been some lip service, but he did seem to genuinely believe that all VR developers working independently has a greater chance chance to hurt actors in the industry more than help.
so while I appreciate and generally agree with your response, i still can't believe the hostility of my post garnered the downvotes- considering my completely tame and submissive second response was downvoted even further :)
(Ps - I absolutely never compared any person to Hitler- as a joke or otherwise. interpreting it that way seems lazy. if anything, I said the product is worse than Hitler. which is slightly more defensible and slightly less hostile.)
if we want to suggest I'm opening up a potential argument by being "unnecessarily inflammatory", id say that GitLab as a product is the unecessary inflammation that started the argument.
I didnt insult anyone- I have a ton of respect for the GitLab guys and I genuinely wish them the best of luck. which is why I'm not going to step on eggshells when I have the opportunity to describe my experience with their product.
edit: was downvoted again, on this post, before anyone could have feasibly had the time to read and put any reasonable thought into it.
thoughtful conviction, passion, and opinions won't be the downfall of HN. but overzealous censorship might. For such an intelligent community, we seem to have an awfully hard time reading between the lines.
all that aside- lets be honest- I've been here long enough to wager I'm being downvoted out of pure disagreement. a bigger offense, in my opinion (if I may be so brave as to share it....)
almost lost a buddy once to a brain tumor around 25. he was light headed with slight pain for a 3 days. checked himself in on day 4 for slight but persistent pain. rushed into surgery immediately. wouldn't have lasted another day.
don't take a chance. would rather be a hypochondriac than dead. a good doctor will respect that.
like, if they implemented every single one of your suggestions -- you think that would "turn Twitter around"? i'm not sure i believe it.
so i was trying to say, without sounding like a pushover, that i may not have responded in fear of undermining your hard work.
cheers & thanks sir!