Starting a new project
-
Right now, I am in the phase of a project that is both the most exciting and most terrifying. Design. I work for a good sized company; not too big, but definitely not small. I have to write a new version of one of our products, and because of a large platform shift it will have to be written largely from the ground up (some math routines and algorithms will be re-used, but not much else). I think I'm in a fairly unique situation in that I am the one, due to my knowledge of the product, that has to come up with the requirements and the design, and will also do the vast majority of the programming. I'm hoping to be able to delegate a bit, but it depends on how busy other developers get. It's a large project for one person, but I've done it before, on the last version of the software. And the one before that. Each generation has had a major hardware platform shift (which I also help dictate), and this is the third one, but it will be the most radical redesign yet. I have started in on the requirements docs and I have to say it's exciting to be increasing the specs to new heights that will put us at the forefront in the field (I think my employer would be pissed if I told you what field it was). But damn, it's also a phase that is prone to writer's block. There's not really anyone more qualified to make the decisions here than me (I first started working on this line of products in 1997, and back then I had to figure it out for myself as all the knowledge had jumped ship). There is an EE and an ME that know a lot about it that I can talk to, but obviously they come from different angles, which can be helpful. Anyway, I've been struggling with a couple of the aspects of the spec, and I feel like I've been spinning my wheels. So I came here to talk about it :) Hope you don't mind. But I was curious about something: how many of you are in this situation, where you get to take 100% ownership of a major project? And do you like it? I imagine it's relatively common at smaller places, but I think I'm lucky to have it at a company this size -- for I do enjoy having it be mine, even though I get as much blame when things go wrong as I get credit when it's successful. The hardest part is trying to put together a schedule. I hate that. But who doesn't? Thanks for letting me get distracted :)
He said, "Boy I'm just old and lonely, But thank you for your concern, Here's wishing you a Happy New Year." I wished him one back in return.
-
Right now, I am in the phase of a project that is both the most exciting and most terrifying. Design. I work for a good sized company; not too big, but definitely not small. I have to write a new version of one of our products, and because of a large platform shift it will have to be written largely from the ground up (some math routines and algorithms will be re-used, but not much else). I think I'm in a fairly unique situation in that I am the one, due to my knowledge of the product, that has to come up with the requirements and the design, and will also do the vast majority of the programming. I'm hoping to be able to delegate a bit, but it depends on how busy other developers get. It's a large project for one person, but I've done it before, on the last version of the software. And the one before that. Each generation has had a major hardware platform shift (which I also help dictate), and this is the third one, but it will be the most radical redesign yet. I have started in on the requirements docs and I have to say it's exciting to be increasing the specs to new heights that will put us at the forefront in the field (I think my employer would be pissed if I told you what field it was). But damn, it's also a phase that is prone to writer's block. There's not really anyone more qualified to make the decisions here than me (I first started working on this line of products in 1997, and back then I had to figure it out for myself as all the knowledge had jumped ship). There is an EE and an ME that know a lot about it that I can talk to, but obviously they come from different angles, which can be helpful. Anyway, I've been struggling with a couple of the aspects of the spec, and I feel like I've been spinning my wheels. So I came here to talk about it :) Hope you don't mind. But I was curious about something: how many of you are in this situation, where you get to take 100% ownership of a major project? And do you like it? I imagine it's relatively common at smaller places, but I think I'm lucky to have it at a company this size -- for I do enjoy having it be mine, even though I get as much blame when things go wrong as I get credit when it's successful. The hardest part is trying to put together a schedule. I hate that. But who doesn't? Thanks for letting me get distracted :)
He said, "Boy I'm just old and lonely, But thank you for your concern, Here's wishing you a Happy New Year." I wished him one back in return.
Sounds like the job I'm finishing right now, except that I did not commit the crime which was its predecessor. And I'm glad it's over.
A while ago he asked me what he should have printed on my business cards. I said 'Wizard'. I read books which nobody else understand. Then I do something which nobody understands. After that the computer does something which nobody understands. When asked, I say things about the results which nobody understand. But everybody expects miracles from me on a regular basis. Looks to me like the classical definition of a wizard.
-
Right now, I am in the phase of a project that is both the most exciting and most terrifying. Design. I work for a good sized company; not too big, but definitely not small. I have to write a new version of one of our products, and because of a large platform shift it will have to be written largely from the ground up (some math routines and algorithms will be re-used, but not much else). I think I'm in a fairly unique situation in that I am the one, due to my knowledge of the product, that has to come up with the requirements and the design, and will also do the vast majority of the programming. I'm hoping to be able to delegate a bit, but it depends on how busy other developers get. It's a large project for one person, but I've done it before, on the last version of the software. And the one before that. Each generation has had a major hardware platform shift (which I also help dictate), and this is the third one, but it will be the most radical redesign yet. I have started in on the requirements docs and I have to say it's exciting to be increasing the specs to new heights that will put us at the forefront in the field (I think my employer would be pissed if I told you what field it was). But damn, it's also a phase that is prone to writer's block. There's not really anyone more qualified to make the decisions here than me (I first started working on this line of products in 1997, and back then I had to figure it out for myself as all the knowledge had jumped ship). There is an EE and an ME that know a lot about it that I can talk to, but obviously they come from different angles, which can be helpful. Anyway, I've been struggling with a couple of the aspects of the spec, and I feel like I've been spinning my wheels. So I came here to talk about it :) Hope you don't mind. But I was curious about something: how many of you are in this situation, where you get to take 100% ownership of a major project? And do you like it? I imagine it's relatively common at smaller places, but I think I'm lucky to have it at a company this size -- for I do enjoy having it be mine, even though I get as much blame when things go wrong as I get credit when it's successful. The hardest part is trying to put together a schedule. I hate that. But who doesn't? Thanks for letting me get distracted :)
He said, "Boy I'm just old and lonely, But thank you for your concern, Here's wishing you a Happy New Year." I wished him one back in return.
Sounds fun. I get a fair portion of projects entirely handed over to me where I'm responsible for pretty much every decision from requirements to code. (Although obviously to some extent the requirements are set by the user/customer). I usually cap projects at what I think looks like ~6 months work. Once we hit that sort of size I cut the detailed discussions short and say that I'll do a version 1 to this spec, then revisit to work out the next phase. I'm lucky enough to have a colleague who knows our company/industry well who I can always bounce ideas off. The company is medium sized, but as we aren't a software focused company, I'm one of only two full time developers.
Simon
-
Right now, I am in the phase of a project that is both the most exciting and most terrifying. Design. I work for a good sized company; not too big, but definitely not small. I have to write a new version of one of our products, and because of a large platform shift it will have to be written largely from the ground up (some math routines and algorithms will be re-used, but not much else). I think I'm in a fairly unique situation in that I am the one, due to my knowledge of the product, that has to come up with the requirements and the design, and will also do the vast majority of the programming. I'm hoping to be able to delegate a bit, but it depends on how busy other developers get. It's a large project for one person, but I've done it before, on the last version of the software. And the one before that. Each generation has had a major hardware platform shift (which I also help dictate), and this is the third one, but it will be the most radical redesign yet. I have started in on the requirements docs and I have to say it's exciting to be increasing the specs to new heights that will put us at the forefront in the field (I think my employer would be pissed if I told you what field it was). But damn, it's also a phase that is prone to writer's block. There's not really anyone more qualified to make the decisions here than me (I first started working on this line of products in 1997, and back then I had to figure it out for myself as all the knowledge had jumped ship). There is an EE and an ME that know a lot about it that I can talk to, but obviously they come from different angles, which can be helpful. Anyway, I've been struggling with a couple of the aspects of the spec, and I feel like I've been spinning my wheels. So I came here to talk about it :) Hope you don't mind. But I was curious about something: how many of you are in this situation, where you get to take 100% ownership of a major project? And do you like it? I imagine it's relatively common at smaller places, but I think I'm lucky to have it at a company this size -- for I do enjoy having it be mine, even though I get as much blame when things go wrong as I get credit when it's successful. The hardest part is trying to put together a schedule. I hate that. But who doesn't? Thanks for letting me get distracted :)
He said, "Boy I'm just old and lonely, But thank you for your concern, Here's wishing you a Happy New Year." I wished him one back in return.
David Kentley wrote:
And do you like it?
Yes. It is way better than having half of the decisions being made by others, without them caring about the half you end up being responsible for.
David Kentley wrote:
trying to put together a schedule. I hate that. But who doesn't?
Nope. Coming up with the budget is part of the job. As is making it all come true. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
Right now, I am in the phase of a project that is both the most exciting and most terrifying. Design. I work for a good sized company; not too big, but definitely not small. I have to write a new version of one of our products, and because of a large platform shift it will have to be written largely from the ground up (some math routines and algorithms will be re-used, but not much else). I think I'm in a fairly unique situation in that I am the one, due to my knowledge of the product, that has to come up with the requirements and the design, and will also do the vast majority of the programming. I'm hoping to be able to delegate a bit, but it depends on how busy other developers get. It's a large project for one person, but I've done it before, on the last version of the software. And the one before that. Each generation has had a major hardware platform shift (which I also help dictate), and this is the third one, but it will be the most radical redesign yet. I have started in on the requirements docs and I have to say it's exciting to be increasing the specs to new heights that will put us at the forefront in the field (I think my employer would be pissed if I told you what field it was). But damn, it's also a phase that is prone to writer's block. There's not really anyone more qualified to make the decisions here than me (I first started working on this line of products in 1997, and back then I had to figure it out for myself as all the knowledge had jumped ship). There is an EE and an ME that know a lot about it that I can talk to, but obviously they come from different angles, which can be helpful. Anyway, I've been struggling with a couple of the aspects of the spec, and I feel like I've been spinning my wheels. So I came here to talk about it :) Hope you don't mind. But I was curious about something: how many of you are in this situation, where you get to take 100% ownership of a major project? And do you like it? I imagine it's relatively common at smaller places, but I think I'm lucky to have it at a company this size -- for I do enjoy having it be mine, even though I get as much blame when things go wrong as I get credit when it's successful. The hardest part is trying to put together a schedule. I hate that. But who doesn't? Thanks for letting me get distracted :)
He said, "Boy I'm just old and lonely, But thank you for your concern, Here's wishing you a Happy New Year." I wished him one back in return.
-
Right now, I am in the phase of a project that is both the most exciting and most terrifying. Design. I work for a good sized company; not too big, but definitely not small. I have to write a new version of one of our products, and because of a large platform shift it will have to be written largely from the ground up (some math routines and algorithms will be re-used, but not much else). I think I'm in a fairly unique situation in that I am the one, due to my knowledge of the product, that has to come up with the requirements and the design, and will also do the vast majority of the programming. I'm hoping to be able to delegate a bit, but it depends on how busy other developers get. It's a large project for one person, but I've done it before, on the last version of the software. And the one before that. Each generation has had a major hardware platform shift (which I also help dictate), and this is the third one, but it will be the most radical redesign yet. I have started in on the requirements docs and I have to say it's exciting to be increasing the specs to new heights that will put us at the forefront in the field (I think my employer would be pissed if I told you what field it was). But damn, it's also a phase that is prone to writer's block. There's not really anyone more qualified to make the decisions here than me (I first started working on this line of products in 1997, and back then I had to figure it out for myself as all the knowledge had jumped ship). There is an EE and an ME that know a lot about it that I can talk to, but obviously they come from different angles, which can be helpful. Anyway, I've been struggling with a couple of the aspects of the spec, and I feel like I've been spinning my wheels. So I came here to talk about it :) Hope you don't mind. But I was curious about something: how many of you are in this situation, where you get to take 100% ownership of a major project? And do you like it? I imagine it's relatively common at smaller places, but I think I'm lucky to have it at a company this size -- for I do enjoy having it be mine, even though I get as much blame when things go wrong as I get credit when it's successful. The hardest part is trying to put together a schedule. I hate that. But who doesn't? Thanks for letting me get distracted :)
He said, "Boy I'm just old and lonely, But thank you for your concern, Here's wishing you a Happy New Year." I wished him one back in return.