HNHacker News
TopNewBestAskShowJobs

dgreensp

3,476 karma · joined April 10, 2007

David Greenspan
submissionscomments
dgreensp··on Learning Dexterity
In 2015, it was commonly thought that it would still be decades before a computer could beat a top human player at Go. Now, you are calling it “easy,” because it’s been done.

The first chess program was written by Alan Turing on paper between 1948 and 1950. He didn’t have a computer to run it, but he could still play a game with it by stepping through the algorithm by hand. In 1997, Deep Blue beat Kasparov, using traditional algorithms and not deep learning.

Clearly there are differences between these problems and dexterity. Chess, for example, can be described relatively simply using logic, and there is no dynamic or physical element; a rudimentary player can be written using pencil and paper; a winning player just needs enough compute power, apparently.

More importantly, there is a technology curve. You are asking about the ultimate limits of a technique moments after its first success puts it at the low end of the spectrum of human ability. Give it a decade or two.

I am just shocked the video was real-time and not sped up like so many of these videos are (eg watch a robot arm fold a shirt in thirty seconds when you play it at 5x speed).

dgreensp··on There Is No Such Thing as Unconscious Thought
Brains don’t solve problems by manipulating symbols. None of these layers are intended to be synonymous. Meditation is basically 4 and 1, with 2 and 3 coming and going. Driving is intended to be an example of just 1 and 2. Saying that driving is a “skill” and “we know it can be done unconsciously” suggests to me that other skills can be done unconsciously, too. A lot happens in ten minutes of driving; options are weighed and decisions made. Music composition and doing mathematics (stopping short of the actual symbols) are also habitually developed skills over years of regular practice.

Edit: I just remembered that Jonathan Blow reports programming “unconsciously” in the same manner as the driving example. Also, on a good day my consciousness is not devoted to “problem-solving” every second of the day; that would be miserable. I don’t see why conscious awareness is seen as so necessary for thought, the only explanation for me being that many people experience themselves as being their thoughts and not their awareness. It is a journey many of us are on.

dgreensp··on There Is No Such Thing as Unconscious Thought
There are plenty of times in the day or night where we may be "thinking" about things but not attending to our thoughts very much or at all, such as while dreaming or zoning out while driving. Actually, driving itself is a great example of a complex activity that requires very little conscious oversight. While driving, you can suddenly realize you have no recollection of the last ten minutes. If your brain can drive "unconsciously," surely it can work on a problem unconsciously; after all, you've been thinking longer than you've been driving. Moreover, you can be driving home from work after a hard day, and your brain can switch back and forth between emotional processing of your day and keeping an eye on the road, and you can still have that feeling where you can't remember the last ten minutes.

None of this contradicts the idea that your brain can only work on one problem at a time, but the overall thesis of the essay only works by blurring different concepts together under the terms "thought" and "consciousness."

Let's distinguish between these different brain/mind functions:

1) Parallel, perceptual work (like recognizing an image)

2) Serial, conceptual work (problem-solving, "thought")

3) Verbal, narrative mental occurrences ("thoughts")

4) Conscious awareness

Cognitive behavioral therapy demonstrates that (3) doesn't imply (4) as much as you'd think; you can have a verbal thought very rapidly that you are at most dimly aware of and immediately forget. Rather than implicating consciousness awareness in a wide range of mental activities extending all the way to problem-solving (2), I would say that most things the brain can do with awareness it can also do without awareness.

Those of us familiar with non-verbal "thinking" as we solve a problem know that (2) doesn't imply (3), either. Meanwhile, the thesis of the essay seems to require that (2) implies (4), which is quite a stretch.

dgreensp··on Not all bugs are worth fixing and that's okay
This is my experience as well. Product progress is prioritized over code quality, and the ultimate cost to velocity is real but often unacknowledged. Bugs go unfixed because they are very hard to fix, and this high cost is taken for granted.

It’s definitely on the technical leadership to stand up for code cleanliness and push back against product, and on the higher-ups to recognize the importance of this dynamic.

dgreensp··on The Wrong Abstraction (2016)
Conceptual or semantic compression, yes, as the rest of that section makes clear. The very problem with deduplication without abstraction is not thinking at the conceptual level, only at the literal code level. There are lots of ways to compress code, e.g. minifying it :)

Quoting the start of the article: Abstraction in its main sense is a conceptual process where general rules and concepts are derived from the usage and classification of specific examples, literal ("real" or "concrete") signifiers, first principles, or other methods.

For the Button case, you'd have to come up with some concept of what a Button is and does, beyond what code lives in its file (e.g. an onClick handler that calls handleClick, etc.) in order to have an abstraction.

There are "wrong" abstractions (in the sense of abstractions that turn out to need to be changed later, like any code), but if you lump all deduplication into abstraction then you will have a skewed sense of the cost of changing an abstraction.

The cost of changing an abstraction also depends on your programming language; if you spend a lot of time in a dynamically-typed language, you may internalize that refactoring is tedious and error-prone and often intractable.

dgreensp··on The Wrong Abstraction (2016)
This comment is more insightful than the original post.

The real problem is when engineers abhor duplication, and in order to reuse existing code, they simply call the same code from multiple places without thinking through the basis for this reuse.

Mindless deduplication is not an act of abstraction at all! This is a very important point, because a "wrong" abstraction that is conceptually sound is not that hard to evolve, and if the code is called from N places then you get to look at those places to understand how to evolve the abstraction. Improvements to one part of the code benefit N parts, and you save work.

The only other factor to keep in mind is the dependency graph and coupling, as my parent mentions.

Mindless deduplication is more common than you'd think, especially with bits of code like utility functions and React components. For example, you end up with a component called Button that has no defined scope of responsibility; it's just used in one way or another in 17 different places that render something that looks or acts sort of like a button. This is not the "wrong abstraction," it is code reuse without abstraction.

dgreensp··on The open-plan office is a terrible, horrible, no good, very bad idea
> People whose jobs were mundane/mindless/entry level, people whose jobs involved multitasking across a lot of things, and people whose jobs involved constant interruptions

This is a great description of being a software engineer at certain companies. The pay is good, though.

dgreensp··on The Bulk of Software Engineering in 2018 Is Just Plumbing
The complexity, reliability, and user-friendliness (or technician-friendliness) of the kinds of software components you need to plug together to make a software solution are more like that of a space shuttle or fighter jet than, say, a car, let alone a plumbing fixture.

The glamour (and risk to life and limb) of doing so is that of plumbing.

dgreensp··on Why I Don't Love Gödel, Escher, Bach
A metaphorical fugue on minds and machines in the spirit of Lewis Carroll

The dialogues are supposed to be whimsical and bizarre dream-like riffs on the topic at hand, a la Alice in Wonderland, not sharp teaching instruments.

I think Hofstadter did get the supposed point of Cage’s piece, or why would he have joked about whether people want to hear ambient noise or not?

The review gets good in the middle when it starts talking about Zen, and I agree with some of the conclusions towards the end. As another commenter pointed out, Hofstadter was young. In a way, the whole book is like an amateur piece of music or film or poetry, at times clumsy or campy but generally endearing. I understood this even as a kid.

dgreensp··on The Surprising Power of Virtue Labeling
If you don’t prejudge everyone as lacking virtue, you have no reason to insincerely tell them they are virtuous to try to make them more virtuous.

If you want to do some good in the world, sincerely appreciate the good in people and help them feel seen in it.

dgreensp··on The SEC Will Leave Good ICOs Alone
Anything can be an investment. There are laws about gift cards and equity. Cryptocurrency systems are so technically complex and overloaded with ideals, uses, and philosophies that they can be simultaneously nothing like and everything like these things, IMO. It’s not about what’s right and wrong, it’s just amusing to me that if you want to exploit this particular opinion, as a loophole, the way you’d do it is to make your cryptocurrency sufficiently abstruse.

Edit: To be really clear, I’m talking about the opinion that basically says, if your coin functions as equity then it’s equity; if it functions as a gift card, it’s a gift card; but if it functions as a protocol, it’s a protocol, even if it has speculators bidding it up and benefits going to coin-holders — basically a lot of the properties of equities and gift cards that cause them to be regulated.

dgreensp··on Thousands of Mobile Apps Leak Data from Firebase Databases
It’s not a vulnerability in Firebase, setting aside the question of whether it’s a Firebase “problem” (ie how the blame is divided).

How is it true that apps using Firebase “rarely” secure it properly, if only 10% of apps using Firebase are vulnerable?

A lot of mobile apps are very poorly written.

dgreensp··on The SEC Will Leave Good ICOs Alone
So basically, if you want to raise money by selling gift cards for a product that doesn’t exist to speculators who will trade them, make sure you describe it in terms of some inscrutable crypto protocol network thing that doesn’t map neatly to stock or gift cards.
dgreensp··on Why Threads Are a Bad Idea (1995) [pdf]
Threads were overprescribed in the 90s. I’m pretty sure the original example code for drawing an image in Java involved typing “new Thread” so that the image could be loaded over the network in the background. Truly the way to write apps in the Internet age!

At the same time, Java’s threads are so easy to use — without of the portability or debuggability issues of native threads — that threads don’t seem that bad to Java programmers. Yeah, shared state can be a foot gun, but so can global variables. You just keep things as pure and easy to reason about as possible. And Java has had concurrency primitives that keep you from having to deal directly with threads and locks for over a decade.

I don’t think “events” and threads solve the same problem. If your program would work just as well doing all its work in a single thread then yeah, you don’t really need threads. If we’re comparing “events and callbacks” async style to async/await style where you write your code as if it were running in a thread (even if it isn’t), I think the latter wins.

dgreensp··on How Children in a Maya Village Do Chores
I think the article is helpful for a family in such a situation who might not otherwise think of, say, folding the laundry while hanging out with the kids and being receptive to offers of help, with the idea that down the line the kids could have the job of folding the laundry.
dgreensp··on How Children in a Maya Village Do Chores
I don’t think the article is saying there is anything magic about culture, just about doing chores around and with your toddlers (I have toddlers). It doesn’t take much money to park your kid in front of a TV or a cheap tablet. If anything, parents with more resources have more options. I can see why children in wealthy families or just “wealthy cultures” would not be encouraged to help with chores, but there’s no reason they couldn’t be.
dgreensp··on Haxe: Cross-Platform Development's Best-Kept Secret
The biggest thing that interests me about Haxe is it is rare to find a high-level language with a sophisticated static type system and familiar syntax. This is why TypeScript is so much beloved, but Haxe has some awesome features TypeScript lacks, like a pattern-matching switch statement (with guards), and array comprehensions.
dgreensp··on Things I Regret About Node.js [video]
Haha! Ryan may not have been the best person to design a novel package manager, and while he has some insight into his mistakes the first time around, he still may not be. Neither am I; call me if you need a compiler or a GUI. Everybody has a different set of areas where they have gone deep and developed good instincts.
dgreensp··on Leveraging Introversion as a Career Strength
I’ve come across a couple true extraverts recently, and it has reinforced the idea that there are introverted and extraverted personality types. Previously, I don’t think I fully believed that anyone felt recharged rather than drained being around people. Note that social, outgoing, highly-connected people can be introverts.

Because extraverts are more at home in a social setting than alone — again, hard to even imagine for an introvert — they will tend to choose being around people over being alone. Meetings at work. Drinks after work, followed by meeting friends. An awesome day involves being around other people from morning to night, and the next day they are right back at it.

Extraverts also do their processing by talking to other people, whereas introverts talk to themselves a lot more, hence the part of the article about problem-solving alone vs in meetings. Through this lens, the whole concept of a meeting ought to strike introverts and extraverts very differently. This also leads me to believe that introverts and extraverts each have unique strengths.

dgreensp··on Scrum disempowers developers
Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;

Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis

Maybe T-shaped people are required to make Scrum work, or vice versa? Like if you are running a restaurant and your company process says “there is no distinction between waiters and chefs,” then your waiters need to be decent cooks, and your chefs need to be personable and presentable. “Passion” can be a liability in this environment, for example being passionate about great food or great service. The lack of specialization doesn’t seem directly related to how to do great work, or be really happy at work.

dgreensp··on Scrum disempowers developers
Does Scrum itself empower individual members of the development team? Saying it’s on the developers not to be “mindless drones” and the managers to not be “bad managers” may be true but doesn’t really refute the article’s point. Maybe you have Scrum disempowering developers and (at the best companies) other forces, including other practices and processes, empowering them.

For example, Scrum says responsibility for operations and testing are to be shared responsibilities; you don’t have an ops team or a testing team, or titles, or recognized responsibility. You might have a de facto ops team, but those are just some individuals who have chosen to carry pagers right now. I’ve seen things like this play out and been puzzled by it. I didn’t actually realize until reading this article that people have been giving talks and writing books saying that “subteams” are bad, but it makes sense now.

The point being, not having officially recognized responsibilities is a form of disempowerment.

dgreensp··on Scrum disempowers developers
Having worked at primarily at “informally agile” software companies in Silicon Valley (and I count Google as one), I see an important bit of truth in the article that Scrum ideas have become the embodiment of agile, and ideas from Scrum that may not make sense in isolation have become standard practice in software development and are somehow seen as the alternative to “waterfall” development, even if they have nothing inherently to do with waterfall vs agile development.

For example, it’s never made sense to me to have a powerful product owner while treating the development team as N interchangeable workers who may have “areas of focus” but have no roles, responsibilities, or organization among themselves, smearing out any sort of power or responsibility for technical quality like butter spread on toast. And yet, the fact that Scrum says to do it makes me wonder if that’s why everyone does it. Reading Scrum’s idea of a development team made me facepalm.

I don’t think the article is attacking a straw man that Scrum can turn a bad team into a good one. It may be pointing out that Scrum is regularly used to turn a good team into a bad one. Because everyone wants to be “agile,” even if they never use the word Scrum, they are implementing bad Scrum or cargo-cult Scrum by default.

dgreensp··on The 9.9 Percent Is the New American Aristocracy
I have young kids. If violin lessons are apparently so expensive as to require you to be a millionaire (not merely, say, a six-figure-earner), what is a class or event I can go to to see all the poor, obese kids that I haven’t come across yet? I don’t live in a frou frou part of my town. It seems more likely to me that cultural forces are at play.
dgreensp··on The 9.9 Percent Is the New American Aristocracy
“As of 2016, it took $1.2 million in net worth to make it into the 9.9 percent; $2.4 million to reach the group’s median; and $10 million to get into the top 0.9 percent.”
dgreensp··on The 9.9 Percent Is the New American Aristocracy
Wait, so 10% of the county is millionaires (more or less, if 9.9% are 1.2-millionaires), and these people have such “good family, good health, and good jobs” that they might as well be a different species? If I tell you how “good” someone’s family or health is, you can tell me if they are a millionaire or not?

I think the author’s intent was to acknowledge privilege, but the article is just making more weird caricatures. I think it’s better to put a spotlight on particular ways people might not be able to advance themselves as much as the usual narrative would suggest.

dgreensp··on Reality Driven Development: Fixing Project Management in Software
I would argue bad management is pretty easy spot if you have any reference point for good management; you don’t even have to be a manager. Sit down with a few employees and ask them a few questions. The effects of bad management are everywhere in an organization. Employees are frustrated, resentful, unheard, and happy to talk.

Programming is hard, too, and good code is a much subtler thing that requires an expert to give you any sense of.

dgreensp··on Ask HN: Why is nearing completion so demotivating?
Your brain may be telling you that you need to shift your point of view and focus your energy on different activities, but you may not be clear on what those activities are, or feel like doing them.

Have you launched a product before? Do you have any pre-launch users/customers? Have you done customer development on this product, or just built a thing?

dgreensp··on Value Type Hygiene
Yes, the point is to not box them.
dgreensp··on Announcing TypeScript 2.9 RC
Personally, I find TypeScript to be a joy. I am a team of one right now, but at the last company I worked for, we migrated the codebase to TypeScript, and it was a fair amount of work to migrate the existing code (especially since we had partially migrated to Flow), but worth it, IMO, to have the additional type information, especially given that it was a large shared codebase.

I've never seen such a powerful type system that's so easy to use. While the advanced stuff can be quite complex (as a consequence of its power), the experience of working with the compiler is made pleasant by good IDE support, fast type-checking, and readable syntax. Also, the level of type safety you want to go for is totally up to you.

The one frustrating thing can be using frameworks and libraries that don't have good type definition files. React and TypeScript are actually a slightly awkward fit, because React's component classes and idiomatic HOCs are quite difficult to type correctly, even though TypeScript has built-in React support. In my own code, I've ditched React's component classes for this reason.

dgreensp··on Announcing TypeScript 2.9 RC
I disagree. TypeScript is JavaScript plus type annotations. A team can move from JavaScript to TypeScript and see easy wins with little friction (barring my personal pet peeve, the difficulty of applying types to idiomatic React). I think you are including more about your specific situation in your analysis than is easy to parse out, like your role within a larger organization and the number of different technologies you are working with.
← PreviousPage 10 of 30Next →