HNHacker News
TopNewBestAskShowJobs

courtf

660 karma · joined July 2, 2012

submissionscomments
courtf··on Expert programmers have fine-tuned cortical representations of source code
Took the words right out of my mouth! I feel a little guilty when I'm reminded that "the language is just a tool," meanwhile I am loathe to switch unless truly necessary. Honestly, I don't think I have the memory space to be deeply fluent in more than a few languages, and so when presented with the option of learning/using a new one, I weigh that against proficiency lost in other areas. I know it's not zero-sum, but context switches have a cost. Especially in industry, languages are often so similar that it's hard to justify. I used to feel differently, and be more enthusiastically polyglot (I've got production code currently running somewhere in the world in about 8 languages). It wasn't until I found a language that clicked with me that I even had the motivation to become really fluent.
courtf··on Next steps toward Go 2
There's a lot of talk in these comments about the new 'try' built-in and error handling in general which gives me the sense that errors are more controversial and in need of criticism than the proposed generics design.

I see it the other way around. I'm in favor of generics for Go, but I can't support this design and I think it will have a negative effect on library stability.

Rather than narrowing the scope of contracts to remain mostly orthogonal to existing features, they have it totally open-ended. They clearly didn't want to put too much restraint on what can be stipulated by a contract, and consequently it just feels like a solution looking for a problem (or like they didn't want to to make any hard decisions for which they might be critcized). With contracts as they are, they are incredibly powerful and stomp all over the type system and interfaces in terms of their practical utility. This is not orthogonal design, or really any sort of design, it's a blank page. They feel like a complete abdication of the designers' responsibility to make Go a simple language that tries to only pull in minimal features while reducing overlap. It's context.Values again but far worse. Please stop trying to make everyone happy, it's impossible (and I realize the irony here).

I liked generics when they were going to be super strict (and consequently super simple from the user's perspective), no upper or lower bounds on the type, just essentially a glorified gogenerate. This feels like you all are trying to answer to the critics rather than to the code.

courtf··on How does it feel to be watched at work all the time?
Just insert this slim, minimally intrusive sensor into your anus until the soft beep it emits can no longer be heard; that's how you know it's in far enough. Our team in Copenhagen came up with the sleek design (you should see the office there!). Our CEO even wears one, and you can watch his colon expand and contract, in real time, up on the big board!

Over time, we've found that a rectum capable of dilating to at least 1.5 inches in diameter is correlated with improved productivity, so try and stay loose throughout the day! There are lube and applicators available in the restrooms, and welcome to Job Corp!

courtf··on Error Handling in Go (2016)
I don't agree with this, and I find the pace of writing in Go to be quite quick. I've recently been working on a server that performs arbitrary work pre-defined in DAGs, with an API, full tests and several fancy features. The initial bulk of the work took me about 3 weeks and the only dependency is a test mocking library.
courtf··on Error Handling in Go (2016)
Luckily you can implement a stack in 10 very simple lines. And if you don't want to do that, there are many existing implementations.
courtf··on Alan Kay on the Meaning of “Object-Oriented Programming” (2003)
don’t find types to be worth the trouble

This is the part I always fail to grok in discussions about type systems. For me it is just the opposite: I typically don't find dynamic typing to be worth the trouble, so I fail to understand this sentiment when going the other direction.

Maybe it's because my degree is in mathematics (lots of proofs written out long-hand), and my first language was Java? I have since all but abandoned many of the ideas that Java so rigidly enforces, OOP among them, but static typing just has so many advantages for me that I have no desire to get rid of it.

One thing I've noticed in some recent work is that the static language I'm using (Go) allows me to both be lazier and get more done than comparable work being done in dynamic languages. I'm not reading or writing tons of documentation (I'm reading other people's code directly, or just looking at the types involved and moving on). I'm not constantly handling byzantine runtime errors or having to memorize the arbitrary intricacies of any over-bearing frameworks in order to be productive. I don't need to be on guard quite so much, I lean on static analysis. In general I just don't need to hold so much extraneous crap in my head, it's all spelled out right there in the code and I'm free to think about larger concerns, like the best way to solve the problem at hand. And when I circle back around to some 10-20k line library I wrote 3-6 months ago, I can read, understand and refactor parts of it quickly.

People often talk about developer comfort and speed being improved by dynamic languages, and maybe that's true if Rails solves all your business needs, but for many of the tasks I've work on, that just hasn't borne out over the past 10 years. I have no doubt that dynamic languages seemed a breath of fresh air after fighting with C/C++/Java, but to my eyes Ruby/Python/Javascript etc were always a bridge too far for a lot of tasks.

courtf··on The New 30-Something
As a millennial born in the early 80s, I know a good number of people from my college years who, I have learned over time, live a similarly charmed life.

Looking back, there was always something a bit odd about these folks: namely, that they seemed to be far more concerned than I was about what to do with their time. They seemed to really be concerned about having the "right" kind of job, or the "right" kind of life. When I was working customer service or slinging cocktails at the gay bars to pay my rent and food costs, they were researching grad schools (only the best), or traveling to the third world on short-term humanitarian missions. One took several years off from work without much apparent anxiety. Another jumped from city to city, making large numbers of fair-weather friends and throwing himself into startup after startup, never settling down or really committing to anything or anyone. Another married a successful artist, and raises the kids in Santa Monica. I know a few living very bohemian lives, in high-minded intentional communities, writing books to teach their peers about some obscure facet of culture. Some went into the corporate world, where they adequately fill a suit and sometimes write about M&A on a blog.

I've worked with lots of these types as well of course, in the tech industry. They have no concern about being their own angel, and care a lot about diversity, but have no qualms about asking you to work late, or over the weekend to help "the business" meet its latest pivot. Needless to say, all of these people are white.

My husband's family is white too, although quite poor. His father used to break and shoe horses, and can track an animal through a desert. The sort of man who relies on Medicare to pay for his liver removal surgery, his lymph-node removal, his spinal growths removals, and any other places where the cancer metastasized, but is out fixing a truck engine soon after, with his oxygen tank dangerously close to the welding torch. This happens in the sort of countryside where your trailer gets broken into, and the thieves drag your refrigerator over to their trailer not far away up the dirt road, leaving a trail you can see from space, but the police can't do anything. In an earlier time, he would have solved that problem himself, but he doesn't hear so good, or see so good thanks to a couple of strokes and type-I diabetes. The wife has MS, so he spends most of his time taking care of her.

When the grandfather shot himself, the gun was one of the most valuable things he left behind. Despite losing her retirement to shady financial management, after 30 years as a charge nurse in the ED, the wife couldn't wait to blow what little they got in the will on a new hot tub. Better enjoy it now.

Of course they'll have to sell their sandy little plot in the next year or so anyway, before it becomes worthless due to the water table drying up. My husband does what he can to bail them out when unexpected bills arrive, and maybe he ought to spend more on their comfort. God knows his sister can't help from behind bars.

My family is different, my parents paid for my bachelor's, just not my master's, but we can tell some similar stories from a couple generations back. My grandfather had to cut off his own father during the depression, essentially dooming him, because the old man stupidly lost everything he owned, and his only hope was the wage my grandfather earned, after a career as a ship's engineer, shoveling coal into the furnaces of buildings in NYC. This is the ugly side of progress no one wants to talk about: how people get left behind. How the parents fight a losing battle, and the kid grows up knowing their only hope is to get the hell away from it all. These callous things long to be forgotten.

courtf··on A listing of companies that don't do whiteboard job interviews
I was responding to these lines:

I'm not hiring artists I'm hiring engineer's. I'm not hiring your for your gorgeous code in x language, I'm hiring for problem solving skills and communication.

I agree with the second half (problem solving and communication) but take some issue with the the way you dismissed the art of it all. Maybe we have different ideas of what an artist is?

I tend to think of software in more blue-collar terms myself, perhaps more like a carpenter (who has to consider more than just aesthetics, but certainly can't ignore them) than a violinist, but my earlier comment was just continuing the established metaphor. Either way, I get the sense we agree more than we disagree here.

courtf··on A listing of companies that don't do whiteboard job interviews
Software is far more art than you think, and rigid, formulaic thinking can be a detriment to good problem solving skills. Especially when solving something you can't just look up on the internet.

If your engineers aren't writing clean, readable, maintainable code that solves problems as simply as possible (ie, gorgeous), I'm not sure your hiring practices are doing you any good.

courtf··on A listing of companies that don't do whiteboard job interviews
Would you ask a violinist to draw the chords they would play on a whiteboard, or would you hand them a violin?
courtf··on A listing of companies that don't do whiteboard job interviews
Completely agree. My best decisions are not made on my feet, and I have often been responsible for difficult technical tasks. I also prefer to "communicate my thinking" in the form of readable, well-tested code that can be verified by a machine.

If that code is unsatisfactory for some reason, I'd rather figure that out after writing it, based on concrete evidence, than during an upfront design meeting with folks who likely won't be doing the actual work, but often feel the need to impose themselves in arbitrary ways. When a team focuses on excellent communication through writing, I find less planning and verbalizing is necessary, and a lot more gets done.

As a partial aside, one of my greatest annoyances when starting a new job is when after being grilled for technical skills during the interview, they walk you in to a messy, amateur codebase, where many of the ideals discussed during the interview clearly haven't been applied, but no one seems to acknowledge it. This has happened to me repeatedly, enough so that when these sorts of questions come up during the interview, I mentally start preparing for the disappointment. People sometimes seem to take more pride in trying to rattle candidates than they do in building anything admirable. Luckily, there are many fine places to work where the team can be honest with itself and with candidates. I don't really care about the current state of projects when I'm starting; I don't mind being a janitor (except in extreme cases). Just don't start our relationship off with a load of BS. I feel like this is such an elephant in the industry. A lot of our code is bad, real bad, but we can't admit it.

courtf··on Sheryl Sandberg: The teens consented
Yep, once you start leanin' in you just can't stop.

In all seriousness, I do wonder how these billionaires can resist just riding off into the sunset. Have some damn dignity.

courtf··on Proposal: Go 2 transition
In addition, it's pretty easy to avoid heap allocations in Go, so you can do some basic (but effective) management without breaking a sweat.
courtf··on On the Road to Pure Go X11 GUIs
Yeah definitely a bug.

I've worked on systems that allocated and freed hundreds of GB every 10 minutes, written in Go with no such issues.

courtf··on Things I Learned in the Gulag
That's not Shalamov's point though, which is what I'm trying to steer us back towards. I think it's fair to take from Shalamov's words that religion is getting short shrift from secular society in the west today. But beyond that, I'm afraid our conversation is mostly descending into the typical culture war topics.
courtf··on Things I Learned in the Gulag
The way it's worded it mostly just sounds like men were generally more cowardly. Of course there could be a variety of pressures that might account for the anecdote, such as women not being given the opportunity to refuse.
courtf··on Things I Learned in the Gulag
Eh, kind of a stretch. Religion is not a purely Western invention, and you're reading what you want to in #29.
courtf··on Dead People Are Posting Anti-Net Neutrality Comments to FCC Website
I'm imagining that the dead are just a small fraction of the fake comments: just those who had died since whatever dataset being used was last regenerated/cleaned.
courtf··on Program your next server in Go
I don't have great measurements for this, but we have done optimizations to reduce the data flowing over the Go<->C interface. One of our key measurements that does make a big impact on performance is how often we need to upload data (that's not already over there) to the GPUs. So that's something we have worked on reducing (buffer reuse, compression). We also have a series of caches on the other side, so we aren't drawing more than we need to. It's hard for me to tease apart how much of these optimizations (and others) are ultimately aimed at addressing the cgo overhead, and how many are just typical stuff. The data we work with is cumbersome and my intuition is that there's probably a lot of room for optimization in our drawing even still, regardless of cgo. I wouldn't be surprised if a direct port C/C++ implementation of the rendering pipeline was significantly faster than ours in getting data into and out of the GPUs, but a big part of the project is data storage/networking/serving/caching as well and Go has bridged the gap for us (a small team that needs to build reasonably fast things reasonably quickly :)).
courtf··on Program your next server in Go
We run a cluster of P2P, GPU heavy machines that use Go to ingest byte streams of raw radar data, store that info in btrees, and render, cache & serve map tiles that are drawn on the fly in response to http requests. We are not using much outside the stdlib (opengl and gdal bindings).

Garbage collection has become very fast in recent versions of the language. It's quite painless now, and we did struggle with it in the past. I'd take the current GC over dealing with other strategies unless you are a very specific, >60fps kind of situation. We literally don't think about the GC anymore.

Random stats from one of our busier nodes, over the past 20 min: 40GB currently in use, 391GB allocated (and freed) in the last 20min average of 2.6ms GC pauses every 70.6s 95th percentile on GC time is 7.26ms

For dependency management, there's a lot of tools that make things more automated and I think probably offer people what they are expecting/used to from other environments. This has been a sticky point for sure. I've settled on a bare bones solution that seems to work well: just using git submodules in the vendor directory within the project repo. Does everything I need (pin to version of a fork, build immediately after a clone and a submodule update --init). As of Go1.5, the vendor directory is supported by the compiler, and it will look there first to resolve dependencies. While this does work with recursive dependencies, you will want to flatten the dependency graph as much as possible if types are being used across multiple deps because types are distinguished by their full import paths. This encourages breaking things into modules so I'm ok with it.

First-tier support is a problem I have no doubt, but not one we've suffered from personally.

I'd say that debugging comes up a lot too, and Go doesn't have an official, reliable option for debugging. The Delve project is getting close to that though it looks like. I personally debug with the stdlib pprof package (provides an http server that prints stack traces for all goroutines currently active, allows cpu/memory/blocking profiles to be requested), print statements, general testing/experimentation and newrelic.

courtf··on Deconstructing K&R C Is Dead (2015)
We have a few Go processes with high memory usage. For one in particular, while it's been higher in the past (~150GB), we're sitting at 40-80GB per node right now.

The busiest node traffic-wise had average GC time over the past 20min of 3.4ms every 54.5s. 95th percentile on GC time is 6.82ms.

That node is sitting at 36GB in-use right now, and has allocated (and freed) an additional 661GB over the past 20min.

Can't really speak to how fast this is vs other environments, but it's smooth sailing overall. /shrug

courtf··on Go channels are bad
Synchronizing access to a memory address isn't really the use-case for channels. I think that's fairly well understood by the Go programmers I work with. This example demonstrates why, but it prefaces the discussion by implying this is the standard practice, which I think is misleading.
courtf··on SurveyMonkey to Lay Off 100 and Retool Business Product
Worked there from 2007-2010, through the sale etc. I had no idea they were up to 750 employees, and can't guess why they've gotten so big. There were 10-15 employees, 2 engineers in 2008 and that company was printing its own money, lots of it. I'm sure revenue is much higher today, but that profit amount isn't a big jump from where the company was headed pre-buyout, on momentum alone. Really have to wonder what they are spending it all on (besides payroll tax).
courtf··on Things I've learned about writing software after 12 years
Your comment isn't really addressing mine from the context in which it was given. My comment was in reply to someone implying criticism of the piece stems from its reading level being above that of a 12 or 13 year old, which isn't the case.

I'm simply proposing that the criticism is founded on actual flaws with the piece, rather than it being too complex to be understood by its detractors.

courtf··on Things I've learned about writing software after 12 years
Beyond the grammatical errors, misplaced punctuation and misspellings, and despite the relative novelty of the anecdotes, I thought the writing itself was dull and simplistic. Many paragraphs were just a string of blunt statements without any independent clauses.

According to a copy+paste of the text into http://sarahktyler.com/code/sample.php, the article as a whole reaches Flesch-Kindaid grade level 7.

courtf··on Welcome Peter
"the founders of those companies will generally tell you he has been their best source"

Honest question: if a company receives investment from Peter Thiel, do the founders have any choice but to express the opinion above?

courtf··on Michael Jordan Has Not Left the Building (2013)
There's no doubt that Federer and other great sports figures are well mannered and handle their success with extraordinary grace. However, if your definition of a-hole includes 1) being ruthlessly competitive and/or 2) believing you are better than your competition (even if that hasn't been convincingly demonstrated), I'd wager many of these figures would fit the bill, Federer included.

Personally, I find 2) unbearably obnoxious, but it's something I'm willing to forgive if they provide evidence in the affirmative, as Federer certainly has. I think we have to permit a certain amount of elitism, because it would be dishonest to expect that these players refrain from acknowledging their positions within the respective pantheons of their sports.

courtf··on Michael Jordan Has Not Left the Building (2013)
It's a common trope, particularly among the more intellectually focused, to reduce sports to mindless drudgery.
courtf··on Michael Jordan Has Not Left the Building (2013)
Fair point, although I wonder if we'd have these elite players if they were more willing to tolerate failure in themselves.

The man is obviously flawed, but a lot of the criticism is petty and no better than Jordan's own kvetching. I'm sure we all know plenty of other ego-maniacs who don't even have something real to brag about.

courtf··on How my life was changed when I began caring about the people I did not hire
Good points here. Some of those who left the process in the beginning may have simply had better things to spend the next month on, not because they were inferior candidates. I like the tone of the article in general, but it does smack of a certain entitlement on the employer's part whereby they feel justified in extracting many thousands of dollars of free work from unemployed job seekers. Despite the admirable intentions, the caveat that some of those who didn't receive a job immediately were later hired elsewhere is only meager consolation, as I'm sure there were significant contributors who were not proportionally compensated.
← PreviousPage 7 of 9Next →