Joky

12 ms·

91.
by Joky 8y ago
> They didn't because AP2 hardware wasn't capable of that You'd have to elaborate as of why this would have been the main reason (vs other possible reasons...).
92.
by Joky 8y ago
The problem is that with a L2 system like the current autopilot where you have to take over when you exit a highway and encounter for example a traffic light, you trigger effectively a "disengagement" while operating with the expe
93.
by Joky 8y ago
But you don't need to train in a car, so you want to optimize cost/power for pure inference. Similarly if all you want to do is cheap and efficient inference, it isn't clear to me that TPU V1 are obsolete today.
94.
by Joky 8y ago
> the description you’ve given above, which is a really nice summary, would be so utterly bonkers advanced-sounding and deeply complicated to average workers But this description was very technical, another way to approach it is: keep in
95.
by Joky 8y ago
> If medical care is free It is never "free" (almost nothing is). Costs are usually covered through (forced) mutualization (usually through taxes).
96.
by Joky 8y ago
LLVM is an example that this black-and-white view of the world does not generalize.
97.
by Joky 8y ago
There are no “puzzles”, but problems to solve. I expect that things like this string search are entry level / new grad kind of question. Someone more senior with more experience should have different kind of problems to solve. I certai
98.
by Joky 8y ago
It's blurry to me what it mean for including a libc++ header though? This is not "your source code" but LLVM inline code. How is it different from including a header from LLVM itself?
99.
by Joky 8y ago
It seems like you're making a dichotomy between corporations and the community. However corps are a big part of the community! They are leveraging LLVM in many different products, and individuals in the community are frequently paid by
100.
by Joky 8y ago
What does "self executing" mean in this context? I assume there is no JIT compiler embedded in the license right ;)
101.
by Joky 8y ago
The problem to me is that this is used too often as an excuse by sloppy developers to not care about the quality of the software. It is too easy to overlook the impact 6 months down the line of the lack of design/readability of some pi
102.
by Joky 8y ago
> Making signed overflow/underflow trapping behavior would also be acceptable. You can just add the right compiler flag if this is the right tradeoff for you application (it isn't for everyone).
103.
by Joky 8y ago
Actually I discourage my colleague to use unsigned especially because they can overflow. The problem with overflow is that most of the time it is a program bug if there is an overflow that wasn't intended. Using signed arithmetic m
104.
by Joky 8y ago
Even there, you need a fuzzer that can generate code that actually execute and does something you can observe. Otherwise the output of a C compiler (as in the binary itself) is expected to differ even between different versions of the same
105.
by Joky 8y ago
See the "trophies" here: https://llvm.org/docs/LibFuzzer.html#trophies Also: https://github.com/google/oss-fuzz
106.
by Joky 8y ago
See also for in-process fuzzing: https://llvm.org/docs/LibFuzzer.html
107.
by Joky 8y ago
Just as another data point: I have been looking at it like you in the past, but now I’m getting old enough that I worked with enough engineers to realize that whole experience has a general correlation with seniority, there is a huge vari
108.
by Joky 8y ago
Why not look at the source to get the right information? https://www.42.us.org/42-admissions-overview-requirements-pr... https://www.42.us.org/42-admissions-overview-requirements-pr... > I AM NOT BETWEEN
109.
by Joky 8y ago
You need to do 3D touch on the keyboard itself.
110.
by Joky 8y ago
Not sure if you’ve been driving one for some real time, it is very practical, I wouldn’t go back to any of my previous car.
111.
by Joky 8y ago
Bolt hasn’t much to do with clang/LLVM I think, unless you’re thinking it could be integrated with lld, the linker that is developed under the LLVM umbrella?
112.
by Joky 8y ago
But your camera manufacturer may log on a dedicate flash memory inside the camera some logs about pixel defects, and claim that they copyright these data.
113.
by Joky 8y ago
Yeah I just clarified because of the part that said "for France's system", this part of the tax is not what's paying for the welfare part of the "system". According to https://argent.boursier.com&#x2
114.
by Joky 8y ago
> Another good example are monorepos. A decision maker sees a headline about Google and Facebook using monorepos and mandates his company to switch. Unfortunately he didn't know that `git` does not scale well with the size of the re
115.
by Joky 8y ago
> But then it is not income tax, which is the percentage of what was discussed. On the contrary, this matches what is "Income tax" in the US. > If you want to account for everything that is removed from your salary between g
116.
by Joky 8y ago
45% is only the (higher bracket) "federal taxes" (France isn't a federal country) that don't include all the welfare contributions which are taken from your salary (22% IIRC) and also the higher employer contributions.
117.
by Joky 8y ago
Not including employers contribution when comparing countries is just non-sense to me: the only number that matters is the total cost per added employee for a business, and on the other side for the employee the after-tax money that remains
118.
by Joky 8y ago
The merge won't bring more changes than if the PR was squashed in a single commit though. Hopefully if you have a test broken and the PR merged two commits: one that refactored the code and the second one that leveraged the refector to
119.
by Joky 8y ago
This is not about serializing builds on master, but builds on the PR before they get merged on master. If you have a few hours of test plans, you can't serialize every PR one after each other.
120.
by Joky 8y ago
That's not very scalable: with a team of 100 developers merging on average 100 PRs a day, you have lot of concurrency. Imagine everyone want to merge at the same time, only one can, the 99 others have to re-run the build/tests. Th

More ›