From a user viewpoint, "paving the cowpaths" means that the legacy usability issues have now been modernized without being fixed. The issues remain. A dumb business process is now implemented in a modern programming language. It's still a dumb business process.
Here’s the thing about security – you can’t just “do it” then move on. What I mean by this is that it’s a continuous process and thinking that you only need to just implement some secure coding standards or scan the website once before go live leaves a great big hole in your process.
At DevCon TLV I gave this presentation about code coverage, and how we can use, and misuse it. Here are the slides. You can still catch it in webinar form in a week’s time on the Typemock channel.
If I were to suggest that you implement Microsoft Dynamics AX 2012 in your life, you might give me a strange look. But if you have experience implementing Dynamics AX, and especially AX 2012, for clients or your own company, maybe my suggestion won't seem so strange.
As pointed out by John E. Vincent in his blog Configuration Drift and Next-gen CM, configuration management systems aren’t assertive enough. They are designed to verify the state of a resource at the point they run.
Here's a moderately sized list of Books, Blogs, Articles, Podcasts, and Videos about DevOps, Continuous Delivery, and workplace culture. From the blog "Opus Magnus"...
This is PuppetLabs' State of DevOps survey, which polled over 4,000 IT practitioners. They found out some interesting things, which you can see in the infographic.
Continuous Deployment is an awesome-save, process-changing, team-loving, kudos-earning, stress-reducing capability that any team is wise to implement. OnCheckin is definitely aiming to bring this awesome’ness to as many ASP.Net developers as possible by making it fast and easy to setup.
This week we're talking to Zac Gery about what he calls the biggest misunderstood problem in the development world -- not to mention his love of curling.
I’ve recently seen a spate of engineers declaring boredom and/or dissatisfaction with their current roles and responsibilities, which leads them to openly question what options are available.
It’s really nice if you can decouple your external API from the details of application segregation and deployment. On my current project we’ve building a distributed service oriented architecture that also exposes an HTTP API, and we’re using a reverse proxy to route requests addressed to our API to individual components...
I am a fan of Capistrano from way back and we use it for almost all kind of deployments - Hadoop, MongoDB clusters and so on. If you have not tried Capistrano, you must try it and figure out how you can use for deployments in your environment.
This is a classic DevOps presentation from a former Velocity conference that I thought people could take another look at or see this for the first time. It's definitely worth it.
Andy Parker gives a quick-but-dense talk at Puppet Camp Austin on the fundamentals of testing and test-driven development.
Here's a 14-minute discussion about the future of DevOps presented by Patrick Debois.
It’s been to years ago, I’ve released my own project - Trackyt.net. Month ago I’ve cancelled my VPS lease contract, so your would not see it available at http://trackyt.net anymore.
We’ve covered the controversy of a DevOps Team on this blog before. DevOps Teams are dangerous in that many organizations realize that their Dev and Ops groups . . .
Maintainable software projects usually take the issue tracker seriously. More often, it is used not only to monitor bugs and defects, but also to serve as a task tracker.
Automated configuration tools (such as CFEngine, Puppet, or Chef) allow you to specify how servers should be configured, and bring new and existing machines into compliance. This helps to avoid the problem of fragile SnowflakeServers.
Careful study of the HamCalc shows a number of quirks. Some are funny, some are just examples of the need for unit test frameworks.
At Tangent we handle environment-specific configuration of Django projects using the method outlined by David Cramer. This involves distinguishing between core settings (which we keep in core/default.py) and environment specific settings (eg core/stage.py, core/test.py).
Automated configuration tools (such as CFEngine, Puppet, or Chef) allow you to avoid SnowflakeServers by providing recipes to describe the configuration of elements of a server.
Some additional points on using Python 2.7 in a way that bridges the gap to Python 3.2. The steps are small and simple. You can start taking them now.
Design Patterns above claims that programming to an interface and not an implementation reduces implementation dependencies, and thus it follows that ptainai reduces the probability of ripple-effects. But is this true?
Are you using Celery to process python backend tasks asynchronously? Have you wanted to get insight into their resource consumption and efficiency? Here’s a few useful ways to get insight into Celery performance when running tasks.