One of the first ones I can think of is pairing it up with Browser extensions to increase productivity of knowledge workers. Think of sales people quickly assessing the viability of leads, or simply reducing noise on social media as a B2C app.
117 karma · joined June 18, 2022
One of the first ones I can think of is pairing it up with Browser extensions to increase productivity of knowledge workers. Think of sales people quickly assessing the viability of leads, or simply reducing noise on social media as a B2C app.
1. Quality control. What documents to include?
2. Timing. When to query?
3. Pre & post processing. Improve LLM outputs based on retrieved data.
4. End to end training. Expensive, and data intensive but possibly the best long-term approach.
5. Controller. An interesting idea with similarities to Reinforcement Learning.
I wonder what are your thoughts. Which one is most promising? What has been your experience when building RAG apps? Also, is RAG the leading architecture for building applications?
And it does makes sense, in a way it would be similar to letting children (developing persons) make their own decisions.
The interesting question would be what is then, the best form of government for developing nations. Or even better, what are the required skill-set for leaders to bring development?
One has to deeply wonder about Political Theory after reading stories like this.
I can imagine this being true for 80% of high-mamager positions. But there's also a good portion of leadership positions that get created with new lines of business.
That is blue ocean thinking. Generally, it will give you more ownership about the outcome of your career.
Regarding science is about one standard deviation further than software development in complexity. It's not necessarily a trade off. On the contrary, software applies scientific breakthroughs.
Is about allocating the brightest humans to the most productive activities.
> The problem of excess genius is one of the most important questions I can imagine, but very little progress has been made. It surprises me that essentially no scholarly effort has been directed towards it. I warmly solicit any suggestions from readers that may help me to clarify my own confusion and uncertainty regarding this.
Excess tends to have a negative connotation, but not as used in the article. It also mentions that "the great minds in each of these societies tended to hang out together" which resonates as true based on reading biographies from accomplished philosophers. I'm curious to read your thoughts:
However, if your SaaS product already provides a developer salary, possibly your best chance is to look for sources of growth. Search how you can reposition it based on market conditions for a larger customer base, get professional advice, and even invest in sales, and marketing. Getting a job today might be the easy solution but a few years down the road you might regret it: getting the first customers is always the most difficult part. Finally, consider that if you've been developing for 10 years independently it could be challenging, or unrewarding to lose that freedom.
But I do wonder, what is the plan to achieve VC type returns. The market seems fairly small, and not particularly growing. I would think this is a great indie, profitable business but have a difficult time imagining how it scale to become a meaningful player in the start-up ecosystem.
Could you please offer me some insights?
Visits, clicks, read time.
> Novel writers?
Sales, reviews.
> Pop song composers?
Hits.
> "Management" needs to stop thinking that software is an assembly line and that they are managing "workers"
I can't avoid to find funny the thought of telling management, as an engineer, what they should do.
---
Good software engineers should embrace good productivity metrics (like the ones presented) as a meritocratic path to success.
I find there are 2 distinct set of metrics for engineers: ability to delivery, and to create value. Both important, both difficult to measure, both possible to approximate, and both benefit the business.
If the problem is serious enough, the capitalist solution would be to develop a platform that solves the problem for independent artists. However, as others have pointed out, the real customers for Spotify are not indie artists but rather paying users, and established artists.
While it is tempting to blame platforms for commercial failure. One has two recognize the truth of the business: making music follows a long-tailed distribution, and ultimately the listeners decide who rips those benefits.
There used to be fancier applications to ontologies, like question answering, but I agree with the author that LLM could replace most of them. The more interesting question is how to auto-generate ontologies?
I did found very interesting the anecdote around 1820 with the shift from the "old guard" on the British Royal Society. But it led to me to wonder why such an importance is given to specialized knowledge. It's like reducing every problem to be solved by a depth-first search algorithm.
i.e. storage is cheap, attention expensive