psykotic

71 ms·

571.
by psykotic 15y ago
Beware: This article is filled with factual errors. I was making a list as I went along, and when I afterwards read the comments section I realized I had overlooked many more. That does not by itself affect the validity of the author's over
572.
by psykotic 15y ago
Rapid Software Development by Steve McConnell, the same guy who wrote Code Complete, is a great pre-XP, pre-Agile book on the software development process that covers the waterfall and spiral models, evolutionary prototyping and delivery, a
573.
by psykotic 15y ago
His xor-laden branchless min/max code in the fastest version so far, sort6_sorting_network_v4, is some seriously janky shit. It's making it harder for the compiler to generate good platform-specific machine code. That initial impression was
574.
by psykotic 15y ago
The lex program and its descendants are generally regarded poorly by Ken and Rob and others from their tribe of Unix systems programmers. The blog post suggests why. It is often faster and easier to write the lexer in C by hand. But they do
575.
by psykotic 15y ago
Yeah, I obviously dig it, but not everyone is on our wave length. Here's one reason having a random assortment of equipment at the office is useful. Loop a 53 pound kettlebell through a gymnastic ring strap and you have yourself a makeshift
576.
by psykotic 15y ago
> By working at the building site, for example, you train your body and your mind to respond in constantly changing situations You mean like most competitive sports in existence? Your comparison is also overlooking the physical and ment
577.
by psykotic 15y ago
This will strike most of you as weird, but I have a door-frame pull-up bar, gymnastic rings, a kettlebell, a jump rope and paralleletes for my office at work. I mostly use them on weekends or after normal office hours so it won't distract o
578.
John Carmack Interview: GPU Race, Intel Graphics, Ray Tracing, Voxels(pcper.com)
4 points by psykotic 15y ago|1 comments
579.
by psykotic 15y ago
A bunch of the people I went to school with as a young kid are now carpenters, bricklayers, mechanics, etc. A few are quite fit but that's because they're active outside of work. Most of them have big pot bellies, eat like shit, drink too
580.
by psykotic 15y ago
> It builds your constitution slowly but in a way that cannot be achieved in a gym, because it happens in a natural way, not artificially. That has an appealing ring to it but could you be more specific? What's a concrete physical task
581.
Protecting Freedom in the Patent System(youtube.com)
1 points by psykotic 15y ago|0 comments
582.
by psykotic 15y ago
> You're right that if you can create a nice, modular API and have it be slow-as-heck if it's model doesn't correspond to the underlying hardware or processes. Well, the underlying problem is that the design of an apparently abstract in
583.
by psykotic 15y ago
If you don't think ahead, it's easy to expose an API with implicit implications of poor or at least limited performance. The rest of your code base becomes dependent on it, and the month before shipping when you start really focusing on opt
584.
by psykotic 15y ago
Could you give a realistic scenario for the present case? Safari exploit that installs a keylogger on the victim's iOS device? It seems much more likely someone was hit by an exploit on their desktop machine with iTunes installed.
585.
by psykotic 15y ago
I read the first edition when I was in high school eleven years ago. Even back then it was considered the standard go-to book for learning the basics of algorithms and data structures. If your bookstores weren't carrying it, they must have
586.
by psykotic 15y ago
I said the greatest marginal benefit was from debugging. I didn't say it was the only one. :)
587.
by psykotic 15y ago
If you aren't fluent in assembly language, the biggest marginal benefit you get from learning it is the ability to read the assembly output from your C compiler for debugging or low-level optimization. For that purpose I've always recommend
588.
by psykotic 15y ago
At that point you're left with an underpowered desktop experience. It obviously depends on what work you're doing, but I'm happy with my desktop machine with 12 cores and 24 gigabytes of memory and wouldn't switch to a laptop for anything i
589.
by psykotic 15y ago
That's an odd attitude for a math major to have. When geometers in ancient times thought mechanical curves were lesser second-rank objects, that was obviously a counterproductive prejudice that for a long time retarded the development of ma
590.
by psykotic 15y ago
This classical result holds in some generality, e.g. you also cannot trisect every angle with straightedge and compass in the hyperbolic plane (an exercise in Hartshorne's book Companion to Euclid).
591.
by psykotic 15y ago
You don't need to pass it by address to a function. Something like this could trigger it: // region 1: // x is allocated to register r1 int x = 0; // store 0 to r1 jmpbuf jb; if (setjmp(jb) == 0) { // region 2:
592.
by psykotic 15y ago
The trick is to be careful about variable size and alignment and use wrappers around platform-specific load/store operations with the right memory ordering guarantees. There's no portable way to do this in C. But whatever you do, volatile w
593.
by psykotic 15y ago
What do you mean? You will get a compiler error in any case where there is a break or continue in an outermost while block. There's nothing odd or uncommon about that. Here's something closer to a real program: int main(void) {
594.
by psykotic 15y ago
Yeah, I've done low-level driver and microcontroller code in C as well. But these days I view everything through a multi-threading lens, so my default reaction when I see people bring up volatile is to assume they're talking about its use i
595.
by psykotic 15y ago
It will cause compiler errors, so it's not all that sneaky: int main(void) { while (1) break; return 0; }
596.
by psykotic 15y ago
That's cool example I didn't know about. Thanks!
597.
by psykotic 15y ago
That it would. Lots of raw memory-mapped IO and dependencies on compiler-specific interpretations of C semantics!
598.
by psykotic 15y ago
> I think #define volatile is by far the sneakiest. The only legitimate reasons for using volatile generally involve memory-mapped IO and POSIX signal handlers. C's volatile is nothing like Java's volatile and has very weak semantics. W
599.
by psykotic 15y ago
I hate it when a pedantic correction backfires. I should have been more careful. :) You're right to raise that question. It's a classical result of computability theory that there exists an undecidable problem that is strictly easier than t
600.
by psykotic 15y ago
> (much like NP-Complete problems are a subset of Complete problems) That sentence is messed up in a bunch of ways. You probably meant: "Turing-undecidable problems are a subset of NP-hard problems."

More ›