Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

75%

+4 −0

Q&A Request for a Member Story feature which helps to highlight a Codidact member's topic expertise

The idea of the developer story on StackOverflow was to present yourself to potential employers. (For further reading see Introducing the Developer Story or Developer story: first impression where ...

posted 3y ago by Trilarion‭ · edited 3y ago by Trilarion‭

Answer

#3: Post edited by

Trilarion‭ · 2022-01-26T22:06:24Z (almost 3 years ago)

Copy Link

Raw

Markdown

The idea of the developer story on StackOverflow was to present yourself to potential employers. (For further reading see [Introducing the Developer Story](https://meta.stackoverflow.com/questions/313960/introducing-the-developer-story) or [Developer story: first impression](https://meta.stackoverflow.com/questions/320953/developer-story-first-impression) where one can also see example screenshots - basically a vertical timeline) It was some kind of resume, similar to what for example LinkedIn or others are presenting. My guess is that StackOverflow gave up on it in the end, because they could not compete with LinkedIn and the likes.
The "member story" here would have to be quite different. You would have to ask yourself what problem you are trying to solve and give much more details for a feature request to be better assessable by the audience. What benefits would a professional resume on Codidact (a developer story was not so much more in the end) bring to members and what exactly should be on it? This feature request could be filled with more details.
In the end, it doesn't really matter what degrees you have earned for participation here. You simply answer a question and others vote on that. Resumes are more a social network feature than a necessary part of a knowledge transfer platform.
On the other hand, there is this free-form profile field that you can fill with anything (your story if you want). What would a more formalized story give that this free field does not give? Better formatting maybe?
What I plan to contribute to Codidact is a network profile and a network wide landing page. And I think that the network profile should act as something telling others (and yourself) what you have achieved here on Codidact. But that is (badges in tags for example) always also a measure of participation than simply of abilities.
To summarize:
- We should not offer special resume sections because that is not very relevant for Q&A and anyway there are specialized sites like LinkedIn for that. However, if you want put that on your profile and if more special formatting is desired why not.
- We should think about ways to present the amount of work/knowledge/abilities that people have in the best possible way. What are the tags that you are good in, what users are good in a tag. I think this is useful information.

The idea of the developer story on StackOverflow was to present yourself to potential employers. (For further reading see [Introducing the Developer Story](https://meta.stackoverflow.com/questions/313960/introducing-the-developer-story) or [Developer story: first impression](https://meta.stackoverflow.com/questions/320953/developer-story-first-impression) where one can also see example screenshots - basically a vertical timeline) It was some kind of resume, similar to what for example LinkedIn or others are presenting. My guess is that StackOverflow gave up on it in the end, because they could not compete with LinkedIn and the likes.
The "member story" here would have to be quite different. You would have to ask yourself what problem you are trying to solve and give much more details for a feature request to be better assessable by the audience. What benefits would a professional resume on Codidact (a developer story was not so much more in the end) bring to members and what exactly should be on it? This feature request could be filled with more details.
In the end, it doesn't really matter what degrees you have earned for participation here. You simply answer a question and others vote on that. Resumes are more a social network feature than a necessary part of a knowledge transfer platform.
On the other hand, there is this free-form profile field that you can fill with anything (your story if you want). What would a more formalized story give that this free field does not give? Better formatting maybe?
What I plan to contribute to Codidact is a network profile and a network wide landing page. And I think that the network profile should act as something telling others (and yourself) what you have achieved here on Codidact. But that is (badges in tags for example) always also a measure of participation than simply of abilities.
To summarize:
- We should not offer special resume sections because that is not very relevant for Q&A and anyway there are specialized sites like LinkedIn for that. However, if you want put that on your profile and if more special formatting is desired why not.
- We should think about ways to present the amount of work/knowledge/abilities that people have in the best possible way. What are the tags that you are good in, what users are good in a tag? I think this is useful information.

#2: Post edited by

Trilarion‭ · 2022-01-26T22:05:48Z (almost 3 years ago)

Copy Link

Raw

Markdown

The idea of the developer story on StackOverflow was to present yourself to potential employers. (For further reading see [Introducing the Developer Story](https://meta.stackoverflow.com/questions/313960/introducing-the-developer-story) or [Developer story: first impression](https://meta.stackoverflow.com/questions/320953/developer-story-first-impression) where one can also see example screenshots - basically a vertical timeline) It was some kind of resume, similar to what for example LinkedIn or others are presenting. My guess is that StackOverflow gave up on it in the end, because they could not compete with LinkedIn and the likes.
The "member story" here would have to be quite different. You would have to ask yourself what problem you are trying to solve and give much more details for a feature request to be better assessable by the audience. What benefits would a professional resume on Codidact (a developer story was not so much more in the end) bring to members and what exactly should be on it? This feature request could be filled with more details.
In the end, it doesn't really matter what degrees you have earned for participation here. You simply answer a question and other vote on that. Resumes are more a social network feature than a necessary part of a knowledge transfer platform.
On the other hand, there is this free-form profile field that you can fill with anything (your story if you want). What would a more formalized story give that this free field does not give? Better formatting maybe?
What I plan to contribute to Codidact is a network profile and a network wide landing page. And I think that the network profile should act as something telling others (and yourself) what you have achieved here on Codidact. But that is (badges in tags for example) always also a measure of participation than simply of my abilities. The picture will never be very complete and what is it worth then?
To summarize:
- We should not offer special resume sections because that is not very relevant for Q&A and anyway there are specialized sites like LinkedIn for that. However, if you want put that on your profile and if more special formatting is desired why not.
- We should think about ways to present the amount of work/knowledge/abilities that people have in the best possible way. What are the tags that you are good in, what users are good in a tag. I think this is useful information.

The idea of the developer story on StackOverflow was to present yourself to potential employers. (For further reading see [Introducing the Developer Story](https://meta.stackoverflow.com/questions/313960/introducing-the-developer-story) or [Developer story: first impression](https://meta.stackoverflow.com/questions/320953/developer-story-first-impression) where one can also see example screenshots - basically a vertical timeline) It was some kind of resume, similar to what for example LinkedIn or others are presenting. My guess is that StackOverflow gave up on it in the end, because they could not compete with LinkedIn and the likes.
The "member story" here would have to be quite different. You would have to ask yourself what problem you are trying to solve and give much more details for a feature request to be better assessable by the audience. What benefits would a professional resume on Codidact (a developer story was not so much more in the end) bring to members and what exactly should be on it? This feature request could be filled with more details.
In the end, it doesn't really matter what degrees you have earned for participation here. You simply answer a question and others vote on that. Resumes are more a social network feature than a necessary part of a knowledge transfer platform.
On the other hand, there is this free-form profile field that you can fill with anything (your story if you want). What would a more formalized story give that this free field does not give? Better formatting maybe?
What I plan to contribute to Codidact is a network profile and a network wide landing page. And I think that the network profile should act as something telling others (and yourself) what you have achieved here on Codidact. But that is (badges in tags for example) always also a measure of participation than simply of abilities.
To summarize:
- We should not offer special resume sections because that is not very relevant for Q&A and anyway there are specialized sites like LinkedIn for that. However, if you want put that on your profile and if more special formatting is desired why not.
- We should think about ways to present the amount of work/knowledge/abilities that people have in the best possible way. What are the tags that you are good in, what users are good in a tag. I think this is useful information.

#1: Initial revision by

Trilarion‭ · 2022-01-26T22:02:09Z (almost 3 years ago)

Copy Link

Raw

Markdown

The idea of the developer story on StackOverflow was to present yourself to potential employers. (For further reading see [Introducing the Developer Story](https://meta.stackoverflow.com/questions/313960/introducing-the-developer-story) or [Developer story: first impression](https://meta.stackoverflow.com/questions/320953/developer-story-first-impression) where one can also see example screenshots - basically a vertical timeline) It was some kind of resume, similar to what for example LinkedIn or others are presenting. My guess is that StackOverflow gave up on it in the end, because they could not compete with LinkedIn and the likes.

The "member story" here would have to be quite different. You would have to ask yourself what problem you are trying to solve and give much more details for a feature request to be better assessable by the audience. What benefits would a professional resume on Codidact (a developer story was not so much more in the end) bring to members and what exactly should be on it? This feature request could be filled with more details.

In the end, it doesn't really matter what degrees you have earned for participation here. You simply answer a question and other vote on that. Resumes are more a social network feature than a necessary part of a knowledge transfer platform.

On the other hand, there is this free-form profile field that you can fill with anything (your story if you want). What would a more formalized story give that this free field does not give? Better formatting maybe?

What I plan to contribute to Codidact is a network profile and a network wide landing page. And I think that the network profile should act as something telling others (and yourself) what you have achieved here on Codidact. But that is (badges in tags for example) always also a measure of participation than simply of my abilities. The picture will never be very complete and what is it worth then?

To summarize:

- We should not offer special resume sections because that is not very relevant for Q&A and anyway there are specialized sites like LinkedIn for that. However, if you want put that on your profile and if more special formatting is desired why not.

- We should think about ways to present the amount of work/knowledge/abilities that people have in the best possible way. What are the tags that you are good in, what users are good in a tag. I think this is useful information.

Communities

Post History