We landed on this planet,
Under this turquoise sky,
With flying tangerine leaves,
Slept on mantis beds.
All of a sudden,
A screeching sound thousand-fold,
Surrounded by dark crows,
Was awake to feel every pinch,
Was asleep to make any moves,
A dreary dark nightmare.
I see a witch in white drape,
trying hard to wake me up.
I see humming birds,
trying hard to break the crow cloud.
Another life on Rotten tomatoes had very bad reviews, but it is OK series, not a bad series. For Sci-fic fans watching old great series again and again due to dearth of great new ones – this is worth the time.
They took more liberal approach by including all kinds of love. Straight couples, gay couples, lesbian couples, bi triples and even AI couples!
The sci-fic plot is cliche some times. Mix of popular elements from previous classics (at one point I screamed inside – not aliens franchise please … 🙂 )
But, the actors are decent. The script and story is crisp. No unnecessary cliffhangers. More importantly it set stage for more series in future successfully!
Ideas though important, are cheap, execution is costly.
Software engineering made leaps and bounds with agile, scrum and other related innovations. But one thing didn’t get much attention is ideas. We are not tracking them similar to our other objects of a project management. They are discussed in corridors, scrum meetings, emails and chat-channels. But that’s it. It is either hit or miss. Not preserved for future. Like every cell in a human body regenerates in seven years, every team regenerates with new faces in two years. Ideas are lost to ether. Who knows one of those ideas disappeared in a blip may save the project in future?
Of course there are reasons for ideas not being tracked.
- They are cheap! For somebody with startup itch knows how easy it is to be flooded with ideas and how travail execution of those ideas is.
- Ideas are not rewarded during review cycle. May be for right reasons, ideas itself are not rewarded during review cycle. What is delivered is the only value considered for all those fat bonuses, stock options and promotions. This leads to engineers and managers alike ignore the importance of ideas.
- Once we start tracking ideas, it might become frenzy. If something is tracked, there will be un?-necessary attention to it.
To avoid “3” above – to stop team going frenzy we could call ideas as proposals. Now along with bugs, tasks, backlogs, features we better have a place for Proposals. In that way anybody in team could propose something and be discussed, tracked and logged for history.
There are two kinds of people – who are good at bird’s eye view and those good at ant’s eye view.
Bird folks are good at coming up with ideas, sub-ideas, thinking of all the problems, dependencies in reaching there; Ant folks are good at executing stuff but one grain at a time, how big the granary might be.
Now, keep both these folks in one room for whiteboard discussion and see the fun.
BTW, there are always ambidextrous folks, who can wear both the hats and context switch.
Here is a framework you can use to proceed from idea to release.
Form a big circle, write everything you can think of. organize them in whatever way you feel is suitable. This is basically your laundry list. It can include big picture design diagrams, north pole. If every dependency can be resolved, if we have infinite resources, what is that we are trying to achieve? How are we going to achieve it?
Now cut this big circle into three circles. Phase One, Phase Two, Phase Three. To be cute we can call them Milky-way, Andromeda, PinWheel. These are our short-term, medium term, long term goals.
Now each circle is to be cut into spiral with three parts. Zero, One & Two; Or Sun, AlphaCentaury & Proxima; Each one is its own release to customers. Sun could be start of life – gather data with initial POCs, perform things without dependencies, Work with dependent teams to unblock AlphaCentaury work.
Repeat this in three spirals in three small circles. We are still not actually executing project, only moving our laundry list into these galaxies followed by solar systems.
After each release revisit this and improve the same.
If anything the current quarter results and subsequent free fall of stock price tell, etFlix may no longer increase either subscription price or subscription base, it is time for other revenue sources. Otherwise its future is doomed. Moreover the content it is creating originally is super mediocre. Reason?: creativity is not something which can be produced by centralized managements. It is altogether a different ball game, all the money etFlix could dump may not be enough for a competitive rich content.
O! and before I forget to mention, couple of side-tracks.
- In spite of all the head start and overwhelmingly superior engineering team presence its user’s home page plus suggestions is flawed. Even after browsing for 10 minutes couldn’t find a decent flick to watch. They only show either already watched or not interested to watch videos. They should at least have an option to hide something. Which should hide from every recommendation except hidden pieces.
- Prime is eating away its eye-time. It might be time to have a partnership with Costco (similar to T-Mobile) ; but Costco doesn’t get monthly 100$ average like T-Mobile. Once advertising based subscription is available etFlix may go to Costco for a partnership. It might be win-win for both of them.
Back to advertising based etFlix brain storming.
There are Six players in this
You have existing subscribers and new subscribers who might come if it is advertisement supported model.
Once new advertisement based subscription comes – is it going to be completely free? Or 50% less than current price? For anybody else it might be easier but for etFlix with all its current user base this is difficult choice. If given free, current users might feel alienated, might even become vocal anti-advocates, a dangerous outcome. 💡 Instead etFlix should start with six months free for all the users who newly joined in advertising-based-subscription model, including those who got converted from any of current subscription models. This should keep current users happy and bring in new users in flocks as six months is a good trial period. After six months the subscription could be 50% less than current basic subscription. Of course this six months free can not be for-ever. It should be only for one or two quarters. Then it can be brought down to half-a-month free. Otherwise users will simply go on creating logins with different credit cards 😉
💡 In the initial days – we might be bombarded with new conversion requests. The service may not be ready for all those users trying to convert. Like Gmail initial invitation only method – we needed a way to tackle this problem. Robinhood’s add-to-queue is better approach. In this way we could completely control geography vs number of subscribers in new model. We could balance advertisement revenue vs loss in new subscription. So that the balance sheet at the end of quarter doesn’t look that bad in short term. This also means before we open up to users need to be ready with good advertisers.
Advertisers, Sales & Intermediaries
These are bunch of important folks. One of my MBA friends mentioned sales & marketing is a solved problem. Hopefully she is correct 🙂
In-house sales team can do everything in their capacity to get more advertisers. But this is equally technical problem too. In exact words this is digital enablement problem. Same problem Google adverbs solved. Anybody can be either advertiser or anybody can be a middle-man advocating other small to medium scale players. The big players can always be handled by in-house teams. Small and medium players may not get much attention. 💡 Here is where tech comes into picture. Anybody should be able to place an advertisement. All you need is a credit card.
Without these folks, we couldn’t build! This team needs to be top-notch, highly responsive, iterative, experienced, creative with motivated leadership team.
This is the most important piece of puzzle. If this can be done correctly we will have success otherwise it will be another failed project. Except Youtube nobody is adopting latest technical advantages to video advertisement.
Unlike Google, etFlix may not have much personalized data about a particular user. But it has good enough data about viewers to depend upon and customize advertisements.
- Favorite categories.
- Presence of kids – number of kids, their age group.
- Favorite color, favorite music etc…
- Income range?
- Education range?
- People with similar taste.
- Active time, free time,
- Data from other third parties (legal of course)
But the advertisements itself is a big challenge. We don’t want them to be highly intrusive. Do we support skip? What is the impact of CDN caching?
Do we support text only? image only? video only? (all three is what I recommend)
How does pay works? Any extra charge if user “saves” an advertisement to view later? 💡 Obviously we don’t want users to click on it and leave our video watching. We want users to continue watching video and enjoy the same. So we need a better idea to make advertisement win-win-win for etFlix-advertisers-subscibers. Instead of click and open in new tab we could have two buttons “Save” which will save it under a tab and also sends an email to user. “Contact Me” this will enable advertisers contact user with special coupons, offers etc..
The other fact is where to keep these advertisments?
- Banners (either text or image of GIF (sans-audio) )
- Full screen video advertisements with skip option.
- For high width screens – like those sports advertisements we could have vertical banners come and go on the right side.
- 💡 Dynamic placement advertisements. We all know there are several placement advertisements inside all those original videos. But they are static (for example actors will still be eating same pizza in same pizza-shop even after 10 years, that pizza shop may now be defunct!) we could make these dynamic! So Somebody watching in USA might see coffee boards, somebody in UK/India may see Tea bill boards! This will be completely dynamic! This is a great challenge for engineering team and content creators.
That’s all for now.
Read in half a night plus half a day.
Read two scenes so far. Good effort and presentation.
- If you are stuck on a single problem for more than three hours it is time to call help.
- You work for your manager not for company. Is it?
- Keep your ideas to yourself until you have more around them, like useful impact for team, reasonable confidence of execution, POC & estimates
- Best part of day must be spent on very important and more impacting work
- Never over promise – which inevitably leads to under delivery. Always under promise and over deliver.
- Tech debt vs timely delivery – always let the later win. Nobody loves a delayed but perfect release. (It may not even be that perfect)
- 20% of your time should be spent on something your manager is not aware at this instance. Provided you always work 20% more time than average.
- Consistent schedule is preferable for your health and your team’s health. Remember Rome is not built in a day.
- Know and understand dependencies of the feature before you write submit first draft of plan.
- Know your red-flags, and feel free to jump ship before they eat you alive.
- Every morning and evening write personal logs (as simple as OneNote )
- Nobody likes a smart-goblin.
- Always go prepared to a meeting.
Its been two tri-weeks,
we entered into this dark nebula.
Like dreary dark winters of old-earth,
this is extremely difficult on crew.
We wished for a glimpse of at least a single star –
the hell, we even prayed to almighty.
Forced to conserve energy –
means indoors are not lit bright.
adding bonus frustration and depression.
The doctor is busy,
patients are plenty.
Bridge is deserted, other than few ensigns.
Then there is little glimpse.
Is it for real?
Or only in our imaginations?
Only time will tell …
We continued our journey across dark nebula.
Before Sending CR
- Keep trivial changes like renaming, reformatting, moving code around in its own Pull Request (PR) ; Keep refactoring code in its own PR; Keep rest of the code in separate PR. Combining these three will dilute PR, people either won’t review by looking at sheer number of changes or will leave too many comments ending up in a myriad of ping pongs resulting in overall compromising tiresome experience.
- Keep smaller PRs, Keep them to one issue (or minimal logical conclusion of feature) ;
- Try to develop one or two buddies. This greatly improves turn around time of your PRs. Of course you need to reciprocate the same.