eacapeisfutuile

5 ms·

31.
by eacapeisfutuile 2y ago
It would have zero value in every process of vetting someone. People don’t care about years of verification in the form of degrees, who do you think will care about some “license to fucking code” given for reading some garbage pdf
32.
by eacapeisfutuile 2y ago
Well also now entire companies fail quicker instead. It is useless because no one will read it or use it as any type of benchmark, probably rightly so here. There is a version of this at every company, just more relevant, also already not b
33.
by eacapeisfutuile 2y ago
It is not known what the timeline could be, so injury seems fair to me. By the same analogy it may lead to mental health problems “down the line”.
34.
by eacapeisfutuile 2y ago
Scope change is really not a foreign concept in the field of software engineering, including politically driven
35.
by eacapeisfutuile 2y ago
> Every company I go to, the base of knowledge of all the engineers is a complete crapshoot Sounds like unfortunate companies to go to. > much less teach them about it on the job That is literally how and where people learn the job pr
36.
by eacapeisfutuile 2y ago
You can erase JavaScript from this title and have equally valid points.
37.
by eacapeisfutuile 2y ago
So… most likely it is a “typo” or edit-mistake or similar. If you understand what they meant then all is good, no?
38.
by eacapeisfutuile 2y ago
Please no, this is a solved problem for decades, it will not actually multithread the DOM and more likely just add overhead.
39.
by eacapeisfutuile 3y ago
Yeah I think this is the common case. I think we usually trust that dependency A took a look at their dependency B and C before releasing a new version of A. And even if properly reviewing our bump of A, how often do we check out changes in
40.
by eacapeisfutuile 3y ago
Yes but the distribution likely depends on it, making it wider spread even without the middleman dependencies.
41.
by eacapeisfutuile 3y ago
I think this almost the default even outside of FAANG, of course there’s companies not applying it.
42.
by eacapeisfutuile 3y ago
Lack of proof in any direction is approaching the core issue here.
43.
by eacapeisfutuile 3y ago
That is very subjective, and far from what I’ve seen.
44.
by eacapeisfutuile 3y ago
Yes, this is anecdotal, but I think there’s a fair share invested into it (from my experience)
45.
by eacapeisfutuile 3y ago
> That arrangement is deemed a “misconfiguration” by that provider, and we’ve been receiving alerts about it since rolling it out So 90 days of alerts about certs, and then certs fail?
46.
by eacapeisfutuile 3y ago
Does that mean we don’t look into changes in dependencies at all when bumping them?
47.
by eacapeisfutuile 3y ago
I’m not sure this would be smaller scale? At least probably too early to tell?
48.
by eacapeisfutuile 3y ago
Isn’t it a bit ironic with how much code everyone depends on that can freely be altered by some unknown party, while so much time goes into code reviews to verify internal changes at most companies.
49.
by eacapeisfutuile 3y ago
Yes but if that’s the sentiment how is this not as problematic as the npm ecosystem.
50.
by eacapeisfutuile 3y ago
Generally yes, but ripping all conditions out of SECURITY.md should at least raise an eyebrow?
51.
by eacapeisfutuile 3y ago
Why is that accepted? Serious question
52.
by eacapeisfutuile 3y ago
Nice work, a somewhat hilarious, albeit understandably stressful way to surface a few systematic issues.
53.
by eacapeisfutuile 3y ago
Thank you for the thorough response, that makes sense
54.
by eacapeisfutuile 3y ago
In what way? Isn’t a big part of observable the community provided content, which does not seem to be what this tool provides?
55.
by eacapeisfutuile 3y ago
Why do you need to bundle these, is it to simplify iterating on frontend and data loaders simultaneously? Why not run them separately?