Recent submissions

Comment · 4 months ago
Comment · 4 months ago
We do but I don't want to over promise here since that's not my area. My best recommendation is to apply if it looks like a fit.
Comment · 5 months ago
Comment · 3 years ago
Comment · 8 years ago
From the Article

>>> A top U.S. Justice Department official, Makan Delrahim, praised the deal as being carefully sculpted to avoid antitrust concerns, signaling federal regulators were unlikely to block it. That stance is all the more notable given his continued efforts to kill on antitrust grounds the AT&T acquisition of Time Warner, a combination of a telecoms giant and an entertainment powerhouse that have little overlapping commerce. The Justice Department is appealing a judge's ruling that swept aside all objections to the AT&T/Time Warner merger.

Comment · 9 years ago
Im curious as to how he's using vim + ensime. I've been trying off and on for the last 2 years to figure out a good workflow using ensime but i typically end up just turning it off after a few days. EnType only works for me when its completely obvious. EnImport seems kind of useless. After these 2, i just give up, tbh.

Still, I wont give up my text editor :) Any emacs folk like to comment on its usefulness? Its seems more fully implemented there.

Comment · 9 years ago
would that happen to include scala?
Comment · 10 years ago
Space Data Centers -- we got tons of power, just need to figure out how to vent all that heat.
Comment · 10 years ago
this reminds me of the post about the jvm code cache a few days ago where if they had left the jvm to optimize the code cache by itself, the would not have ended up with the problem situation where the had to spend time to figure it out their optimization was the cause of the problem.

-- sorry for the run on sentence.

Comment · 10 years ago
My posit was that 80% of the software an engineer will write will not require optimization and based on the responses i've been getting I should have used "rule of thumb" vs mantra. My intention was to warn the ones that read this and say, oh i gotta do all of this for every piece of software that I write, which will undoubtedly lead to overly complex code when a simple solution would have worked just as well.

  "Know your performance goals going in and code accordingly."
I this is key sentence here and its worth repeating. Know your performance goals before your fingers touch the keyboard.
Comment · 10 years ago
absolutely agree with your last sentence. But thats not a majority of software written in my experience.

  "If you really need *high performance*, you need to design for high performance, not just leave it as an afterthought." 
Emphasis, mine.
Comment · 10 years ago
While this article is itself worth a read, remember the programming mantra:

  * Make it Work
  * Make it Right
  * Make it Fast
And this is the last step. While this does not apply to all projects but it does apply to the majority.
Comment · 10 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton