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.
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.
I may not have the stamina and fortitude to continue for decades, but I cannot just sit idly by as technology blindly marches forward. I have to understand how it all works and push back, hoping to influence the course we take.
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.
This ultimately comes down to the idea that the involvement of developers doesn’t end at their last commit. Collaboration is key which allows every developer to play a key role in keeping the site up and running, for more happy users. After all software with no users has no value.
Last month the massive Heartbleed security vulnerability was exposed. Three weeks later a security flaw in Microsoft Internet Explorer was revealed. It seems as though every few months there is news of a security breach or vulnerability.
The best way of changing your display depending on screen size is to use media queries to find out the size viewport of the screen and allowing you to change the design depending on what screen size is on.
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.
So there's a bunch of cool scientific research projects that use hundreds of thousands of users' free CPU cycles for saving lives, finding aliens, whatever. But everyday development needs lots of computing power too. What if you could use the same distributed system for builds?
How many times have you tried to use an API only to find that you had to fill in some ridiculous number of parameters with values that you had no idea about? If you’ve ever done Windows programming and had to call into some of the Win32 APIs, I’m sure you’ve experienced this pain.
This post explains how different devices in my home connect via Wi-Fi and provide an easy way of streaming media contents. In this setup I create a playlist in one location (NAS) and all other devices can consume it.
While the changes in 3.9.0 were relatively minor, they open the door to getting some interesting features into 4.0. Here are some of the high-level features I think should make it in to 4.0:
As software developers we spend a large amount of time learning. There is always a new framework or technology to learn. It can seem impossible to keep up with everything when there is something new every day.
I hate “Agile” Initiatives because of the damage they usually cause. The problem is that when people start thinking that “Agile” is the goal they start to use “Agile” as a Whip or a Shield.
So how do we test for both WebSockets and MozWebSocket? Here’s how: