PluckyPleco
Newly Enlightened
- Joined
- Oct 29, 2003
- Messages
- 65
Peter,
By now you've probably realized that the software/firmware in the LS4 is a significant investment. You probably consider Arc a flashlight company, but knowingly or unknowingly you've also become a software company...
I've made (a lot of) money, reverse engineering business critical embedded software for companies who didn't realize that they were in the software business until too late. Also led software and system development teams for 15 years. I've got a couple of concerns that you might want to think about...
1) If your current software guy gets hit by a bus tomorrow morning, can you (somebody other than the software guy) find, build and install the most recent stable version?
2) Can you find, build and install the next to last stable version? The current test / unstable version?
3) Who, other than your current software guy can work on the code?
If you (as a company/development organization) aren't already using some form of SW configuration management / source control, I would recommend looking into CVS, RCS or SCCS (all free, listed in decreasing capability/complexity).
If you are not already doing code walkthroughs or inspections:
Once you believe you have a "final" "stable" version, I would recommend that you invest the time to do a top-to-bottom code walk through (yes, it will take DAYS) with two or three software people you trust. This will serve two purposes.
#1 Any defects you catch in the walk through will not make it to the field, saving you BUNCHES of money...
#2 You will then have 3 or 4 people familiar with the code (the software guy plus the reviewers you trust) rather than just the software guy.
If, by looking at how the LS4 development has been impacted by the software, you realize how important the software is, it makes sense to do some risk avoidance/mitigation on that asset.
Experience dictates you will encounter one of four responses to discussing this with the software guy.
1) He goes ballistic, claiming that you don't trust him and are trying to micro-manage him. (Ya got trouble long term...)
2) He agrees that these are important and will get to them "real soon" or "after the code is done." (Standard answer)
3) Sees them as really good ideas and spends the day or two needed to get them up and running RIGHT NOW. (He's a keeper.)
4) Says "well... duh... Been doing that all along, here are the stats, wonder why it took you so long to ask." (a true diamond).
My $0.02US.
Free advice, take it or leave it as you see fit.
PluckyPleco
By now you've probably realized that the software/firmware in the LS4 is a significant investment. You probably consider Arc a flashlight company, but knowingly or unknowingly you've also become a software company...
I've made (a lot of) money, reverse engineering business critical embedded software for companies who didn't realize that they were in the software business until too late. Also led software and system development teams for 15 years. I've got a couple of concerns that you might want to think about...
1) If your current software guy gets hit by a bus tomorrow morning, can you (somebody other than the software guy) find, build and install the most recent stable version?
2) Can you find, build and install the next to last stable version? The current test / unstable version?
3) Who, other than your current software guy can work on the code?
If you (as a company/development organization) aren't already using some form of SW configuration management / source control, I would recommend looking into CVS, RCS or SCCS (all free, listed in decreasing capability/complexity).
If you are not already doing code walkthroughs or inspections:
Once you believe you have a "final" "stable" version, I would recommend that you invest the time to do a top-to-bottom code walk through (yes, it will take DAYS) with two or three software people you trust. This will serve two purposes.
#1 Any defects you catch in the walk through will not make it to the field, saving you BUNCHES of money...
#2 You will then have 3 or 4 people familiar with the code (the software guy plus the reviewers you trust) rather than just the software guy.
If, by looking at how the LS4 development has been impacted by the software, you realize how important the software is, it makes sense to do some risk avoidance/mitigation on that asset.
Experience dictates you will encounter one of four responses to discussing this with the software guy.
1) He goes ballistic, claiming that you don't trust him and are trying to micro-manage him. (Ya got trouble long term...)
2) He agrees that these are important and will get to them "real soon" or "after the code is done." (Standard answer)
3) Sees them as really good ideas and spends the day or two needed to get them up and running RIGHT NOW. (He's a keeper.)
4) Says "well... duh... Been doing that all along, here are the stats, wonder why it took you so long to ask." (a true diamond).
My $0.02US.
Free advice, take it or leave it as you see fit.
PluckyPleco