It really depends on the job you're trying to accomplish.
I'd venture saying that it's way too early for horizontal / massive scale RAG apps.
Most solutions will want to focus on a very specific vertical application where the dataset is much more constrained. That we're this makes more sense.
Interesting article about long term planing. It does bring forward some interesting thoughts about how one should execute on a plan, but mostly I find it interesting in how this article misses the point of a plan.
I’d like to propose a slightly contrarian, if not, more nuanced view of what is the purpose of a plan.
If one considers a plan as a map that must be followed in minute details, to travel the proverbial territory then, of course, you’re much better with small, unplanned iteration that allow you to learn from each story you deliver.
The image that the author proposes is a very powerful one: yes it is much better to play the lottery by buying one digit at a time, because overall, you’ll cut your losses short in most cases.
However, this only focuses the value of the plan in it’s execution phase, absent from the planner, and the feedback he will get from the divergences from the plan, and the updates he will be able to bring to the mental model / explanation linked to the plan.
Let me be clear: *plans are meant to fail*. Why? The value of the plan is in *HOW* the execution diverges from it, and in so help us to update how we think and reason about the world.
Each plan, has as origin an explanation, theory, of how the world/market/customer works. Changing your explanation of how the world works is the goal of learning. To learn, you must make predictions. That is what the plan is, a simple prediction. Of course we should not expect those to line up with reality 100% of the time. It is quite the opposite: *expect your plan to fail* but most importantly *improve your understanding of the world / your market / your customer based on what you did not predict.*
I'm currently reading Competing Against Luck and it is a truly eye-opening book that highlights and puts the finger on a lot of the luck-based innovation work we've been doing over the years.
I was planning on taking MR Christensen's online class[1] this coming April, but I wonder if this will still be happening given Mr Christensen's passed away.
Would anyone have any good resource, online classes, books, videos, etc that they would recommend to learn more about Jobs to be Done and Disruptive Innovation Strategy?
It seems to me that the article doesn't debunk at all the existence of a tipping point in social networks phenomenons.
In fact, it clearly states that it is the law of the fews, "that rare, highly connected people shape the world", that seem to be inexistent in Watts experiments.
If trends are really like forest fires, then there is a tipping point ; it is just not required to have these highly connected people on board to reach it.
This definitely reads like one at least. I can't help but be amazed at the way he uses to publish / distribute it all at the same time using this print spool.
IMHO I would expect a big proportion of the sites to break when you browse w/o JS nowadays ; nothing wrong with it, it's just the state of the web now...
I think it would be good to have that on both the client and the server.
Also, as simple as this might be, making it a de-facto standard (on meteor) would be a good thing since it would be a tool that we can count on, all the time. There are too many browsers IMO to make an extension a viable option.
Whitelisting variables would be good as well ; that way we do not get alerted if it is something we expect to be global.
> We've added file-level JavaScript variable scoping. Variables declared
with `var` at the outermost level of a JavaScript source file are now
private to that file. Remove the `var` to share a value between files.
I think it is convenient to be able to declare global variables like that but perhaps there should be a way to monitor those ; in other words, it would be really convenient to have some form of alert system to notify you when a new global variable is created.
That way, globals created by mistakenly forgetting the 'var' keyword would be easily spotted.
What is the project direction in relation to complex JS apps?
i.e.: How do you guys expect the instarepl idea to be used in apps made of serveral node.js modules/libs or several files meant to be loaded together via RequireJS ?
Most solutions will want to focus on a very specific vertical application where the dataset is much more constrained. That we're this makes more sense.
Also a lot of alpha in data augmentation.