You know I love you Adam, but please don't use real names in any of these stories going forward (unless the story is about how awesome someone is). Just use neutral, made up name that don't suggest ethnicity or an actual person that can be easily tracked down using linked-in.
I've also grappled with similar situations and I guess what's missing for me here is how you've grown and changed as a result of this whole ordeal or what you could have done better.
For example, I saw people successfully transition from devs to product/project managers or technical sales in similar scenarios (not to say that programming is superior to these professions, just that it requires a different skillset and might be better suited).
Cheers
I've also grappled with similar situations and I guess what's missing for me here is how you've grown and changed as a result of this whole ordeal or what you could have done better.
I hear you. But I specifically decided that the Tales From The Dev Side series would be just that - tales. Not lessons. Or best practices. Just... tales. And I totally get that won't appeal to everyone.
All my other "normal" articles are basically extensions of my real-life experiences, with additional information about how I've changed, or what I've learned. As for this particular story, there are, quite literally, about a half dozen different takeaways (for me), and I didn't wanna make it even longer by adding a whole bunch of preachy "what have we learned today?" findings.
I just wanted to tell the story. I'll do others like that in the future. Just telling that story - and letting the readers draw what they will from it.
I didn't mean in a preachy way but in a "in good storytelling the main character (you) usually grows and changes" way.
It is your story though and you can tell it however you like. I fully respect that.
Some comments have been hidden by the post's author - find out more
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.
You know I love you Adam, but please don't use real names in any of these stories going forward (unless the story is about how awesome someone is). Just use neutral, made up name that don't suggest ethnicity or an actual person that can be easily tracked down using linked-in.
I've also grappled with similar situations and I guess what's missing for me here is how you've grown and changed as a result of this whole ordeal or what you could have done better.
For example, I saw people successfully transition from devs to product/project managers or technical sales in similar scenarios (not to say that programming is superior to these professions, just that it requires a different skillset and might be better suited).
Cheers
I hear you. But I specifically decided that the Tales From The Dev Side series would be just that - tales. Not lessons. Or best practices. Just... tales. And I totally get that won't appeal to everyone.
All my other "normal" articles are basically extensions of my real-life experiences, with additional information about how I've changed, or what I've learned. As for this particular story, there are, quite literally, about a half dozen different takeaways (for me), and I didn't wanna make it even longer by adding a whole bunch of preachy "what have we learned today?" findings.
I just wanted to tell the story. I'll do others like that in the future. Just telling that story - and letting the readers draw what they will from it.
I didn't mean in a preachy way but in a "in good storytelling the main character (you) usually grows and changes" way.
It is your story though and you can tell it however you like. I fully respect that.