Some people naively believe that you can refactor your way out of any design mistake or misunderstanding – and that you can use refactoring as a substitute for upfront design. This assumes that you will be able to immediately recognize mistakes and gaps from customer feedback and correct the design as you are developing.
This article will look at how you can easily distribute work to background processes, provide flexible service brokering for your next service oriented architecture, and manage caches efficiently and easily with just PHP and the ZeroMQ libraries.
I’ve always heard that it was difficult to move from QA into development (game design/programming/art/production). I thought this was smart- QA people should be there to be QA people, not doing a job only because they hope it would lead to something else.
The iteration is a cornerstone of agile development. However, the way many teams run their iterations creates serious pitfalls which can keep them from delivering software as effectively as they could.
A puzzler was given before, and all submitted solutions were based on the iteration: x_n+1 = (x_n + x/x_n) / 2. That formula is great for finding good rational approximations of the square root of a number, but it's trivial once you know the formula.
Computing technology has reached a critical level where we are going to see all kinds of amazingly useful (and not just quirky) gadgets. And then people then will find ways to bring them together into single robot models. The jobs of the future will be be in how to make things that are going to make obsolete the things that human beings do.
When I started working for a software house our work was mostly made up of building and fixing, we were told what to build, didn’t do it very well and spent most of our time fixing it. Today our daily activities are a bit different so I thought I’d try to break them down
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value these things... (post includes a big list of craftsmanship posts.
I’m not saying agile is for the elite. Far from it. I’m saying agile is for people who want to and can manage the cultural change that it requires. And, if you try to do many of the technical and project management practices we suggest in agile, you will be better off.
Most often the question someone asks is based on whether or not they should invest their time in a particular programming language or technology versus another. What I give them is the 4 most time-tested skills of importance for a developer