141–150 of 171 posts
Earlier quoted context omitted.
History: Eternal September or the September that never ended is Usenet slang for a period beginning in September 1993, the month that Internet service provider America Online began offering Usenet access to its many users, overwhelming the existing culture for online forums. -- Wikipedia
The irony of this comment is palpable.
Honestly, don't depend on central repositories for daily availability. Especially if you are doing CI that redownloads everything from scratch. Use something like artifactory to cache the repository you are using: https://www.jfrog.com/confluence/display/RTF/npm+Registry
That’s been my experience anyway with local servers. We’ve had a lot of problems.
Edit: vendoring dependencies, on the other hand, is very reliable. But it doesn’t work well with DVCS.
Earlier quoted context omitted.
In addition to the first reply to your post, you may find it strange but having dress codes actually help promote diversity in workplaces.
How?
https://hackernoon.com/for-inclusive-culture-maybe-less-is-m...
Earlier quoted context omitted.
I would not recommend to use the Taobao registry though. This is operated by a Chinese company. Aside from the cybersecurity concerns, if it's hosted in China you'll be getting bad latency.
It's just a mirror service address, the NPM package is the same. Worrying too much about cybersecurity is a bit of a storm in a teacup.
Earlier quoted context omitted.
How?
It helps focus the culture on the business over other social queues and aspects, it removes the anxiety that different social groups will have with that workplace. https://hackernoon.com/for-inclusive-culture-maybe-less-is-m...
FYI, the word you're thinking of is "cue", not "queue".
I’ve been considering checking node_modules into source control for some time now, has anyone else done that successfully? There would be a variety of benefits: 1. Eliminate redownload of packages on every CI build 2. Reduce the amount of gigantic IO operations from unpacking the tens-of-thousands of files sitting in node_modules. 3. Better security: code checked in can be audited better if not downloaded every singl…
https://blog.isquaredsoftware.com/2017/07/practical-redux-pa...
Earlier quoted context omitted.
Why would anyone use "&c" considering that it doesn't actually save any key presses?
Keypresses is a pretty poor metric to base communication upon. It annoys me to see "w/" and "w/o" anywhere except Twitter. The meaning isn't clear to many non-native speakers, and it's jarring — we recognise the most common words by the shape of the whole word, so it's easier to read "with" and "without". "&" is a ligature for the letters "et". A traditional way to handwrite it, other than as &, is a "crossed epsilon…
Earlier quoted context omitted.
How?
It helps focus the culture on the business over other social queues and aspects, it removes the anxiety that different social groups will have with that workplace. https://hackernoon.com/for-inclusive-culture-maybe-less-is-m...
Earlier quoted context omitted.
> [..] and even how they dress. While there are many points in your post that I agree with, we really should stop worrying about how people dress. If it's a developer sitting behind a computer screen all day long with zero customer contact whatsoever, he really shouldn't be forced to wear a certain dress code just to satisfy someone's standard of professionalism. Such feelings are in similar spirit as "woman should n…
> conditioning by society. There is a limit. I'm sure you have one too if you really think about it. Is it tattoos all over the face? What about sandals? Or shorts? Or going bare-feet around the office. I don't know... It's about people giving me money for work. I don't feel like I can go to work dressed like any given Sunday.
And why not? As you said: they are giving us money... for work. Not for playing dressing up.
If they expect otherwise, they should be clear about it up front and give a good reason to give up on that freedom while we work for them.
Honestly, don't depend on central repositories for daily availability. Especially if you are doing CI that redownloads everything from scratch. Use something like artifactory to cache the repository you are using: https://www.jfrog.com/confluence/display/RTF/npm+Registry
I think that's the issue of cost/reward. The cost is - N developers can't work for X hours - or the company can't release new versions due to CI dependency on the registry. - or the registry removes a package you were using - or the existing package contents changes to something malicious BUT you pay this price very occasionally and if you're a small shop, the cost is often negligible. On the other hand, maintaining…