[1] http://www.spacenews.com/article/financial-report/42180aeroj...
1,169 karma · joined January 31, 2011
[1] http://www.spacenews.com/article/financial-report/42180aeroj...
I wish Java had a one-true-way for one-time static initialization like dispatch_once() in Objective-C.
S4LRU: Quadruply-segmented LRU. Four queues are maintained at levels 0 to 3. On a cache miss, the item is inserted at the head of queue 0. On a cache hit, the item is moved to the head of the next higher queue (items in queue 3 move to the head of queue 3). Each queue is allocated 1/4 of the total cache size and items are evicted from the tail of a queue to the head of the next lower queue to maintain the size invariants. Items evicted from queue 0 are evicted from the cache.
Paper: http://www.cs.cornell.edu/~qhuang/papers/sosp_fbanalysis.pdf
Stack: Java (10 yrs), iOS (4 yrs), Android (2 yrs), Redis
Resume: https://www.linkedin.com/in/greghaines | https://github.com/gresrun
Contact: greg AT greghaines DOT net
Experienced developer that prefers small, focused teams is looking to overcome interesting technical challenges to bring great products to fruition.
brew install html-xml-utilsAccepting a counter-offer is almost always a bad idea; no matter how much money is on the table. After accepting a counter-offer you are bought and paid-for, you decided to stay for the cash and, unfortunately, your loyalty to the company will be questioned forever after.
It is possible to roll a 'fat' JAR with all your dependencies baked-in, which is as close to static linking as it gets in Java-land. I prefer this for stand-alone applications as it makes deployment a cinch at the expense of the size of the build artifact.
Fair.
> In many ways community submitted pull requests are a "million monkeys at a million typewriters."
I strongly disagree with this assertion. To argue that community cannot be lead or directed toward a common goal is very pessimistic. Sure, Joe in Idaho has a specific itch, but there's a good chance there is an opportunity to capture Joe's enthusiasm and willingness to do work on the project by working with him instead of treating him like a code-monkey at a keyboard. Community relations is hard because dealing with people is hard.
> 1. Tools that help maintainers cultivate the submitters talent pool on their project.
Yes, I agree that this is someplace where some tools would help tremendously.
> Github can help me discover what is happening to that function elsewhere.
Great idea. I'd love to see a "related diffs" tool for a given piece of code.
> So many of us are code-first, conversation-later types and that constantly conflicts with the social nature of our job.
I totally agree. Ultimately, tools will only get us so far; people skills must fill in the rest. Making "Joe" feel welcome and a part of the creative process requires measures of patience, kindness, gentleness and mentorship.
Is it that project leadership has a clear vision for a product and feel pull requests are a distraction? If so, share the vision and enlist willing developers to help achieve that vision.
Is it that project leadership has a high-standard for the codebase? If so, explicitly state the standard and provide constructive feedback to pulls that don't quite measure up.
I guess my point is: project leadership has the ability to leverage a tremendous pool of talent that is interested in their project using the pull request mechanism. It does take effort and planning but the net result is so worth it to all parties involved.
https://github.com/netty/netty/tree/bufferpooling https://github.com/netty/netty/issues/62 https://github.com/netty/netty/commit/c9968d6cbfa958f73a9868...
It's the Java equivalent of writing your own alloc().
DirectBuffers are also used in I/O libraries like Netty.