231–240 of 242 posts
Earlier quoted context omitted.
The expression is "could not care less", meaning you're already caring the least possible amount.
"Could care less" is a valid idiom with established semantic meaning disparate from its syntactic meaning.
Earlier quoted context omitted.
The expression is "could not care less", meaning you're already caring the least possible amount.
You'd have to have been hiding under a rock the past few decades not to know that "could care less" has been linguistic currency for a long time now.
Earlier quoted context omitted.
I'm not sure if you were building a case towards something, but I definitely don't get where you're going. Variables being private or not-private is not particularly meaningful to encapsulation while exports are relying on underscore-conventions to protect your internal state. Modules being open-source or not is not particularly relevant to either question, nor is semver when your transitive dependencies don't upgrad…
All variables except those in the global scope are private, so you do not need underscore-conventions, simply do not declare the variable in the global scope! And when it comes to nodeJS modules, there are no global scope , all variables will be private unless explicitly exported. So instead of obj.__foo you just declare foo somewhere and it will not be possible to get or set it outside the module. Since all variable…
Alright, I get you now. I agree with you on this that it does allow for that sort of encapsulation--but, IMO, that's a bad kind of encapsulation; having to put fundamentally object-oriented data outside of the object strikes me as a profound routing around serious linguistic damage.
> Since all variables are private (function) scoped in JS you do not have to worry about shadowing (overwriting variables), especially when your functions don't have any outside couplings, witch is possible with (common JS) NodeJS modules as modules can be required from within functions or methods. They are just like any variable.
This, OTOH, is pretty much the same as any language with any kind of encapsulation. Maybe ES modules have finally approached parity, but it's nothing special.
> What do you mean by transitive dependencies ? I don't think there's a concept of transitive dependencies in NodeJS.
Every dependency of your dependency is transitive. Just go look in the node_modules directory of any of your dependencies! If you require X and it requires Y and Z, bugs in its version of Y or Z are suddenly your problem. And its upgrade strategy becomes your problem, too.
OTOH, in something like Maven, saying "no, use my version of this transitive dependency" is very straightforward.
> If you spend one hour to fix a bug in a open source project, you have probably saved other people thousands of hours of work, money, or frustration.
And my client doesn't care. If I'm working on my stuff, sure, I'll do that if it's the most efficient way to solve my problems. My clients do not give a single shit about this, though, and I have to build things they can deal with, not me.
So this is at best a misfeature. Primarily a bug.
Earlier quoted context omitted.
A few reasons I can think of off the top of my head: 1) Anything that can be effectively described as "blue collar" will probably be replaced by automation within 3-10 years depending on the job. 2) Creative thinkers should be valued more highly in the tech field than those that can just follow orders blindly. Very few tech fields emulate an assembly line and the ability to think for yourself and develop an alternati…
That seems fatalist to me. The idea of a work ethic is to avoid fatalism and enjoy the present moment.
I am 100% owner of an internet company making 7 figure profits annually. I am extremely secretive of my business, almost to the point that some would consider a pathology. However, I will divulge my hiring strategy, because even if everyone uses my method, there will still be many employees for me to choose from. I look to hire people who just need a job. People who are qualified, but not overly qualified. People I k…
Earlier quoted context omitted.
Super interested in this space. I checked your profile but only saw a keybase profile. A friend JUST hooked me up with an alpha tonight! What if I am infosec/netsec/whatever student and I watch a ton of Pluralsight on AWS and Docker and I am starting to build my own lab. Will people hire someone like me? I ask publicly because I assume I'm not the only one.
Possibly. Especially if you're using building the environment as a testbed for teaching yourself how to break into apps or how to automate security tools. About that... you know what's more likely to get you hired in the space? If you have no work experience in appsec but walk in and tell or show me a pattern for how you automated appsec testing in a build pipeline or QA process at home and describe the challenges yo…
Earlier quoted context omitted.
All variables except those in the global scope are private, so you do not need underscore-conventions, simply do not declare the variable in the global scope! And when it comes to nodeJS modules, there are no global scope , all variables will be private unless explicitly exported. So instead of obj.__foo you just declare foo somewhere and it will not be possible to get or set it outside the module. Since all variable…
> All variables except those in the global scope are private, so you do not need underscore-conventions, simply do not declare the variable in the global scope! And when it comes to nodeJS modules, there are no global scope, all variables will be private unless explicitly exported. So instead of obj.__foo you just declare foo somewhere and it will not be possible to get or set it outside the module. Alright, I get yo…
function takeScreenshot(webUrl) {
var webshot = require('webshot');
...
}
function visualDiff(imgPath1, imgPath2) {
var imageDiff = require('image-diff');
...
}Earlier quoted context omitted.
Wow, working with Google would be a dream come true for me. However, most of my experience is with Amazon ECS and Docker, tried a bit of Mesos.
Definitely apply - that's useful experience to have at Google. After all, what's the worst that can happen? :) Bear in mind that our hiring process is SLOW, so be prepared for it to take a lot of time. Best of luck!
I don't have anything to offer in the way of specific tech skills. I simply look for someone that is inquisitive, extracts satisfaction from solving problems in elegant ways, and has a strong motive to better themselves.
These qualities, and a few others, tend to transcend tech stacks and techniques of the week.
My most successful interviews have come through chatting with a candidate in an informal setting, presenting hypothetical situations that were actually challenges we've faced in the past here and there in the conversation.
I dropped the whiteboard and puzzle thing a long time ago and I've never had better engineers.
YMMV
(I do ask to see some code beforehand)
I am 100% owner of an internet company making 7 figure profits annually. I am extremely secretive of my business, almost to the point that some would consider a pathology. However, I will divulge my hiring strategy, because even if everyone uses my method, there will still be many employees for me to choose from. I look to hire people who just need a job. People who are qualified, but not overly qualified. People I k…
[0] https://hbr.org/2011/02/hire-for-attitude-train-for-sk
[1] https://www.eremedia.com/ere/hiring-for-both-attitude-and-ap...