Sign up to save your podcasts
Or
Share Not invented here
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Not invented here
By Sonar.1Technology
Not invented here episodes
- #27 One level deeper
This episode on YouTube
Discussion and more in Dima’s blog.
In this episode Dima discusses how going deeper down the technology stack can give a company an important advantage over its competitors.
16 min - #26 Unlimited online backup
This episode on YouTube
Discussion and moreA particular example of limitations of an unlimited service: Backblaze is a great service, but the way it markets itself as “unlimited online backup” is a fair bit of exaggeration.
0 min - #25 Infinite amount of something
This episode on YouTube
Discussion and more on dmalenko.org
We all love getting infinite amount of something for a small fee. That makes all the “unlimited” plans so popular. On practice, however, those plans fairly quickly turn out not to be unlimited, infinite or lifetime and there are reasons why.
17 min - #24 Misaligned incentives
This episode on YouTube
When the way company makes money is misaligned with its values, it can sooner or later lead to decisions that may turn into a disaster of some sort. Similar to what happened to Mozilla with the Looking Glass add-on for Firefox.
* Firefox is on a slippery slope
* Update: Looking Glass Add-on
* Mozilla and Pocket13 min - #23 A-a-aa not so good song
This episode on YouTube
Masking a problem without really solving it can move the problem to a more dangerous place or time. Do you remember the story about “A a a a a Very Good Song”?
* You are finally free from the first embarrassing song on your phone
* A silent, 10-minute song is climbing the iTunes chartsDespite its popularity back in the day the song did not really solve the problem of Apple CarPlay annoyingly starting to play the very first song in the music collection, when the phone was connected to the car. It postponed that annoyance problem until 10 minutes later, when one could be driving through a busy intersection.
8 min - #22 Illusion of control#22 Illusion of controlSonar.1Download
📺 This episode on YouTube
All modern systems are built out of components. Those components can come in different forms: 3rd-party proprietary, open source and developed in-house. Open source seems to be the most popular option nowadays and one may think that using open-source components is an all-around win. It is a win, but not all-around.
3rd-party proprietary- minimal initial effort to start getting benefits from the component: some learning curve, but no heavy lifting with development
- all encompassing solution with features you do not need but still have to deal with
- fairly good understanding of costs related to getting maintenance for the component over time
- minimal control over direction of development
- possible dead ends because of lack of transparency
DIY components- tightly focused solution that delivers exactly what you need
- significant upfront costs and long and, maybe, costly further maintenance
- with all that comes full control over the direction of development
- draws resources and attention from the core competency
Open source- ready-made solution that requires minimal to start using
- free basic maintenance by the comunity
- solution with wide focus and sometimes “half way there” functionality
- illusion of control induced by the fact that source can be forked and taken in-house
Check out Dima’s blog
21 min - #21 Business of selling#21 Business of sellingSonar.1Download
📺 This episode on YouTube
Common bits of criticism of new products often come from the lack of the information and the lack of desire to put them into perspective.
- “New product has feature X. I don’t need this feature. Therefore the product is bad.”
- Usually there is good reason for things they do
- Apple announces Animoji, animated emoji for iPhone X
- Let’s face reality: US Teens engage with iMessage more than any other social platform
- “Apple did not innovate enough.”
- Apple is not in the business of innovation, it is in the business of selling products
- With 60% market share selling upgrades to existing customers makes more sense than trying to convert
- High-end smartphone market share as of 2016
14 min - “New product has feature X. I don’t need this feature. Therefore the product is bad.”
- #20 Code does not equal project#20 Code does not equal projectSonar.1Download
📺 This episode on YouTube
Software projects are so much more than just writing code. It is impossible to replicate entire project with any number of lines of code.
- There is a bold claim about How I replicated an $86 million project in 57 lines of code, but the author confesses
To be fair, I have absolutely no clue what the $86M figure includes…
- Analysis of the limitations of the technical side of the proposed solution, which likely preclude its use for building real-time system: How I failed to replicate an $86 million project in 1 line of code
- A case for order of magnitude difference in effort depending on detailed requirements: printing a file to the console
- Naïve implementation is 2 lines of code in Python
- Gracefully handling printing a huge 4Gb file from USB stick, which is ejected, requires a lot more work
- Don’t think someone is stupid. Instead try to understand why they do what they do.
15 min - #19 Full saturation#19 Full saturationSonar.1Download
📺 This episode on YouTube
Application’s lifecycle in a marketplace explains why at times developers add features nobody really needs and why many of them try to turn their applications into services.
- Security Experts Wary as 1Password Subscriptions Push Users to Cloud-Based Vaults
- What’s new in Transmit 5?
- Adobe Hits Record Revenue of Nearly $2 Billion in a Quarter
Lifecycle model:
- Rapid growth on growing market
- Revenue comes from new users
- Few new users, but strong demand for new features
- Revenue comes from upgrades by existing users
- Full saturation: no new users, no demand for new features
- New sources of revenue are needed
19 min - #18 True to itself#18 True to itselfSonar.1Download
📺 This episode on YouTube
Platform UI guidelines are aimed at making application more approachable for the users. When it makes sense to depart from platform conventions when developing cross platform application or service?
- App Stories Episode 12: The State of Non-Native Apps
- All apps using Windows 95 standard controls looked the same. History repeats itself with Android (How are all the Material Design apps so similar? - Quora)
- Games newer follow UI conventions of the platform
- Experience with an application on different platform vs. experience with the platform itself
- Take a look at examples in How to design a mobile app across OS platforms?
More on this topic:
- Which is the better approach for Mobile UI design, platform-centric or application-centric?
22 min
About Not invented here
From the publisher's feed
Podcast about tech, software, product development and business. Dima Malenko tries to explain driving forced behind news, events and other developments in the hi-tech world and shares stories and…
ideas inspired by them.