bibryam

No backend, not remote API! You can use Chrome Nano (the default), or Ollama locally.

Remote API, only if you decide to bring your OPENAI or ANTHROPIC keys.

There is more content than ever, but it is almost always SEO-optimized & AI-assisted. Usually one interesting idea and few arguments, get expanded into pages of noise, always in a different shape.

I like skimming most blog content in the same consistent structure: - key idea - claims - arguments - counterpoints - action items...

Then, if it looks worthwhile, I then read the full post.

The same structure doesn't work for every content type. Research, product, engineering, marketing... each require a different reading shape.

I have been doing this manually for hundreds of posts, with ChatGPT copy & paste, customGPTS, etc. Eventually turned it into Chrome plugin and since it has become part of my daily reading workflow.

Skimlane lets you create different reading recipes and use Chrome's on-device model (or BYOK) as a local reading harness.

I built it for myself, love using it, and decided to share it. https://skimlane.com/

A few AI companies giving free stuff to OSS maintainers - Dosu - CodeRabbit - OpenAI - Anthropic

https://www.oss.fund/explore/?pillar=operational-support&cat...

I'be been tracking oss funding efforts here https://oss.fund/

For every Tailwind, there will be 1000x other projects affected by AI's use of OSS that will not get sponsored.

https://github.com/tailwindlabs/tailwindcss.com/pull/2388

There is also https://agntcy.org/

A Distributed Non-Deterministic Collaboration Protocol.

command mode is for local, and SSE for remote

AI already does that. Send a question to chatgpt that requires analytics, chatgpt will write a python code, execute it, and return you the result.

https://x.com/bibryam/status/1892332097999626634/photo/1

I did. My path was: software engineer, consultant, architect, TPM - driven by desire to have impact and move one the moment I noticed stagnation of personal growth.

Definitely having technical background helps with managing products that are highly technical or for technical users.

W/o going into the whole rabbit hole of PMing, here are a few links I found useful on my journey

Must read book https://twitter.com/bibryam/status/1629768021391572995 Most popular PM podcast https://www.lennyspodcast.com/ https://www.sachinrekhi.com/top-resources-for-product-manage... I was lucky to attend many courses here pragmaticinstitute.com

That alone is a lot to read. Good Luck!

I described a checklist for open source vs fake open source evaluation

https://blog.oss.fund/p/a-framework-for-open-source-evaluati...

I have one for a long time now: microservices.fail

DeFi explained

https://research.stlouisfed.org/publications/review/2021/02/...

In case you are really interested what it means, but not only picking on the nirvana word, here it is: The Bazaar, and open source in general cover the development model through open collaboration. That is awesome, but not enough. You need to think about open funding and open governance elements.

- Ex. DeFi (that is a word now people seems to be familiarizing with) is an extension of open source where monetization is also backed in the project. It is open source + monetization in a decentralized form.

- There are also MANY blockchain projects that incorporate governance by voting of token holders, etc. That is better than a bunch of folks with commit (or some other lifetime) rights taking all the project decisions, at least it is more transparent. That is open source + decentralized governance.

So the conclusion is: Open/free source (cool but not enough) + decentralized governance + open monetization = nirvana. To get there, that will take the next 20 years.

HTH

(Disclaimer I wrote the article) My first ever computer was a Pentium 4 and I've started my software career around the middle of the open source era (not the free software era). I have missed the beginning and the history of open source, but I'm very interested in what is coming next. There is so much written about the history and various definitions on Wikipedia, that wasn't the focus of the article (hint: the future was). I've included just enough selective facts about the history, to make a point. The focus has been to predict what comes in the next 20 years.

Today, when I chat with kids that are starting their careers, they are hardly excited about what happened 20 years ago, not to mention 40 years ago. They don't give a sh*t about the ideological differences between free & open source, and what the early internet connection speed was. But they are defining the next 20 years through some Javascript and Web3 technologies.

DeFi and other blockchain projects follow the same model. It is not only about writing the code, but also running it. In which case you can embed the monetization in the software. Hats off.

Here are all of the ones I know about https://www.oss.fund/

stars, forks are the metrics that first hit you when you browse a project, so it is part of what THE platform hosting most OSS projects tries to convince us matter. There are other ways to check real people involvement in the project (such as issues, PR) but even these can be single company employees. I'd say we are missing open financial metrics that are missing.?

One does not replace the others though. There are still independent hackers doing a great deal of open source (Let's put them in the free software category). That is especially true for the node community. There are many projects build by full time employees dominated by 1-2 companies (a good example here are the ASF projects). There are gigantic projects that are possible to be developed in high pace only through collaboration even between competitors (Kubernetes in CNCF)

There won't be only one way of doing OSS. But I believe there will be again a rise of independent software hackers and this time they will be better equipped with tools for automation, distribution, funding, marketing, etc.

Agreed 100%. The recent attempts are getting better and better: Github sponsors, Tidelift and their decentralized versions will be the foundation to enable modern day independent hackers. Open source needs open funding/governance infrastructure that is automated.

This is a well known practice and recent trend actually (Redis, Mongo, Confluent, ES...the list goes on). You choose a license that is restricting the usage of the software for certain class of users, whether that is cloud providers, SaaS services, your direct competitor, based on review or what not. By OSI definition this is not any longer open source software, but source available. There is a simpler way too: just pick a business unfriendly license and sell exceptions that is the dual licensing too. Check licensezero for how to automate this.

There tens of different platforms for OSS monetization options https://www.oss.fund/

hi all, the author of the article here :)

The book that is linked has been translated into 4 languages and does a good job explaining what is a sidecar. No need to buy, you can download it for free from here https://developers.redhat.com/books/kubernetes-patterns

The article is for Kubernetes savvy readers, and the main takeaways (which I agree I failed to convey clearly) are these:

- You can consume generic capabilities from a sidecar through HTTP/gRPC, rather than include these capabilities into a microservice's runtime as a library.

- There are many sidecar examples today (some in a Pod, some shared) Envor, Cloudstate, Skupper, etc. Sidecar is an implementation detail. It can be with containers in a Pod, or it can be a shared sidecar per namespace or host machine - next to a monolith. The best example today, that provides generic developer primitives as a sidecar is Dapr.

- Kubernetes Operators encapsulate operational knowledge into executable form and shipped to software consumers as an "Ops-included" mentality.

I explained in more details the concept of consuming distributed system capabilities from sidecars in this article http://www.ofbizian.com/2020/05/multi-runtime-microservices-... and webinar https://www.youtube.com/watch?v=CZPEIJFJV9k

I wrote a paper with 7 rules for container-based applications to make them cloud native (i.e. Kubernetes) friendly. Free to download.

2018: #Blockchain 2017: #CloudNative 2016: #Kubernetes 2015: #Microservices 2014: #ApacheCamel