jfe

ditto.

there are two issues: one cofounder was being "man-handled" by an investor, and their product received little support, allegedly because the author and cofounder was not attractive, white, male, etc.

i think everyone here agrees being "handsy" with anyone in a professional setting is not the right thing to do. it's certainly not punishable by death, but it's socially uncouth. that being said, the author acknowledged that it's common for sales pitches to be misinterpreted as sexual interest, and seeing how women generally like aggressive men, it's not hard to see how an investor would interpret such a situation as a cue to get "handsy" with the cofounder. again, not excusable in a professional setting, but you can't lambaste a man for his own biology.

which brings me to the second issue. if men are biologically predisposed to choose male leaders over female leaders and we want women to have an equal opportunity to be funded -- provided their product is actually as good as a man's -- then women will gain better traction by offering incentives for men to prefer the female leaders over the male leaders, rather than trying to change biology so men "work correctly".

not always. i'm all for the "theme and variations" style of software development, provided the variations offer something distinctly novel. that doesn't seem to be the case here.

nice try, but adobe got in the game long ago :)

https://color.adobe.com/explore/newest/?time=all

I don't read whatever people recommend to me; I prioritize what's available based on what I think will have the greatest impact on me. But whatever I do read, I try to read it all the way through. Books have layers, like an onion. Each time you read a book, you peel back another layer of meaning. The first time I read a book, I don't let myself get hung up on what I don't understand; I just keep reading until I've reached the end. Then, if the book is really worth re-reading, I'll do it, and pay more attention to the details. You can get through a lot of tough material that way, and get 85-90% of the benefits as you would just sitting there, trying to grok every. Single. Word.

the primary function of unions is to improve working conditions and increase wages for its members. the improved working conditions are welcome in developing nations, but the increased wages come at a cost, for unions can only ensure higher wages by limiting the number of jobs available. furthermore, unions must define a set of criteria for the acceptance of new union members that discriminates for reasons wholly irrelevant to employers.

i'll defer to alan perlis on this: "a language that doesn't affect the way you think about programming, is not worth knowing."

does perl offer something distinctly different from other, younger languages? IMHO, not really.

there is a bunch of perl code out there that needs maintenance, which is why i learned just enough perl to read it. but who truly gets into programming to maintain something that's already built? might as well learn COBOL if that's how you think.

yep, at the expense of all your RAM.

that may be true, but is it worth the time of the community to critique code that offers them nothing in return?

one might argue that the decision as to whether code is worth reviewing is up to the individual, and i would agree. but i would also argue that it's the responsibility of the author to decide whether or not the submission of that code in a public forum will generate more light or more heat, and filter such submissions accordingly.

I may be a bit biased -- the Bell Labs guys are major influences of mine -- but I think the criticism of Pike, et. al is unfair. I understood Pike's "systems research is irrelevant" presentation to be a tongue-in-cheek observation about the decline of systems research, not a statement that "OS research is dead" and we shouldn't work on it, but maybe I'm mistaken.

I don't consider Plan9 to be a failure, at least in the engineering sense. Many ideas pioneered in Plan9 influenced developments in the Linux kernel. It actually seems contradictory to me that Keith spends so much time flaming the community for not trying something new, then berates researchers like Pike for doing exactly that.

i still have much to learn about language design, but i believe julia has gradual typing. it uses type annotations for the purposes of multiple dispatch (which is awesome, btw) and optimization.

...or you can just use Julia :)

Management is fixated on On-Time Delivery. We do have metrics showing that QA spends a lot of time re-running automated tests, but there's no direct proof that shows that the crappy framework is the cause.

ditto. HTTPy would have been better, methinks.

neat, but i'll stick to nasm, thanks.

me rikey

yes, perhaps i should have titled this rant "we need fewer programmers and more engineers" :)

not so much interacting, as harnessing computing resources. plan9, though not terribly popular in the mainstream sense, introduced very simple and effective methods of distributed computing. the engineers broke away from the TCP model and developed their own transport protocol for super-fast data transfer. i personally want to see more of this.

i know, and i don't care.

this article is ridden with economic fallacies.

i wouldn't say that HN or the open source community in general has shut the doors on microsoft as much as microsoft has shut the doors on the open source community. developers who get into the microsoft bubble never seem to make their way out, and the number of open-source c# projects is limited in comparison to those written in other languages, simply due to their system dependence.

become as good a programmer as you possibly can, and learn to write extremely thorough test plans.

put another way, build quality in from the start. ensure that you don't need to fix/update your code or test plan later. if that's unavoidable, at least make doing so as quick and painless as possible.

How is a 9-week course in Ruby On Rails considered a "programming foundation"? It's sad to me how many people think software development is all about web frameworks.

why, God, why?

Time to get out of your two-editor bubble, folks; there are other options. In my opinion, Acme puts both Emacs and Vim to shame.

worst writing ever.

if you have other apple devices, i'd suggest sticking with macs to take advantage of icloud et. al. otherwise it doesn't really matter which one you choose.

agreed. these metrics mean absolutely nothing. the founding fathers preferred congressional stalemates to passing laws in excess.

there's a program called 'grep' that does this, too... >_>