You have probably been to many industry conferences and heard about the product discovery process more than once, it seems to me that the topic has become one of the most important issues in the product management domain.
Thesis of this article is that in my opinion, there is not one golden benchmark of this process (as Facebook or Netflix has) and each of them has its own trade offs list that we can thoughtfully structure our processes based on sources.
First, let’s talk about a simple typology of possible product features.
In the global village, fewer projects will be able to cope as standalone products and they will have to look for their competitive advantages in integration with popular tools or being active in terms of building synergy strategies thanks to their integration offer
Developer Experience is the equivalent of User Experience when the primary user of the product is a developer. DX cares about the developer experience of using a product, its libs, SDKs, documentation, frameworks, open-source solutions, general tools, APIs, etc.
Building new product features is a difficult and complex process because, on one hand, we want to be certain of what our users want, and on the other, we have plenty of evidence to suggest that people are very bad at explicitly saying what they need.
The other important side of the equation is the balance between certainty and the agile culture of building and testing new business models, product lines or individual features. (A very interesting short series about Spotify Engineering touches on this problem)
Key is to find a compromise between certainty and the risk of feature development.
As Lewis Carroll famously said, “If you don’t know where you’re going, any road will get you there.”
This quote resonates in my mind while I am writing this article about selecting strategies and tactics for developing an API based product.
This article (hopefully the first one from a series) is supposed to ask you, product manager, some basic questions related to creating and defining a product.
When you create an API based service it should be cascaded from the organization’s strategy and it should add significant communication interface to it.
The first question you should ask yourself is WHY…
Kiedy zaczyna się ta historia ten młody chłopiec będzie zwyczajnym, niczym nie wyróżniającym się szkockim dzieciakiem …gdy się kończy ten mężczyzna będzie jednym z najbardziej utytułowanych trenerów na świecie
Chcę opowiedzieć wam trzy historie
Pierwsza historia rozpoczyna się nad rzeką Clyde w szkockim Glasgow
Był mglisty, zimny poranek w szkockim Glasgow niespełna czterdziestoletni Alexander jak niemal co dzień punktualnie o 6 rano przemierza tą samą drogę do stoczni w tym czasie młody Alex obserwuje ojca pracującego 60 godzin w tygodniu, 45 lat później ten sam niegdyś młody Alex otwiera i zamyka ośrodek treningowy w Carrington pod Manchesterem.
some of you notice problems with deployment to heroku severs because of problems with bundler older version
so that’s quick tip how to solve that’s problem
bundle install — without development:test — path vendor/bundle — binstubs vendor/bundle/bin -j4 — deployment
2. Add to git your gemfile.lock file
git add gemfile.lock
3. Commit all changes
git add .
git commit -m “bundler mod”
4. Push changes to heroku
git push heroku master
that’s it guys, I hope that’s can be helpful for some of you
MAKE or break