Skip to main content
added 45 characters in body
Source Link
Khaled.K
  • 5.9k
  • 11
  • 6

TL;DR:

We're replacing CVs with something you can use even if you aren't currently looking for a job.

TL;DR; Customizability is important

  1. Replacing CV/Portfolio is a bad idea, this should be a separate feature; since they represent two different things.

  2. Developer Story should be customizable, utilizing things like favorites & options to control statistics.

  3. The term "Developer Story" would lead employers to assume it means the timline of your professional projects & honorable jobs they had over the years, as a developer. Technically, this isn't your story as a developer, it is your story on Stack Overflow.

  4. Statistics should show where most of your contributions are, in relation to tag-groups. Tag-groups are like the group of tags related to database, like transaction, sql, plsql, ..etc. Leaving customizing this to the user would solve its shortcomings.

TL;DR:

We're replacing CVs with something you can use even if you aren't currently looking for a job.

  1. Replacing CV/Portfolio is a bad idea, this should be a separate feature; since they represent two different things.

  2. Developer Story should be customizable, utilizing things like favorites & options to control statistics.

  3. The term "Developer Story" would lead employers to assume it means the timline of your professional projects & honorable jobs they had over the years, as a developer. Technically, this isn't your story as a developer, it is your story on Stack Overflow.

  4. Statistics should show where most of your contributions are, in relation to tag-groups. Tag-groups are like the group of tags related to database, like transaction, sql, plsql, ..etc. Leaving customizing this to the user would solve its shortcomings.

TL;DR:

We're replacing CVs with something you can use even if you aren't currently looking for a job.

TL;DR; Customizability is important

  1. Replacing CV/Portfolio is a bad idea, this should be a separate feature; since they represent two different things.

  2. Developer Story should be customizable, utilizing things like favorites & options to control statistics.

  3. The term "Developer Story" would lead employers to assume it means the timline of your professional projects & honorable jobs they had over the years, as a developer. Technically, this isn't your story as a developer, it is your story on Stack Overflow.

  4. Statistics should show where most of your contributions are, in relation to tag-groups. Tag-groups are like the group of tags related to database, like transaction, sql, plsql, ..etc. Leaving customizing this to the user would solve its shortcomings.

Source Link
Khaled.K
  • 5.9k
  • 11
  • 6

TL;DR:

We're replacing CVs with something you can use even if you aren't currently looking for a job.

  1. Replacing CV/Portfolio is a bad idea, this should be a separate feature; since they represent two different things.

  2. Developer Story should be customizable, utilizing things like favorites & options to control statistics.

  3. The term "Developer Story" would lead employers to assume it means the timline of your professional projects & honorable jobs they had over the years, as a developer. Technically, this isn't your story as a developer, it is your story on Stack Overflow.

  4. Statistics should show where most of your contributions are, in relation to tag-groups. Tag-groups are like the group of tags related to database, like transaction, sql, plsql, ..etc. Leaving customizing this to the user would solve its shortcomings.