Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vvanders
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
36 ms
·
331.
▲
by
vvanders
6y ago
Yeah, they cover it pretty well in the podcast. By the numbers NUMMI did well however to achieve those figures they upended many traditional roles and couldn't get the leadership in GM to get on board. There's a great little footn
332.
▲
by
vvanders
6y ago
Another great perspective is This American Life's episode on the NUMMI plant[1]. Coming full circle from Deming back to GM. [1] https://www.thisamericanlife.org/561/nummi-2015
333.
▲
by
vvanders
6y ago
Have you ever used restrict in anger? I've done it when we really needed that performance for an inner loop(particle system). It can be a real bastard to keep the non-alias constraint held constant in a large, multi-person codebase and
334.
▲
by
vvanders
6y ago
Yeah but can I get a metric ton of benchmarks at that 45w setpoint? I don't really see the reason in paying for a 100w TDP premium if I'm just going to scale it down to 65w.
335.
▲
by
vvanders
6y ago
TDP matters a fair bit in SFF(Small Form Factor) PCs. For instance the 3700x is a fantastic little CPU since it has a 65W TDP but pretty solid performance. In a sandwich style case you're usually limited to low profile coolers like Noc
336.
▲
by
vvanders
6y ago
I don't think Threadripper is a hard requirement for ECC. There's some pretty reasonable TDP processors if you step down from Threadripper.
337.
▲
by
vvanders
6y ago
Dalvik and ART have different behaviors than traditional Java VMs. Dalvik is aimed at low memory devices, ART trades some memory for speed but still is significantly different(i.e. it doesn't do escape analysis). As always benchmarking
338.
▲
by
vvanders
6y ago
> The common programming languages used on phones are very memory-allocation-friendly. I would hardly classify Dalvik or ART as "allocation friendly", they don't perform escape analysis and if you do it constantly you'
339.
▲
by
vvanders
6y ago
Constrained embedded systems cover a broad range of things up to and including your phone. There's few things I hate to see more than a flat profile from memory allocation or cache misses. The good news is that flatbuffers[1] is a reas
340.
▲
by
vvanders
6y ago
Error correction only makes sense if the latency of the read/write is long(i.e. spinning physical medium, co-sharrd radio channels). FEC isn't free(~2x overhead per bit recovery if I remember right) so if your error rates are infr
341.
▲
by
vvanders
6y ago
> Software architecture is fundamentally about understanding the shape and structure of the problem domain, understanding the capabilities of your engineering tools, and creating an architecture where both domains support each other. You
342.
▲
by
vvanders
6y ago
You're free to ignore Conway's law[1] and the like at your own risk. I would argue that if software or organizations were straightforward to apply such rigor that you'd see something closer to hardware where formal verificati
343.
▲
by
vvanders
6y ago
All it takes is a neighbor with a router on the same channel as you or a little bit of rf noise(usb3 has a clock rate that tends to do this) and the whole thing comes tumbling down. Back where I did gamedev we designed gameplay specifically
344.
▲
by
vvanders
6y ago
OS threads cost you stack space, among other things. There's a reason that most OS native UI frameworks use some sort of event polling structure(WNDPROC[1], Looper/Handler[2], etc) because they're a nice structure for efficie
345.
▲
by
vvanders
6y ago
If I recall correctly the 787 bypasses the use of bleed air and similar systems by using electrical power instead to pressurize the cabin. That comes with its own set of interesting issues but I wonder if you could get some useful data from
346.
▲
by
vvanders
6y ago
> Yes, big-O notation hides constant factors like cache coherence but the solution isn't to analyse things less. Yet I run into good developers with good CS backgrounds all the time who were never exposed to cache hierarchies in t
347.
▲
by
vvanders
6y ago
My strong statement was in counter to your assertion that the empirical evidence holds that you'll need math and cs in spades. Most of my graphics works was better served by an understanding of hardware(pipelining, SRAM vs DRAM caches
348.
▲
by
vvanders
6y ago
I've done both graphics and embedded systems. I don't think any of that is true. In fact I found most the formal education around graphics to be outdated or disconnected from the reality of how systems are built(mostly due to trad
349.
▲
by
vvanders
6y ago
> But those who are not comfortable with the foundational theory stuff just don't see it and don't even think to approach the problem in that way. Or maybe all that "foundational theory" is oblivious to cache hierarch
350.
▲
by
vvanders
6y ago
I'm sure that was your true intent, but the way you framed it made it seem like it was in exclusion(the dismissive "Cool." at the top didn't help). At the risk of sounding patronizing as much as we'd like to everyth
351.
▲
by
vvanders
6y ago
I mean shouldn't you feel bad if you're trying to discourage active engagement in a topic if one doesn't do it in a specific "correct" way? Personally I've found a diverse set of viewpoints to be incredibly val
352.
▲
by
vvanders
6y ago
By framing the IDE as a crutch, that's very much in the gatekeeping category.
353.
▲
by
vvanders
6y ago
Or you could just put a magnet and a notch on the top of the hammer[1]. [1] https://duckduckgo.com/?t=ffsb&q=hammer+nail+magnet&iax=imag...
354.
▲
by
vvanders
6y ago
I dunno, in the CUT space you've got the 3-point hitch, SSQA, hydraulic remotes and a bunch of other standards that make implements pretty interchangeable. Makes brand lock-in pretty difficult. If I had the option for either a pure-ele
355.
▲
by
vvanders
6y ago
Its definitely a factor, most people I know out here who bale run multiple tractors so they can handle one or two in the shop if it's during a critical time. We've got a Kubota CUT, when rats chewed out the writing harness we were
356.
▲
by
vvanders
6y ago
Oh I worked on titles in that era too, and on other oddball platforms like the PSP :). Without getting into the weeds too much you just weren't doing much with the single CPU core on the PS3. As soon as you booted anything of note it w
357.
▲
by
vvanders
6y ago
The answer for that one is real simple, it was mostly a function of what your first target platform was. Back in that era X360 had the edge by coming out slightly ahead schedule wise so most engines targeted that first and then had a brutal
358.
▲
by
vvanders
6y ago
SoC doesn't make as large of a difference as you'd think. The only place you really get hammered is if your moving a lot of memory between separate memory domains. As a real world example the X360 had a unified memory architecture
359.
▲
by
vvanders
6y ago
Been there, done that, got the t-shirt. Once with a 6 months crunch, second time closer to 10 months of 14 hour days. That was enough for me to swear off the entire industry despite working towards it for most of my younger life. Saw it wha
360.
▲
by
vvanders
6y ago
I remember quite a few aimbots back in the day would MITM packets so there are some reasons you might want to do it from a defense in depth perspective.
More ›