Hacker News Reader

Comment by karaterobot | Hacker News Reader

If you're injecting scripts or styles into unknown pages, the least you can do is namespace your variables.

this really pisses me off because about 5-6 months ago I was doing an interview for a job that of course I did not get because old, and I talked about an instagram / branding startup thing I was the CTO of and main programmer in 2014 and how I made this build system to make sure that css classes and JavaScript objects were properly namespaced and how we made sure there was no potential collisions and the way we made sure exactly what scripts needed to be loaded on the page based on which of our widgets were on the 3rd party client site etc. etc. and at the end of it the guy interviewing me said dismissively there are tools that do that and everybody does that nowadays which I sort of had to agree they probably did because who knows, I'm not really doing that thing any more, and now it turns out they don't even.

on edit: fixed some grammar

I wonder what would happen if you cut your salary requirements in half. Would they still reject you on your age or what? And if so, would they reject you if you slashed it in half again? And keep slashing until they hired you. Just as an experiment

“There is no ageism, because you could work for free or at a loss!”

No but it's a good question. Is it "out of two candidates with similar experience and salary requirements, companies will usually hire the younger one", or is it "companies don't want expensive experienced people because cheaper, less-experienced people are good enough"?

Thank you. Others took it so personally.

Your observation is spot on.

No problem, I have the same question. I'd like to know if it's "old people can't be good at the job" or "we can't afford experienced people". In my experience, it's more the latter.

Old people can be good. But young people are more likely to be hungry/ambitious and take ownership, which (at least has the appearance of) produces more/better outcomes.

I'm not somewhere you earn SV wages, so half my wage would be less than a junior gets paid in my country, and half that again would be less than I get for unemployment. Given market conditions I have dropped 10-15% off asking price but I don't think it is worth that much more for me to drop, given that if I can't get at that I probably can't get.

also, yeah, what the neighboring comment said - you do seem to think I should consider working for free...

In any case sounds like you dodged a bullet :-)

Hell, namespacing makes life easier even just for yourself. I wrote some browser automation in a previous role that was never going to be user-facing—it wasn't an extension—and it still proved useful to namespace things, both to clearly mark what we were inserting vs what was already there, and to avoid possible collisions.

I'm out of the frontend field - what would be common ways to handle CSS namespacing these days?

I don't know if this is what was meant by namespacing but i've seen '--{{ projectname}}-my-variable' before, so something like '--grammarly-rem' in this case.

or better yet: use shadow dom

Reply on news.ycombinator.com