Obviously no right answer, but personally I think worrying too much finding the perfect tool instead of just integrating more knowledge to your PKMS is a distraction.
Rolling your own solution is especially limiting in the context of the sheer amount of integrations the popular ones (like Notion for example) support.
You're basically saying you will quickly build something better than the X hundred engineers at PKMS company Y quickly and it will continue to be better than what X hundred engineers will iterate upon.
I think that time is just better spent learning and picking the subset of features that, for example, Notion offers that really improves your learning rate.
If you reframe it slightly, it can make sense. Those x hundred engineers are working on y hundred features / integrations. Do you need all of those? Do you want all of those? I bet a handful of those engineers are currently working on a brand new UI redesign that will move all the buttons you're used to. One of the engineers is adding a new cookie popup & enforcing SMS 2FA as we speak.
One of the things I dislike about moden software is the constant bloat and churn, because there are so many customers and so many different incentives for software companies to keep pushing features ad infinitum. In contrast, home-grown software like this has one customer and they know exactly what they want. It doesn't matter that a theoretical home-grown app doesn't integrate with the 10 social networks the user doesn't use, because it integrates perfectly with the one they do use.
This person isn't rebuilding the entirety of Obsidian, they're rebuilding the subset of parts they actually use and get value from, which is a much smaller project. By intelligently narrowing your scope like this, making stuff yourself is totally viable. Reframe "limiting" as "targeted".
I agree Notion is great. I prefer it if I need a shared PKMS such as a company wide document system.
That said I've played around with its API a few years ago and with page elements being block elements you need to loop through n amount of requests to get the content, it didn't make sense for my use case.
Considering expert vs. novice problem-solving: Within their domain, experts leverage highly efficient models. Outside? Rigidity often impedes adaptation.
Their ingrained patterns, assets in familiar territory, become cognitive liabilities in the unfamiliar. The novice's counter-intuitive strength lies in a lack of assumptions, fostering the openness to explore without ego.
(author here) I agree that novices have an advantage in that they have few assumptions:
> Something you can do independently (and possibly it’s best done without expert supervision), is exploration of the field. You know nothing, and have no biases about what may or may not be useful. Any time you come across something that feels like it has some depth to it, such as a well-written essay series or a deep technical dive, you need to invest heavily into it. As a novice, your one advantage is that everything is new and nobody expects you to be fast. Because of this, you can afford to spend the time to learn as much as possible.
I'm not sure that it's correct to characterise an expert by the lack of this though. I think it's correlated, but not all experts are so rigid.
But sometimes, there's just not enough variance between the domains. Any NIH attitude is more likely to veer into complicated systems than finding the next best abstractions.
The cynic in me knows the real reason for them to be a carbon neutral company is so that you don't feel bad purchasing another one of their phones since it was produced "neutrally".
I agree with asking hard questions, but I think there's a limit to how much one can really expect an individual job applicant to determine the financial state of the company.
For one, the people that are answering their questions are by pre-condition already drinking the company kool-aid.
I see this argument come up all the time. However, the job market in general and especially in America is terribly inefficient. The vast majority of Americans work paycheck-to-paycheck and are tied down to their geographic location (family, children, housing). There isn't really a social safety net (by design, I think) in America for employees who voluntarily quit their jobs. So lots of people are stuck in jobs they hate, getting paid less than they deserve, and are a poor match for their skills. There are still lots of jobs that don't have the luxury of entirely virtual interview processes. Over time, I do hope the job market gets more and more liquid for candidates.
I'm still waiting for proof it was anything more then people changing jobs or taking time off when they got stimulus checks. I really doubt anything is coming of it at this rate let alone "societal" changes.
Well COVID killed a bunch of people and disabled a bunch more, so those people dropped out of the workforce. There's also the fact that Baby Boomers are retiring. That means that economy right now wants more workers than are available which puts pricing power in the hands of employees.
And the idea that you should job hop to get higher wages and that employee loyalty to employers is for suckers has trickled all the way down and people are talking about it and there's a noticeable uptick in unionization drives.
The idea that everyone just up and quit is probably not correct at all, but I don't think its accurate to say that the environment isn't looking any different from the past ~30ish years.
I think the Fed is about to stomp the shit out of all of it though.
Tinder would seem to contradict you there. How often is an eloquence requirement given vs. height requirement? Sure, height is not something we should fixate on, but it doesn't mean that doesn't happen anyways.
Rolling your own solution is especially limiting in the context of the sheer amount of integrations the popular ones (like Notion for example) support.
You're basically saying you will quickly build something better than the X hundred engineers at PKMS company Y quickly and it will continue to be better than what X hundred engineers will iterate upon.
I think that time is just better spent learning and picking the subset of features that, for example, Notion offers that really improves your learning rate.