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.
"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."
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.
Of course QA knows how to program. But their skillset is about breaking code. It's about writing this crazy C++ function that shows how your API has a security bug in this case. As developers their like dev tools developers as their customers are generally devs.
Skillset maybe isn't the right word... mindset maybe better word. Both should be good programmers -- in fact you'll often have more test code than product code. But you likely won't be able to switch your dev team to QA and vice-versa and get the same results.
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
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.
I've considered it, but that wasn't the use case for nodebot. In order to do some of that, you'd need to be able to run commands on the machine the bot is running on, or have the bot keep some log of state as messages are fed into it, both of which are somewhat non-trivial in terms of storage/query-ability or security. We have a few modified bots (supybot is the most common, I think) that developers have written and run themselves, but I don't think any of them are much more than playthings.
I could definitely see having the ability to allow a bot change the topic of a channel though, so, for example, the deployment status channel's topic shows the most recent version deployed, or the status of the current deployment, for those case where you're not sitting in the channel. Also, the ability to control nagios from IRC would be interesting, but we just use shell scripts for that right now (which is non-ideal in other ways).
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.
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 arosien@box.com!
.. Adam