arosien's comments

Working with Adam @ Box, Los Altos, CA

I'm going rogue and looking for help out-of-band. I need a senior engineer to help with our "continuous delivery" system, including our fancy-schmancy deployment manager that coordinates all the tricky bits. Scala, Akka, scalaz, Apache ZooKeeper, Jenkins, git, bots, tickets, monitoring, all that stuff.

Email [email protected]!

.. Adam

Content-centric networking aims to solve some of these problems: http://en.wikipedia.org/wiki/Content-centric_networking

"Content-centric networking (also content-based networking, data-oriented networking or named data networking) is an alternative approach to the architecture of computer networks. Its founding principle is that a communication network should allow a user to focus on the data he or she needs, rather than having to reference a specific, physical location where that data is to be retrieved from. This stems from the fact that the vast majority of current Internet usage (a "high 90% level of traffic") consists of data being disseminated from a source to a number of users.

The contemporary Internet architecture revolves around a host-based conversation model, created in the 1970s to allow geographically distributed users to use a few big, immobile computers. The content-centric networking seeks to adapt the network architecture to current network usage patterns."

You're lucky to have QA people who know C++, I've never met one. Maybe I've been in too many web-oriented startups.

I disagree. Developers who don't know how to test are bad developers, they should go. And conversely, if you have QA, they should know how to develop, otherwise you're paying them to hunt, peck, and click. Why not have QA write the code to have computer do that and save like 1000x the time? That's efficiency AND quality.

Having worked in Silicon Valley for 12 years, I have yet to find QA people who could successfully automate testing in a non-fragile way or without using an expensive, proprietary and crappy testing harness. Those who know how to program are invariably better at writing automated tests. One recent CS graduate should be able to put a team of QA out of a job. (Disclosure: I work for Wealthfront)

Sweet. We use Apache ZooKeeper for service discovery and have a #zk channel. We just did a deployment, here's the irc log: (deploying the 'PM' service, updating instance pm12 first)

[1:05pm] dm: PM leader changed from pm12 to (none)

[1:05pm] dm: PM leader changed from (none) to pm11

[1:05pm] dm: UNANNOUNCED: ServiceDescriptor[id=pm12,kind=class com.kaching.platform.guice.KachingServices$PM,uri=http://10.99.110.140:8080,shards=[],status=UP]

[1:05pm] dm: ANNOUNCED: ServiceDescriptor[id=pm12,kind=class com.kaching.platform.guice.KachingServices$PM,uri=http://10.99.110.140:8080,shards=[],status=INIT]

[1:05pm] dm: UPDATED: ServiceDescriptor[id=pm12,kind=class com.kaching.platform.guice.KachingServices$PM,uri=http://10.99.110.140:8080,shards=[],status=UP]

See http://en.wikipedia.org/wiki/End-to-end_principle.

Nice. Last.fm has a nice post at http://www.metabrew.com/article/how-we-use-irc-at-lastfm.

We also have separate channels for each message type. IRC is pub-sub, yay! Plus you can direct-message a bot and it will DM you back, to not pollute the channel you're currently in.

Do you have any bots that take commands? I think that's where it gets really useful.

You are so enterprisey! :)

We'll bridge protocols if we need to cross that, um, bridge.

Hi Noah!

Wealthfront (formerly kaChing), Palo Alto CA (no remotes)

Wealthfront is intent on disrupting the $10-TRILLION mutual fund industry, an industry that's seen little innovation in the past 25 years. To reach this goal, we put our customers and our technology at the heart of everything we do. Java, Scala, JRuby on Rails. We have a 5-minute commit-to-production continuous deployment system. Read our eng blog at http://eng.wealthfront.com.

Lead UI Designer / Frontend Software Engineer / Backend Software Engineer

Email [email protected] / More at: https://www.wealthfront.com/jobs

FYI you can clone this code from the blog post (with lots of other goodness) at http://code.google.com/p/kawala or https://github.com/wealthfront/kawala.

Palo Alto, CA - kaChing is hiring front- and back-end engineers to help us disrupt the $10^12 mutual fund market.

We are looking for self-driven software engineers who are passionate about solving problems related to scalability, algorithms and user experience. Our team comes from top schools and companies including Stanford, Google, Ning, and LinkedIn. We're located in downtown Palo Alto within walking distance of the train and Stanford. We use JVM languages (JRuby, Scala and Java) and a revolutionary service execution environment. We share all of our data via a public API, employ a 5-minute commit-to-production cycle and embrace Agile, test-driven processes.

For some perspective into how we think, check out our engineering blog http://eng.kaching.com.

Got a question? Ready to apply? Email us at [email protected]. We respond to our most promising candidates promptly.

kaChing is hiring in Palo Alto, CA (on-site only). Looking for backend, frontend, and interns. We're extremely engineering-driven and have a 5-minute commit-to-production cycle. Our CEO says it well:

"[We're disrupting] the mutual fund market, a $10-Trillion industry that has seen no innovation in the past 25 years. The only way to disrupt an industry is to break with conventional wisdom, so we specifically are not looking for people with financial backgrounds. That's why we're the first company to apply an open-source philosophy to improve the process of choosing an investment manager."

By open-source philosophy he means radical transparency and pay-for-convenience; think about if any investments you have come anywhere close to this.

kaChing is hiring. http://www.kaching.com/company/jobs

We're disrupting the mutual fund industry: $11 trillion market. Whoa.

Looking for great hackers: Java, Scala, Rails. Downtown Palo Alto CA. Lots of cool tech and a 5-minute commit-to-deploy cycle.