Older article from 2016
Older article from 2016
is a phrase that has been thrown around at times and applies to many existing examples like RedHat, Cloudera and others.
If you’re thinking about starting a company, don’t let the tail wag the dog. Start with the question “how can I deliver value for customers” and work backward from that. Then piece together the open source components you’ll need for your ultimate solutions that deliver value and construct your software supply chain. At this point, you may decide, like Red Hat, that you want the benefits of collaborative development, or you may decide, like Cloudera, that you want at least some of that to be entirely under your control. The point is you can make that choice without the baggage of “let’s monetize ‘X’”. You’ll be much happier with your choice.
Open Source Business Model, is discussed in a few places by a few authors and their position is that there is not one of “these” and I would suggest that their perspective is skewed by their pre-existing conditioning from their own experiences. I think there are many entrepreneurs that are working in and with Open Source in various ways.
Lots of interesting ideas none the less.
Follow our affiliate link below:
Will Larson’s Bio:
April 1, 2007.
A long time ago, I also cofounded a really misguided iOS gaming startup with Luke Hatcher. We made thousands of dollars over six months, and spent the next six years trying to figure out how to stop paying taxes. It was a bit of a missed opportunity.
The very first iteration of Irrational Exuberance was created the summer after I graduated from college, and I’ve been publishing to it off and on since. Early on there was a heavy focus on Django, Python and Japan; lately it’s more about infrastructure, architecture and engineering management.
It’s hard to predict what it’ll look like in the future.
In his article, Will Larson (https://lethain.com/about/) discusses the complicated processes of “Infrastructure Planning” and communicates in a very clear and effective way, a lot of what is necessary for something very complex and simplifies it down to less details and less technical language for the lay person. I think his brilliance is in this. I hope I find a lot more of this as I surf the Internet.
Here’s a couple of opening paragraphs to give you a taste.
Technical infrastructure is never complete. System processes can always run with less overhead or be bin-packed onto fewer machines. Data can be retrieved more quickly and stored at a cheaper cost per terabyte. System design can broaden the gap between failure and user impact. Transport layers can be more secure.
The sheer variety of investable projects is overwhelming. There are always new technologies to adopt or finish adopting: Docker, Kubernetes, Envoy, GKE, HTTP/2, GraphQL, gRPC, Spark, Flink, Rust, Go, Elixir are just the beginning of your options. Add cloud vendor competition, and the rate of change is pretty staggering.
With such a broad problem domain filled with so many possible solutions, I’ve sometimes found it difficult to provide guidance for infrastructure teams to prioritize their work. Originally, I thought this was because I lacked depth in some facets, but I slowly came to realize it was equally difficult for the teams themselves to prioritize their own work: there were simply too many options.
I think you will find his article a very solid source of information.
Follow our affiliate link below:
via PolyglotPersistence (excerpt follows)
In 2006, my colleague Neal Ford coined the term Polyglot Programming, to express the idea that applications should be written in a mix of languages to take advantage of the fact that different languages are suitable for tackling different problems. Complex applications combine different types of problems, so picking the right language for the job may be more productive than trying to fit all aspects into a single language.
My programming career began in 1980, as a hobby growing up and an older brother mentoring me during his summer and holiday, etc. visits. Those are fond memories and I miss talking and being around him. Just like I miss our Dad.
Aside from having a lengthy personal history of being at the keyboard or wielding a soldering iron and other various tools through elementary, into high school and through college to this day.
Being a polyglot with computer languages is rooted in my background designing and building actual hardware from the ground up. Yes, I am One of Those Guys. I Love to Tinker with Things. Love Life and The Adventures of Living.
It’s been recognized that software is eating the world,” said Michael Skok, general partner at North Bridge Venture Partners. “Our survey points to the fact that open source is eating the software world
Open Source does not suffer from intrinsic entropy of development that plagues Closed Source Systems.
Open Source has better chance of long term survival due to the concept of “forking” the code base.
Open Source is also “more democratic” than Closed Source Systems historically.
Many consultants and organizations love to cite market share.
Using an “Open Source Cooperative Business Model” is the foundation for future businesses.
Features that are unique to the system and involve Human Intervention to program the Features are applied in stages or levels at each of the levels beyond 1: these other levels generate revenue and the community of cooperative member-owners vote on Features & Benefits that they would like to have in the System.
The Freemium Level will obviously come with the Seed Server which you purchase and receive the first 2 levels of Software.
Base Cost of Hardware (Seed Server) + $29.95 per month after the first year with option for annual renewal, $299.99 when included with the Server.
$2002.69 (Spec in development)
Setting up your own Mastadon instance puts your DATA back in your hands where it belongs.
Should all be required to have Universal Design as a part of their curriculum of their respective College or University and let us be frank. Those same public institutions are not as “accessible” as we might think they are.
We have standards for a reason. There are most industries that regularly handle the Critical Path to achieve a solution that is a best for a scenario.
We’ll see how things unfold with SidewalkToronto and they are still in the very early stages. Hopefully their efforts will be adopted globally, not just Nationally or within the City.