I am now a retired software engineer with experience developing and maintaining telephony applications, desktop UNIX system software, hardware and software performance characterization, software system and applications testing.
I was once a software architect for a project to enable different Email systems to work together until better solutions were developed and I also pointed teams to some of those "better" efforts. I only had one or two good ideas for new projects, but I have written many much smaller tools to promote either faster access to software or convenience tools for keystrokes, keypad mappings, etc.
My emphasis has always been on solving practical problems; inventing something new takes time and many tries with more "failures" than success. All inventors, even the most prolific ones in any profession have more failure than success. The successful inventors make the most mistakes and often stumble on the solution. Look at Edison or some of the software inventors.
Even Microsoft, IBM, Linux developers, and so on have just as many "busts" as the rest of us; the ones using "free" and "open" software may even have their old "junk" out in the open, but with openness is the potential for multiple solutions and for collaboration; we ought to remember that we don't have to do it all ourselves.
A senior engineer may be in charge, but it could be the "newbie" who comes up with a great idea we have not considered.
The best way to go about our day is to share both our success and our failure; an honest look may in the long run bring out the best (and worst) in everyone; thanks for the transparency; it shows that you DO have experience and that experience is of great value!
You are right about looking at both the successes and failures. We often hear about the "overnight" successes, but not the X number of failures those same people had before that success.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am now a retired software engineer with experience developing and maintaining telephony applications, desktop UNIX system software, hardware and software performance characterization, software system and applications testing.
I was once a software architect for a project to enable different Email systems to work together until better solutions were developed and I also pointed teams to some of those "better" efforts. I only had one or two good ideas for new projects, but I have written many much smaller tools to promote either faster access to software or convenience tools for keystrokes, keypad mappings, etc.
My emphasis has always been on solving practical problems; inventing something new takes time and many tries with more "failures" than success. All inventors, even the most prolific ones in any profession have more failure than success. The successful inventors make the most mistakes and often stumble on the solution. Look at Edison or some of the software inventors.
Even Microsoft, IBM, Linux developers, and so on have just as many "busts" as the rest of us; the ones using "free" and "open" software may even have their old "junk" out in the open, but with openness is the potential for multiple solutions and for collaboration; we ought to remember that we don't have to do it all ourselves.
A senior engineer may be in charge, but it could be the "newbie" who comes up with a great idea we have not considered.
The best way to go about our day is to share both our success and our failure; an honest look may in the long run bring out the best (and worst) in everyone; thanks for the transparency; it shows that you DO have experience and that experience is of great value!
Thank you.
You are right about looking at both the successes and failures. We often hear about the "overnight" successes, but not the X number of failures those same people had before that success.