One of my team maxims is "Deploy Early and Often." As soon as a minimum viable product is available I want it off the developer's machine and deployed to a server, device, or wherever the final destination is.
Somewhat akin to TDD,
I'm actually expecting the first couple of deployments to fail. Maybe
you're missing a critical JavaScript library or don't have the same
level of access in the test environment as you do locally. These initial
failures are valuable in detecting any hidden or forgotten
dependencies. Ensuring that your product's deployment process is solid
as early as possible will reduce or eliminate the number of nasty
surprises as you approach the end of development. The last thing you
want to do is to earn the dubious 'Works On My Machine' certification shortly before the release.
Whether
your deployment process is manual or based around continuous delivery
get your application out there as soon as possible. Whether you adhere
to Agile or work in Waterfall, don't wait until the last moment to test
your release deployment.
Originally posted on LinkedIn.
Showing posts with label management. Show all posts
Showing posts with label management. Show all posts
Monday, August 25, 2014
Monday, May 5, 2014
New developer? Start with the deliverables.
I have a developer new to the team who has an extensive system
administration background. Due to various factors he has been working on
our build processes
rather than writing a lot of code initially. He mentioned that he
enjoyed taking this approach because it was a "good bridge" to writing
code.
That comment caused me to reflect on whether this might be a good introduction for all new developers. It seems like it, because the end product is what is important to our customers, not how elegant or innovative the underlying code is. Yes, of course, there is great value in well-written, high-performance code but that won't matter if the deliverable is defective to such a degree that the customer rejects it.
So how can one defend against distasteful defective releases? Configuration management is a set of practices that attempts to improve software quality. One of the important principles of configuration management is the concept of repeatable, reproducible builds. A continuous integration (CI) system gets you started down that path by eliminating the disruptive variables associated with the vagaries of what is installed on a developer's machine.
Setting up a build server as part of your CI system isn't a turnkey process however. One frequently needs to rewrite some code or reconfigure dependencies so that the application can be built in isolation on the build server, free from any detritus tied directly to a specific development machine. Once you get to that point you probably start realizing that you should have made some choices differently in the application. Essentially you're working from the outside in, and this viewpoint is really important. Think how much more efficiently the development team can work if projects are initiated with the goal of cleanly building on the build server rather than chasing down build issues specific to one person's development environment. The exercise of having new developers work within the configuration process earlier in their tenure rather than later resonates with me. Understanding the meta pieces that form the application is critical to deploying it, whether it is developers doing the deployment or a release engineering team.
I am more concerned about getting the release right than anything else. Having new developers- even seasoned developers, for that matter- understand the importance of writing code that fits easily into a CI environment is invaluable. For me, this holistic view of the code pays dividends in efficiency and quality.
Originally posted on LinkedIn.
That comment caused me to reflect on whether this might be a good introduction for all new developers. It seems like it, because the end product is what is important to our customers, not how elegant or innovative the underlying code is. Yes, of course, there is great value in well-written, high-performance code but that won't matter if the deliverable is defective to such a degree that the customer rejects it.
So how can one defend against distasteful defective releases? Configuration management is a set of practices that attempts to improve software quality. One of the important principles of configuration management is the concept of repeatable, reproducible builds. A continuous integration (CI) system gets you started down that path by eliminating the disruptive variables associated with the vagaries of what is installed on a developer's machine.
Setting up a build server as part of your CI system isn't a turnkey process however. One frequently needs to rewrite some code or reconfigure dependencies so that the application can be built in isolation on the build server, free from any detritus tied directly to a specific development machine. Once you get to that point you probably start realizing that you should have made some choices differently in the application. Essentially you're working from the outside in, and this viewpoint is really important. Think how much more efficiently the development team can work if projects are initiated with the goal of cleanly building on the build server rather than chasing down build issues specific to one person's development environment. The exercise of having new developers work within the configuration process earlier in their tenure rather than later resonates with me. Understanding the meta pieces that form the application is critical to deploying it, whether it is developers doing the deployment or a release engineering team.
I am more concerned about getting the release right than anything else. Having new developers- even seasoned developers, for that matter- understand the importance of writing code that fits easily into a CI environment is invaluable. For me, this holistic view of the code pays dividends in efficiency and quality.
Originally posted on LinkedIn.
Sunday, March 24, 2013
Management Nugget 1: Avoid The Holiday Time Crunch
Projects with 31st of December deadlines should be started well in advance of the holiday vacation time crunch. To most this is blatantly obvious. Some of our peers, however, act surprised that Christmas comes on December 25th every year and that most people take time off around that time. (Some folks take a LOT of time off!) I was astonished by the number of messages I received on 12/27 regarding projects with deadlines of 12/31.
There is an ancient fable that illustrates this situation: The Ant And The Grasshopper.
Now, don't get me wrong. I am firmly in the camp that believes that ALL of IT is one team, and we all succeed or fail together. And to get even more macro, the entire company stands or falls as one. So, yeah, though it might seem otherwise, I AM a team player.
But...
But what does that say about the person who hasn't managed their projects properly and are now looking for you to bail them out? Does that make them a good team player? How is the greater team helped by someone who doesn't properly manage projects with cross-team dependencies? Or, at the least, ask for help prior to crunch time? Resources have to be diverted, which then impacts quality and timeliness of on-track projects.
A crisis on your part does not constitute an emergency on my part?
Now, don't be a jerk about it, but, as a manager you're going to have to decide how much you can assist at this late point in time. The right thing to do, of course, is to help your fellow human being. There are plenty of metaphors equating the corporate world as a brutal jungle, but I hope that your workplace isn't a Darwinian struggle for survival.
There is a corollary to the section title above: Poor planning on your part does not constitute an emergency on my part. The bottom line is that you shouldn't get into this situation in the first place. Plan for contingencies. Look at a calendar when you are planning a project schedule. If YOU are the one that has run out of time it's always better to admit that you're not going to complete the task(s) at hand on time.
Conclusion
I am not claiming that I'm covering new ground with this post. I'm merely describing a management anti-pattern that seems to be popular in some organizations.
Background
This is part of a larger series of planned posts: Management Nuggets
There is an ancient fable that illustrates this situation: The Ant And The Grasshopper.
Now, don't get me wrong. I am firmly in the camp that believes that ALL of IT is one team, and we all succeed or fail together. And to get even more macro, the entire company stands or falls as one. So, yeah, though it might seem otherwise, I AM a team player.
But...
But what does that say about the person who hasn't managed their projects properly and are now looking for you to bail them out? Does that make them a good team player? How is the greater team helped by someone who doesn't properly manage projects with cross-team dependencies? Or, at the least, ask for help prior to crunch time? Resources have to be diverted, which then impacts quality and timeliness of on-track projects.
A crisis on your part does not constitute an emergency on my part?
Now, don't be a jerk about it, but, as a manager you're going to have to decide how much you can assist at this late point in time. The right thing to do, of course, is to help your fellow human being. There are plenty of metaphors equating the corporate world as a brutal jungle, but I hope that your workplace isn't a Darwinian struggle for survival.
There is a corollary to the section title above: Poor planning on your part does not constitute an emergency on my part. The bottom line is that you shouldn't get into this situation in the first place. Plan for contingencies. Look at a calendar when you are planning a project schedule. If YOU are the one that has run out of time it's always better to admit that you're not going to complete the task(s) at hand on time.
Conclusion
I am not claiming that I'm covering new ground with this post. I'm merely describing a management anti-pattern that seems to be popular in some organizations.
Background
This is part of a larger series of planned posts: Management Nuggets
Monday, January 7, 2013
Management Nuggets: Priceless Wisdom Dispensed For Free
For better or worse I have been in IT management for almost 8 years. I haven't been fired, demoted, sued, or assaulted (yet!) so I must be doing something right. I have designed, developed, and managed projects of varying scope, from trivial departmental utilities to enterprise applications. Maybe some day I'll get around to that book I've been threatening to write for so long, but until then it's time to give back to the larger community for the greater good.
Monday, March 1, 2010
Who gets the money?
Recently I had to decide on merit salary increases. One of the toughest decisions came down to a couple of folks that I'll call Yin and Yang.
Yang is an expert developer, technically brilliant, always has a clever answer to a problem.
Yin is dependable, reliable, always gets the job done. I can always count on Yin to cheerfully accept and complete any task.
But...
Yang's hubris sometimes causes careless mistakes. Yang is also high maintenance, frequently requiring meetings to discuss the most minute of details and risks. Yang requires a surprising amount of micromanagement to ensure that assignments stay on track, and don't veer off into the realm of overarchitecture.
Yin stopped learning new things years ago. Yin gets the job done through brute force.
Ultimately I ruled in favor of Yin. Both developers adequately complete their tasks but take different approaches. Both are important parts of the team. I went with the person who made my life easiest. Though Yang's solutions are technically superior to Yin's, at the end of the day the user doesn't care about elegant code- users just want their applications to work.
Yang is an expert developer, technically brilliant, always has a clever answer to a problem.
Yin is dependable, reliable, always gets the job done. I can always count on Yin to cheerfully accept and complete any task.
But...
Yang's hubris sometimes causes careless mistakes. Yang is also high maintenance, frequently requiring meetings to discuss the most minute of details and risks. Yang requires a surprising amount of micromanagement to ensure that assignments stay on track, and don't veer off into the realm of overarchitecture.
Yin stopped learning new things years ago. Yin gets the job done through brute force.
Ultimately I ruled in favor of Yin. Both developers adequately complete their tasks but take different approaches. Both are important parts of the team. I went with the person who made my life easiest. Though Yang's solutions are technically superior to Yin's, at the end of the day the user doesn't care about elegant code- users just want their applications to work.
Subscribe to:
Posts (Atom)