HNHacker News
TopNewBestAskShowJobs

DalekBaldwin

434 karma · joined February 3, 2013

submissionscomments
DalekBaldwin··on Can Programming Be Liberated from the von Neumann Style? (1978) [pdf]
"You always need more bits of axioms than of program if you want to prove theorems about your programs."

Fascinating. Is that a quote? I've never seen it stated that way. I think something about it just clicked for me.

DalekBaldwin··on Banksy Dismaland Show Revealed at Weston's Tropicana
I found it rather peculiar that someone started spray-painting over one of his freshly painted works and was wrestled to the ground because of it. [1]

If Banksy's work is meant to raise the question of who in our society gets to determine what images invade everybody's retinas in public spaces [2], those bystanders provided an answer: whoever is hip enough to get people to defend their images. At that point the artwork was complete.

[1] http://www.dailymail.co.uk/news/article-2465617/Banksy-fans-...

[2] http://www.davidairey.com/banksy-on-advertising/

DalekBaldwin··on Generative testing for JavaScript
One feature I've added to my own generative testing tool [1] to mitigate this problem is to save the random value that made the test fail and add it to a set of deterministic test cases that always need to pass before the tool will try any new randomized cases.

Of course, if you discover a test failure on a very low-probability corner case, other people working on their own branches probably won't trigger it. But with the right workflow, the situation shouldn't be all that different from adding a regular test case, which could always fail once attempt you merge it with someone else's code that wasn't written against it.

[1] https://github.com/DalekBaldwin/check-it

DalekBaldwin··on Better Than Raising the Minimum Wage: Expand the Earned Income Tax Credit
Any non-market action will distort market forces. What he means is that the EITC is a softer kind of distortion. Since the EITC is essentially a matching contribution to the employee's earnings, it still allows decisions about wages to be made at the margin, as opposed to a minimum wage which mandates a hard cutoff.
DalekBaldwin··on Inside the D-Wave Fridge [video]
I've taken courses in quantum mechanics and quantum computing, and I put in the effort to try and actually develop some intuition as to how they work, but I still don't have the slightest clue as to how you could build the actual physical substrate for performing those kinds of computations.

Then again, I don't feel like I understand classical computers all the way down to the metal, even after taking courses that supposedly explained that. No matter how much I learn, my mental model of real-world computing is not all that different from what it would be if I had simply decided to believe that, at the bottom, code just runs on magic.

DalekBaldwin··on Ask HN: Who is hiring? (May 2015)
Who's the contact for these positions? Your jobs page doesn't list anything in the LA area.
DalekBaldwin··on Alan Kay on Messaging (1998)
AOP also encompasses techniques you can't find in CLOS/MOP. The analogues to before/after/around methods are the easiest concepts to implement and reason about, so those are what popular language extensions tend to emphasize. But if you look at the original AOP papers describing Reverse Graphics, you'll see an AOP system used to liberally restructure the control flow of the entire base program, not just augment its behavior. It was an early version of what you can see now in something like the Halide language.

> I believe MIT first year CS switched to Python in part to deal with this resistance.

In part. The full story is a bit more depressing: http://www.wisdomandwonder.com/link/2110/why-mit-switched-fr...

Most of the other top universities that had used SICP also switched shortly after MIT.

DalekBaldwin··on Common Lisp as a Scripting Language, 2015 Edition
I wonder if the scales would tilt more in favor of separate images if you added a good tree-shaking step. You can bang out useful scripts pretty fast by pulling in a few helper functions from large libraries, but the more scripts share a library, the less functionality you can discard from the final image.

If you can cut the size of the core language's image in half with just a simple method like this, you could probably get impressive results using more sophisticated methods on images requiring a lot of libraries: https://gist.github.com/burtonsamograd/f08f561264ff94391300

DalekBaldwin··on LA's Proposed Parking Signs
Doesn't matter. The rules for parking spaces in LA are usually complicated enough that you have to stop to read them anyway.
DalekBaldwin··on Not everything is an expression
The specific problem is that it's buggy. But the general problem is that it's a massive, fragile hematoma of duplication [ctrl-f "hematoma": http://people.engr.ncsu.edu/efg/517/f00/syllabus/annotations...], which makes the bugs buggier.

A macroexpansion facility works more like a framework than a library. Each macro you define is basically a callback function triggered when the compiler sees a form with a particular symbol at the head. You want to be able to describe what should happen in particular situations you're interested in, without having to specify anything about other situations. A code walker spoils that separation of responsibilities because it has to reimplement large parts of a macroexpansion framework just to make it possible to add a few new features which are then used in conjunction with the original framework.

The potential for bug contagion is quite high, because any single bug's effects aren't localized to the few forms that make use of the extended functionality you've rigged up. This is tantamount to introducing a bug in the language implementation. If you're expanding something like (my-macro (... (my-other-macro))), a bug in your code walker can break the intermediate code. This might be acceptable if you're just using it to write a couple of one-off macros that don't trigger any weird corner cases and are only used in the same project in which they're defined. But if you're creating a general-purpose DSL like iterate that you intend for people to use in all sorts of situations you never anticipated, it's not. In fact, the same bug is more dangerous as part of a code walker than it would be as part of a Lisp implementation's internals. If it's in the implementation, at least it would show up consistently whether the vulnerable code is wrapped in your macro or not, making easier to identify, document, and manage the problem. And probably easier to get somebody to fix, because the implementation ought to be better maintained than the walker.

These are not merely hypothetical concerns. Some projects already rely on macroexpand-dammit working in the quirky way it does; Masataro tried to have his improved version supersede the existing version on Quicklisp, but it broke some packages that were using it: https://github.com/guicho271828/macroexpand-dammit/pull/4#is...

Sometimes I use those packages too, so instead of using his version with the fix I submitted, it's actually less of a headache for me to apply my fix using a wrapper package on top of the Quicklisp version, duplicating some of the code which itself duplicates what Lisp already does. The original duplication problem led to bugs which led to the need to load two separate implementations which led to a name clashing problem which justified additional duplication.

Also, I tried to implement that same iter example using a similar trick before, and I see that your code generates the same mysterious output, at least on SBCL:

  ; compilation unit finished
  ;   caught 1 fatal ERROR condition
A fatal error during compilation, yet it clearly compiled and ran. What was the error? I don't know, it looks like something in the code walker muffled the details. Does it matter? Could it matter in any other scenario? Something about macroexpand-dammit doesn't play nice with the implementation, but we don't know what, why, or how, and it makes it more difficult to use the very language features that would normally help us find out.

I think a lot of critiques of the "bipolar Lisp programmer" [http://www.lambdassociates.org/blog/bipolar.htm] are overblown, but in the case of these kinds of tools, they're justified. These kinds of techniques will always be restricted to obscure one-off software projects unless they're supported by core language features like what rntz and Masataro are proposing. The designs of macro systems are optimized for making it easy to make small tweaks to the language to fit the particular problem at hand. They're not quite as flexible as something like the MOP. If you try to use a facility designed for making small, local interventions in the language to write very general language extensions which themselves make broad, global interventions in the underlying system for making small, local interventions, you're gonna have a bad time.

DalekBaldwin··on Not everything is an expression
The macroexpansion hook isn't nearly as powerful or useful as it could be because the process of macroexpansion is not recursive. Although expansion functions can access information about the lexical environment via an &environment parameter, the invocations of those expansion functions do not share any dynamic context with other invocations at nodes above or below them in the syntax tree.

Here's a more thorough summary of the problem: http://qiita.com/guicho271828/items/07ba4ff11bff494dc03f

DalekBaldwin··on A Xenon flash will cause the Raspberry Pi 2 to freeze
Looks like there's some truth to the belief that a photograph steals its subject's soul.
DalekBaldwin··on Show HN: A modernized and annotated code companion to Paul Graham's “On Lisp”
The original nonprofit software license isn't suitable for distributing the code through Quicklisp, but I thought I'd put this here for everybody who's wanted to work through the book before and has run into snags. Enjoy!
DalekBaldwin··on Building a better and more diverse community
Your proposed test for bias would be reasonable for a traditional school, but although the linked post focuses on how Hacker School has fared in regard to gender diversity, Hacker School stands out more for its diversity of programming skills and skill levels, from near-beginners to CS PhDs, as part of the goal of maximizing how much the students can learn from each other. You're overlooking this important part: "We accept every person who applies who we believe we’re a good fit for and who would benefit from and contribute to Hacker School." This is of course ultimately a subjective standard, and any serious attempt to evaluate their success in meeting it is bound to be highly subjective as well. You might think that focusing less on raw programming ability would be an excuse for bias, but from what I saw in the batch I attended last year they achieved a very healthy balance along those dimensions for both men and women. It's to the facilitators' credit that if you removed either all the men or all the women from my batch, it would still be the most well-rounded group of programmers I've ever worked with, which again is admittedly subjective, but even as a white male as prone to statistical nitpicking as you are, I can't think of a better way to judge that they really do admit men and women, as individuals, in a way that aligns with their more holistic objectives for HS as a community of individuals.
DalekBaldwin··on New Requests for Startups
> Sadly, one of the biggest hurdles is self preservation because software developers don't want "software development accessible to the widest part of our society". I hate to say it, but there are Luddites among us.

It's a strange form of Luddism that seeks to limit opportunities to integrate the existing skills of the labor force into the structure of production. We don't have much in the way of unions or guilds, so perhaps the only effective way to restrict the labor supply is to keep the tools user-unfriendly.

DalekBaldwin··on Pascal Costanza's Highly Opinionated Guide to Lisp (2002)
Pascal Costanza exemplifies a lot of what I love about Lisp. It's interesting to note that not too long before this was written, he was highly opinionated about the language in a very different way:

> I have participated in one of the first Feyerabend workshops, organized by Richard Gabriel, one of the main drivers behind the original Common Lisp effort. I have also read his book Patterns of Software around that time. Later we had a small discussion in the patterns discussion mailing list. He tried to promote Lisp as a language that has the "quality without a name", and I made some cursory remarks about Lisp's unnecessarily complicated syntax, just like anybody else who doesn't get it yet.

> To me, the most important comment he made in that discussion was: "True, only the creatively intelligent can prosper in the Lisp world." The arrogance I perceived in that comment annoyed me so much that it made me want to learn Lisp seriously, just to prove him wrong and show him that Lisp is not as great as he thought it is. As they say, the rest is history.

[http://lisp-univ-etc.blogspot.com/2012/04/lisp-hackers-pasca...]

Once you begin to peek under the hood of the language, there's no end to the secrets it starts revealing and no end to the intellectual rewards it brings to curious (and yes, even arrogant) newcomers. P-cos has since gone on to do some of the most interesting work in Lisp since the ANSI standardization, such as ContextL. It would be interesting to see a substantial update to this guide in light of his more recent work.

DalekBaldwin··on The Most Terrifying Thought Experiment of All Time
We should all just commit to believing that Box A's label actually says "Devote your life to helping create Roko's Basilisk... who will arrive in the form of the Stay Puft Marshmallow Man".
DalekBaldwin··on XKCD: Research Ethics
Going further: what if this was broad exploratory study, not meant to test any specific hypothesis? What if they rated posts based on thousands of features, a parameter space large enough to guarantee they would find plenty of correlations (both spurious and substantial), and randomly perturbed each user's feed and monitored how the features of their contributions changed? I would expect that they already do this, and from the very small amount of detail I've seen in articles about the mood factor so far, I wouldn't be surprised if this was just one of the more interesting correlations that fell out of that sort of process.
DalekBaldwin··on Visualizing Algorithms
I can't find any copies of these papers that aren't behind a paywall. Is there any record of what the visualizations looked like?
DalekBaldwin··on Bret Victor: Seeing Spaces [video]
Agreed, I've been thinking too much in code, not enough in English.
DalekBaldwin··on Bret Victor: Seeing Spaces [video]
Especially for programming, the tools have to be narrowly tailored to the examples since you're constantly wrestling with the specter of Turing-completeness. Any given program is an instance of an infinite number of more general classes of programs, and it's the tool designer's job to choose which dimensions of the design space are meaningful and important enough to be worth simultaneously visualizing the consequences of possible alternatives. I think it's going to take some very judicious integration of recent work on modularity-enhancing programming paradigms into the design of reflective language implementations before it becomes tractable to build responsive special-purpose reflective tools on top of a generic infrastructure. Or at least that's the strategy I'm trying.
DalekBaldwin··on Will you drown?
Another depression-oriented game. Well, thanks to parallelization, I got to make love during work hours, so I must say my life wasn't all bad.
DalekBaldwin··on Ask HN: What source code is worth studying?
Honestly, aside from learning to express a few extremely specific patterns in your language of choice concisely and elegantly and reminding yourself of the existence of certain libraries and utility functions so you don't accidentally waste time reinventing them, I think reading source code is a pretty useless exercise unless you also have a detailed record of how that source code came to exist in its present form. Until there is some revolutionary new tool for generating a human-understandable narrated history of large-scale design decisions from a source control history, your time will almost certainly be better spent reading textbooks that incrementally develop a piece of software over several chapters. Even that is cheating -- the authors know exactly where they want to end up and they won't include all the missteps they made when they first started writing similar programs. But it's still loads better than the alternative. Just as sitting in a law school library absorbing an encyclopedic knowledge of the law won't really train you to make arguments that will fly in front of a judge, reading a code base as a dead, unchanging document won't teach you what it is to live in that code.
DalekBaldwin··on OkCupid urges users to abandon Firefox
Are you in British Columbia?

http://dailyxtra.com/vancouver/news/bcs-new-law-erases-line-...

> The qualifications for a common-law relationship, Dahl says, are much lower than they once were. To have a “marriage-like” relationship in BC, you do not have to share a bank account, call yourselves married, be sexually monogamous, file taxes together, or even cohabit all the time. To “hold yourself up to the community as a couple” and share a home is probably enough.

By that standard, it seems like it would be pretty easy for an ex-roommate to sue you for half of your wealth.

DalekBaldwin··on Introductions to advanced Haskell topics
I'd say it is in fact a familiar abstraction (as the "You Could Have Invented Monads" article shows) that's presented in an unfamiliar way with unfamiliar syntax. Taking something you already understand intuitively and learning to express it in a new formal framework (like much of Haskell) is often harder than learning something brand new in a formal model and slowly developing an intuition for it (like much of physics). Sometimes gaining a formal understanding enriches your intuition and vice versa, but I haven't experienced anything like that with Haskell so far.
DalekBaldwin··on 8402: 2048 from the other side
I beat it on the first try with nothing but 2's before I read the instructions and found out I could use 4's.
DalekBaldwin··on New Health Law Frustrates Many in Middle Class
Sure. You could spend that time writing posts on Hacker News that influence more than one voter.
DalekBaldwin··on New Health Law Frustrates Many in Middle Class
That's a miscalculation of opportunity costs. You are throwing away the time you could have spent doing better things than voting. How many times have you cast the deciding vote in an election?
DalekBaldwin··on Why Bitcoin Will Never Be a Currency
Is it sad that they would believe those sentences, or sad that those sentences are even necessary? I can't tell whether you agree with it or not.
DalekBaldwin··on Microsoft Research Publications
I'm not an academic, but I read a lot of scholarly publications in computer science and I have never seen a single reference to a patent in any of them. Usually I only discover that something is patented or patent pending later, after some heavy Googling.

I copied down this quote from somewhere earlier this year but I can't find the source now: "One of the things they tell us developers here at Microsoft is that we should never read any patents. That's because you're liable for triple damages if you knowingly infringe on a patent."

← PreviousPage 3 of 4Next →