dblock / dblock/code.dblock.org
How does one go from Engineer to Product?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- coffeescript, javascript, jquery, rails, react, ruby
- Domain
- documentation, full-stack, web-dev
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 1/100