Slashdot Mirror
Simplifying Commercial Software Development?
NerdOfPrey writes "I'm nearing completion of development and testing of my first self-produced commercial application, but just beginning to appreciate the full bevy of other associated tasks ahead. There are help files to compile, end user license agreements to write, a website to create - and a secure online payment system to identify and integrate, automated installers to build, logos to design, marketing, and so on. Are there any good web-based single sources of information covering these sorts of issues? I've never had to do all of these things myself in the past; a comprehensive 'small developers guide' would be of considerable benefit." So is there anything besides "imitate, guess and pray" for all the tasks that come after the app is written?
This is what we call division of labor. If you write software, like I do, then you should not be doing those other things. A graphic designer should make the website. A data entry person should enter in all the information. An interface designer should make the GUI. I think a big problem with jobs being hard to find, besides outsourcing, is companies pushing fewer people harder so they can hire fewer people and pay less money. I was just on a project that pushed me to do craptons of overtime, even on weekends. I will never do that again.
If you are a software developer you do your job of developing software. Anything else you tell the boss you don't know how to do that. Also be sure to note that you can learn to do it, but it will take time and money. And since this will be your first time doing it, you probably wont do the greatest job despite great effort. If your boss has half of a brain they will hire other people to do the other parts. If not, then work at your usual pace leaving the parts you don't know until laste. When the project is late, say I told you so!
Oh, and if losing your job worries you then grow some nuts and watch office space. There's more to life, its not worth it.
The GeekNights podcast is going strong. Listen!
You mean having to read header files isn't end-user documentation?
(don't even ask me about installing MythTV on a machine with 100% Linux compatibility... UGH!) (I'm sure it's me...)