pifflesnort

13 ms·

61.
by pifflesnort 14y ago
I admit that I don't understand your analogy. There isn't a bug in the call for papers -- it's fair. There isn't a bug in the review of papers -- the selections model the actual distribution of the larger population. So where is the problem
62.
by pifflesnort 14y ago
> Well spotted. The point is that the status quo is a choice, just as being more inclusive is a choice. Which is the better choice? Better technical content is the better choice for a technical conference. > 1. That including peo
63.
by pifflesnort 14y ago
> That's not the case for open-source tech conferences. Open source has a preference for social change at its fundamental level - "anyone can edit". This at least leans towards promoting an egalitarian environment. Open-source is not
64.
by pifflesnort 14y ago
> Well I don't exist to facilitate your preferred status quo. You are not a technical conference . You are a person. At a technical conference , focused on technical content : if you sacrifice the quality of that technical content
65.
by pifflesnort 14y ago
> If there isn't anyone from your particular group at a highly demanding conference panel, or visible in your industry, you're much less likely to become a part of it... even though you're more than capable of performing at that level
66.
by pifflesnort 14y ago
> I used the phrase "only test what needs to be tested" intentionally. How should I know what you need to test? But if you accept that you should only test what needs to be tested, then there is an implication that some (I'd venture to
67.
by pifflesnort 14y ago
> It's not some kind of man-hating reverse discrimination, it's an attempt to correct very real and very pervasive institutional inequalities. Your position also assumes that the parties performing evaluations have existing gender bia
68.
by pifflesnort 14y ago
I can't comprehend why you're arguing that these complex "upstream" cultural issues should force me to evaluate conference papers on any other grounds other than their technical merit -- something that would be the to the detriment of speak
69.
by pifflesnort 14y ago
> When "their qualifications" results in a selection rate of men approaching 100%, I think that's prima facie case that one of the most important qualifications is being a man. Why is this a prima facie case proof of sexist qualific
70.
by pifflesnort 14y ago
> But when you suggest that no work is accomplished in any meeting, you're wrong. This is where we disagree. Talking about work isn't tangible work. Talking unblocks work, to a point. > I'm sorry you've had such a bad experience
71.
by pifflesnort 14y ago
> The function being used to evaluate speakers is broken - that much is clear from the rate of women being selected. What numbers do you have to demonstrate that the function is broken? What percentage of our industry is made up of wo
72.
by pifflesnort 14y ago
> The point that you're missing is that just because some meetings add no value doesn't mean that no meetings add value. The fact that some meetings add value doesn't mean all or even most meetings add value. My analogy holds; p
73.
by pifflesnort 14y ago
> Why is it that the coding part is considered "work" and the meetings is considered "not-work"? In kernel terms, meetings and PMs are the scheduler, and you are the threads/processes being scheduled. Is the scheduler doing work? Yes.
74.
by pifflesnort 14y ago
> When I was working for a large internet company, we got a lot of work done in meetings and lots of PM's were respected. How did you get work done in meetings? By definition, meetings are stopping work to communicate; the most work
75.
by pifflesnort 14y ago
> Response latency makes scripting language unacceptable for some types of problems. But in my experience very few latency problems I've come across are down to language choice vs. badly written database queries, lack of caching etc.
76.
by pifflesnort 14y ago
These are all aesthetic complaints, not UX complaints. The UX is standard. Now, I actually happen to agree that it's not the prettiest app. But it is a very usable app, in ways that a web browser music player is not. I also get the impressi
77.
by pifflesnort 14y ago
> It's ugly. It doesn't look nice in the slightest. It doesn't scream to me "Boy, this looks like an awesome user experience. I better try it out!" Why is it ugly? What, specifically is wrong with the UX?
78.
by pifflesnort 14y ago
You seem to be saying that the AOT path requires constrained typing and a strict subset of the language semantics, which agrees with the parent's point that static type semantics matter in terms of performance.
79.
by pifflesnort 14y ago
> But it didn't touch the important question -- is the development time for Go faster than for scripting languages with critical sections in C? "Writing critical sections in C" is a terrible cop-out of the Python community, by which t
80.
by pifflesnort 14y ago
> You totally miss the point. There are large classes of systems where CPU time in your app is not a significant factor. E.g. my go-to example of this is the first Ruby project I deployed in a production environment: This is only true
81.
by pifflesnort 14y ago
> Time of "Getting that shit done" and cost of long-term maintenance are two of the main reasons why people use Ruby/Python, not for the raw performance. Plenty of other languages "get shit done". > And anyway, from my experience
82.
by pifflesnort 14y ago
> I like how you're talking about good user experiences and then use that as an example. What's your point? > Furthermore, that wouldn't as easily transfer to Windows since taskbar notification icons are routinely hidden. Mac OS
83.
by pifflesnort 14y ago
> Perhaps a better way to look at it is this- when I have a great job doing web development and see job listings all over the place for other rewarding web roles, where is my incentive to do desktop development- even if it's close to t
84.
by pifflesnort 14y ago
> Speaking as a web developer, I can tell you that I am perfectly able to transition to making desktop apps, I just have no incentive to. There are fewer and fewer desktop apps out there, so it's not a great use of my time to learn tho
85.
by pifflesnort 14y ago
> They were getting rid of native rendering and replacing it with rendering a webpage. No wonder people were so pissed and no wonder so much functionality was dropped. I can confirm this, and have heard that this was politically drive
86.
by pifflesnort 14y ago
> ... but when compared to the big disadvantage of having to maintain two codebases ... It's about your users, not your developers. Of course it costs more to provide a better product, which was the original reasoning behind providing
87.
by pifflesnort 14y ago
This is a silly false dichotomy. We've built our own business, profitably, from the start, by paying prevailing wages to top-tier talent who are located where we are. It benefits our community and our country, but it also means that we're g
88.
by pifflesnort 14y ago
It only looks like a lot when you're not zoomed in. The density here is very, very, very high. The vast majority of buildings aren't covered.
89.
by pifflesnort 14y ago
We started using Paychex when we had a total of two founders, making almost nothing, five years ago. It was painless -- and cheap. On top of that, Paychex has had our back with hands-on personal customer service when things went wrong due t
90.
by pifflesnort 14y ago
> Heck Verizon FiOS offers fiber to the home in NYC and has speeds of 300Mbit/s Where? The entire time I've lived in NYC, in neighborhoods with population density between 30k to 70k people per square mile , I've never, ever, ever had

More ›