How does one go from Engineer to Product?

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
1/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
coffeescript, javascript, jquery, rails, react, ruby

Research direction

The issue names no repository files, tests, or entry points; start by reviewing the repository's issue and contribution context. It describes a career question rather than a code change, so the payload provides no implementation target or completion criterion.

Written by the indexing model from the issue text.

Description

post topic suggestion

I'm currently working at XXX where I focus on full-stack web development, using primarily Ruby on Rails on the backend and Javascript (especially jQuery, Coffeescript, and React) on the frontend. I joined the team in YYYY as the first full-time employee. It's been a great learning experience, but I'm now trying to figure out how to continue working as an engineer while also having more involvement in the product strategy/research/development process.

Dominant language
JavaScript
Stars
7
Forks
30
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dblock/code.dblock.org

All issues in dblock/code.dblock.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.