So here I am in New York, all alone and looking for something fun to do during a rainy day preceding QCon New York. The Empire State Building was covered in clouds so what can you do?
Your organizational structure drives a particular software architecture. And your software architecture drives a particular organizational structure. People who work closely together and communicate frequently will create software that reflects this and vice versa.
Writing code for a living can make you fat. That’s because coders work long hours behind a computer and don’t have much time for exercise. Here’s what you can do about it.
Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (June 6 to June 13). This week's topics include antifragility, agile transformation and executive engagement, Heisenberg developers, dealing with burnout and Scrum.
When I speak to people (including Agile coaches) from other companies, I tend to see and hear a lot of interesting perspectives. Many buy into the idea of Agile being this cultural shift with everyone sitting around a campfire singing Kumbaya and feeling all happy.
"It seems that agile ideas such as pair programming, lack of code ownership are neither new nor revolutionary. Had we only forgotten about them? At what point did we decide to isolate developers in cubicles or tie their salary to the lines of code produced?"
I listened to the recording of Michael Coté's keynote on the second day of DevOpsDays Austin and I felt like a few of my questions have been answered with respect to DevOps and PaaS. Bottom line: while change is happening, it seems to be moving at slower pace than expected.
As tech companies implement all sorts of ways to increase their output, the often-undiscussed tradeoff is how it impacts employees.
Developers are used to thinking in an extremely abstract way. They take a complicated problem and simplify it to a point where it is simple enough to describe in a list of instructions sent to a computer processor.
The most important facet of agile development in a fast-moving workplace is communication – without it, processes can fall apart and deadlines can fail to be met. In a blog post, agile coach Lorraine Pauls Longhurst works through some issues she's faced as an expert.
I think this bias pervades our culture so much that we're shortchanging ourselves. Having worked with a number of rockstar quality technologists who happened to be female, I wonder how many there might be that are shying away for whatever reason.
At the end of the day, it is about creating the necessary conditions for employees to become engaged and empowered to do their jobs as good as possible. Remove all friction. Love synergy, hate waste.
For a long time I had a difficult time reconciling that both the cowboy coders and the meticulous software craftsmen are able to achieve extraordinary results.
My last few months of working with a larger, more traditional organisation has lead me to conclude that the roles and processes involved in traditional project management only serve to get in the way of creating something meaningful.
Developers attach quickly to tools because they are concrete and have well defined behavior. It is easier to learn a tool than to learn best practices or methodology. Tools only assist in solving problems, they can't solve the problem by themselves.
I recently finished the book Antifragile – Things that Gain from Disorder by Nassim Nicholas Taleb. I liked it a lot, and I think the ideas in it are quite useful when examining various systems and phenomena. What especially struck me when reading it was how much of it applies to software development.
Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (May 30 to June 6). This week's topics include non-programming programmers, being Turing, Async standups, 1-person scrum and stand-up meetings.
You can not observe a developer without altering their behavior.
Most people are familiar with drawings or raffles and some of these events require that you must be present to win. A highly successful Agile Transformation happens when there is executive engagement throughout the path to agility.
There are a lot of things that can break us out of flow or prevent us from ever entering that state of immersion in our work, that are out of our control
In the end as long as the meetings you have are clear and focused and relevant to all parties then, for me, it doesn’t really matter if you are standing up or sitting down.
If there is one theme that is weaved through all of Agile’s principles and practices, it is feedback. TDD. Pair programming. Continuous delivery. Stories. Estimation. Reviews. Retrospectives. On-site customers. Feedback comes up against and again. Feedback from code, the team, and users.
A lot of people are cynical. Well, we tend to be pretty cynical as a culture. Whenever someone does something, we tend to sneer them and we tend to talk about why things can’t work.
Their message boils down to committing often, writing descriptive commit messages, making branching a logical process and making sure to have other eyes on your work.
There is a phenomenon common in many vehicular sports that occurs when the driver’s gaze is focused too near the front of the vehicle. With the field of vision narrowed, the pace at which the world around you moves seems to speed up.