BitBucket user flowblok posted code for his IRC bot named "challenge-bot." It's pretty short. Only 155 lines. He has Python to thank for that. Another cool technology you can see in use within his code is ZeroMQ.
DevOps isn’t just a set of tools, but a philosophical shift that needs that requires buy-in from all folks involved to really succeed. It’s only through a high level of collaboration that things will change for the better.
If you've read the ZeroMQ docs before, you probably noticed a few pockets of good old-fashioned corny nerd humor. It seems that the creators and the rest of the ZeroMQ development community had a little fun when creating their docs. Maybe other open source projects should follow their example.
Twitter-Harvest is a Python script that utilizes the Twitter REST API v1.1 to retrieve tweets from a user’s timeline and insert them into a MongoDB database. It takes care of the nitty gritty and allows you to explore what makes MongoDB great.
This video has a double-header of presentations. The first is on twelve best practices for the Go programming langauge, and the second presentation, which starts after the 50 minute mark, is about using ZeroMQ with Go.
Learn about the new utilities for Dropbox and SkyDrive. Then you'll have to see if you fall in love with Angular and Python 3.4. Plus, have fun with the developer excuse generator and the startup legitimizer.
The scenario - you integrate three applications, two client HTTP ones and the third is a backend one (no matter the technology). All is well except client1 tends to send requests in bursts for no good reason and its developers just cannot tame it.
Writing C extension modules for Python is tricky: the programmer must manually manage reference counts and the exception state, in addition to the usual dangers of coding in C. CPyChecker is a new static checker being developed by David Malcom to rescue us from our mistakes.
See how to use Zato (a Python-based ESB) to integrate ZeroMQ, AMQP, JMS WebSphere MQ and more in a pass-through manner using 2 lines of code. The article goes through Zato's main features and characteristic aspects.
Why do we all know a developer who has been pounding out unmaintainable code for a decade or more? Why do people "believe in TDD but I don't have time to write tests during crunch?" How is it that we have an entire industry based around rescuing teams from acutely awful Rails apps?