Category: Editorial

  • Bug Management

    All of our software has bugs. Some bugs are just bad code, some are incorrect specs, and some are things the client thinks should work differently than the way the application is built. In any case, we know there are plenty of bugs in software.

    How companies handle bugs is interesting. Some feed these back to the current developer team. Some use junior developers to do bug work. Some have support teams that focus on bugs and coordinate with developers.

    What if you get parts of your software from another source? More and more developers are using open source libraries, packages, frameworks, and more. How do you deal with bugs in those situations? As someone that has worked in this manner, tackling those bugs yourself is problematic and introduces other issues with your software development pipeline when the upstream source is updated.

    Google is taking a different approach, actually assigning developers to projects that they need. One example is in this piece, about a couple developers assigned to the security of Linux. While the headline is that they keep finding lots of bugs, the more interesting part to me is that Google internally builds the OSS they use from source, add in their patches, and then use pull requests to get them accepted into the main project.

    I don’t know that many of us can afford to sponsor a developer to contribute to a project full time, but I do like the idea of using a fork to build your software from source. This might not prevent bugs or malware, but if you are hit in this manner, you know that lots of others will be as well.

    Steve Jones

  • DevOps in Space

    Some of the early science fiction books I read were by Robert Heinlein, often including rocket ships and space travel. These days I’m uninterested in actually going to space, but I am excited by the prospect of the efforts being made to send others. It’s an exciting time to be interested in travel off of this planet.

    One of the headline makers is SpaceX, which has had quite a bit of success launching reusable rockets carrying all sorts of cargo. My son was very interested in their work as an 18 year old, and I still remember taking him to Cape Canaveral and watching the first first rocket launch and land at the facility. An exciting time for us.

    SpaceX has adopted a DevOps attitude towards their physical rockets, adapting and iterating quickly to improve their designs. The pace of progress is quite interesting, analogous to how some companies have changed their software development lifecycle practices, becoming quite adept at building and improving applications in a rapid fashion. Alex Yates draws some parallels, and includes lots of fascinating rocket information, in this post on the Octopus Deploy blog.

    One of the big challenges I find with changing software development is that we struggle to let go of old practices. Even as we look to iterate, often we are unable to accept risk, and we often want to stick with the “always done it this way” for some things. While we might accept some changes, we don’t accept others, and may even cancel out the benefits of automation improvements with a lack of willingness to adapt our culture.

    I do hope that other companies challenge SpaceX, and learn from them. Ultimately we do better with a competitor that forces them to continue to improve and not rest on past success. The same is necessary for software development teams to continually improve. If your organization is stuck in a rut with software development, request (or push) for a team to try something new. To adopt and grow with DevOps. Make them prove they can build, deploy, and operate software in a better way. Then challenge other teams to try and adopt their ideas, and then improve upon them over time.

    Steve Jones

  • Easing Back to the Office

    Much of the tech world moved to remote work last year when the pandemic started. Various companies started to announce future dates during which they’d guarantee workers the ability to work from home. That was helpful, as many needed to plan for child care, parent assistance, and more. My company kept pushing the date out, and early this year (or late last) said that we would have the option through all of 2021.

    Microsoft had various announcements, but one was that employees could work from home permanently. For less than 50% of their time. The headlines downplayed the restriction, though I was glad to see some flexibility. Now, Microsoft is starting to allow some workers back to campus, noting that they are on step 4 of their 6 step dial. This is 57,000 workers, which is quite a few. Masks and social distancing are still required.

    While a good portion of employees want flexibility, and many prefer remote work, there are a good number that want to return to an office and be around other people. While Microsoft, and my employer, both want to embrace the changes of the last year, finding a balance between the past and future is hard. I thought that Microsoft’s blog on embracing a flexible workplace echoes a lot of what I hear from my company and a few others. We want to work with you, but there might be some restrictions. Certainly tax implications are a part of this for my company, and perhaps for Microsoft as well.

    I honestly am not quite sure how I want the future to work. While I appreciate remote first, and I like the idea of everyone being somewhat a peer during meetings, I also value getting people together. I don’t really look forward to going to an office and logging onto Zoom from a desk. I want to see people in conference rooms, able to discuss, debate, and brainstorm solutions for the future.

    For technologists, this might be easier. I could see more whiteboards, like Mural, in use in meetings, allowing remote people to participate in similar ways to those in the room, but I until we get something that creates some sort of virtual presence, I’m not sure that we will really see a good blend of in-person and remote attendees. I hope companies work on solutions like this, as the world has changed and in person attendance will still matter.

    Steve Jones

  • You’ve Changed. Has Your Employer?

    This past year has been one to remember. It’s disrupted lives and changed the world in many ways. Whether you have been cautious or fearless, scared or angry, the pandemic has changed you and the world. There’s an interesting read at Fast Company about life during the pandemic and how life has been turbulent from one point of view. 

    While I related to some of what the author wrote, I didn’t relate to a lot of it. I also know I’ve been lucky, and relatively lightly affected by this pandemic. I’ve published, and needed, coping tips at times, but I’ve been able to live my life, get outside, still coach youth, still visit some restaurants and take some limited vacations. I’ve looked back periodically, recording how I feel about life. I’ve changed, and I’ve struggled, but I’ve also been able to do things and I didn’t have the lockdown, and the limited life that some tech pros had, and I certainly didn’t have the struggles with security and finances that many less privileged dealt with.

    I’ve also had a great company that recognized issues last February and started preparing us, even before the UK went into a lockdown. While I haven’t visited with fellow employees in person, we’ve adapted and continued with some level of success for over a year. We hire and onboard people, software is getting written and sold, and business moves on, in many ways a reasonable facsimile of what we did in 2019.

    We’ve also changed. Remote offices have closed. A limited, experimental opening has few people actually taking advantage of going to work in a group. We’ve adopted and abandoned some of the early coping meetings and are looking for new ones. We’ve promised people they can move away from a city with an office, though remain within a reasonable travel time, for the rest of the year. All to provide some stability and allow employees to make concrete future plans for more than the next few months.

    We are experimenting with remote first, which is an attempt to adapt for the future to a distributed workforce, including our annual reteaming. I suspect trips to the office for many, including me, will be rarely scheduled, and used more for team building and brainstorming, with less tactical, let’s do something for today, work. I’m hoping we still do get together, but time will tell.

    I wonder how many of you will see your work change. We’re the privileged group, working in a field where we can accomplish tasks without physical interaction, but one where many of us might find that we do crave some sort of social touch. Maybe the world has changed it, and maybe it’s changed some interactions, but I also suspect some companies are looking forward to returning to the world as it was in 2019.

    Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.