> Just as there are odors that dogs can smell and we cannot, as well as sounds that dogs can hear and we cannot, so too there are wavelengths of light we cannot see and flavors we cannot taste.
This is comparing ourselves with dogs lol. We are much more than that. We can build scientific instruments to smell what dogs smell or hear what they hear etc. See: https://publicism.info/science/infinity/7.html
Ok thanks, that is the assumption part. Very important indeed.
I will try my luck on the "definition part" myself: According to Wiktionary, To Scale =
1. To climb to the top of : This upper movement looks like scaling toward "Wisdom/enlightenment" to me. (not very "Poppers")
2. To tolerate significant increases in throughput or other potentially limiting factors : The one is more like "Management" (as in KM)
3.To weigh, measure or grade according to a scale or system : here it is the "Value" aspect. what is valuable knowledge?
4. To change the size of something whilst maintaining proportion: The size is the easiest angle. I don't know how "maintaining proportion" would translate here.
At the personal level, that is one the biggest problem of "scaling knowledge" right there ! We just can't help "growing" it in article after article, because those ideas just keep coming to us. We need sometimes to step back and communicate the "meta". Not just the assumptions but also the definitions.
I think 4 comes closes. "Maintaining proportion" here could refer to the breadth and depth of the knowledge. These forces are somewhat antagonal so that we need to maintain a certain ratio to reach complete understanding. David Deutsch explains this to some extent in the first ~20 pages of the fabric of reality.
> We need sometimes to step back and communicate the "meta". Not just the assumptions but also the definitions.
Yes, good point. Do you think assumptions and definitions are something different? If yes, how are they different? The problem I solved with choosing a name for the blog was that I wanted to communicate a category of what will appear on this blog, which I think the less defined/fuzzy term solved well.
I guess, I was assuming none of these. But the word scale as in scaling a business/company[0].
> Do you think assumptions and definitions are something different?
Nah, I'm sure we can go real deep into how they relate to each other. Here I was just stressing their importance together, not their distinctiveness.
> I think 4 comes closes > I guess, I was assuming none of these
Well, you are underestimating the genius of that choice. Now that I thought about it, IMO, the 4 meanings could be seen as equally important but complementary perspectives into engaging with knowledge (I’m sick of the KM acronym). You are warned, I'm gonna steal it!
> the less defined/fuzzy term solved well.
Yeah, that is what I thought. Over (pre)defining things could lead to predefined (=limited) thinking. No always good for exploring wide topics.
> Maintaining proportion
Ok, so it is the proportion of
1- Breadth/depth for Knowledge
2- Gain/Losses for Business
3- flexibility/simplicity for data structure.?
I just added the third one, like, how you could scale Remnote, not just as a business but also as a data-structure? what if, in the case of data-structures, scaling is seen as maintaining proportion between flexibility and simplicity?
I will just say this : I have a general theory on how Outliner+DB combos have an excellent flexibility/simplicity ratio [1] (= top-notch at scaling) , So I hope the new table feature will be implemented deeply into remnote (and not as an afterthought)
Not the person you're asking, but I was actually somewhat underwhelmed by that book. Maybe I had unrealistic expectations, but I felt like it combined very general, obvious ideas ("keep teams together") with oddly specific numeric recommendations ("a manager doing technical work in addition to management can support at most five people") that didn't come with any good evidence beyond author opinion.
There were some things that I did find reason to take notes on, such as:
- Each area of responsibility should have a team dedicated to it, even if some teams end up having zero people in them, and sometimes members from other teams have to rotate into that function. I liked this because I know how easy it is to forget that some functions are understaffed if you squeeze them in with other functions.
- If you want to improve how the larger organisation works, run the improvement as an experiment in your team and then publish a very brief report on the results along with instructions for how other teams can try it. I liked this because I've often done the first part, but I've often forgotten the publishing part.
- A leader is asked to decide a million things a day. Your job is not the make those decisions, your job is to figure out a system in which the decision is not needed, or the right decision is clear for anyone to see, and then help others participate in that system. I knew this from before, but it bears repeating because it's so easy to forget in the heat of decision-making.
(The last point has a more general corollary: your job is never to do what you were hired for, it's to teach others how to do what you were hired for.)
I found "An Elegant Puzzle" brilliant because the advice was so specific and concrete on a wide range of topics. But I'd guess the target audience is a leader in a mid-size startup (100-500 employees), so its advice isn't going to be so much help outside that group.
A beautiful piece of IOS app engineering! How did you make the UIPageViewController in SwiftUI at the beginning of the app? I also tried to use it but have not yet found a way to bridge the UIKit with SwiftUI.
we tried really hard to bridge the UIKit one, but had some bugs & crashes due to the PageController (the dots underneath). I think it is caused by the fact that a same SwiftUI @State is used by 2 UIKit "bridged" controllers, and is not operated in a thread safe way.
So we ended up building it from scratch ourselves, in SwiftUI :)
I'm curious, have you (or your customers) deployed this in a RAG use case already, and what have been the results like?