48 karma · joined April 20, 2018
Imagine you are creating an asset which requires multiple API calls and your UI is designed to go through a 10-12 step setup process for that asset. In practice even if we give one tool for LLM to one-shot it, or even if we break it down into 10-12 tools the points of hallucinations are much higher.
Contrast this with "skills" and CLI.
So, I dont see why a typical productivity app build CLI than MCP. Am I missing anything?
You learn from TikTok, for me thats the place to see hot girls(arbitrary).
But,
|empirically social media seems to be the web. '
is true.
Learn has such positive connotation and I want to highlight how a sentence with a not so positive connotation looks like.
An Apartment - A house that is my own, not my parent's place, but mine.
A good chair to work from home - Steelcase Series
That being said, product mindedness is hard for engineering teams. 2 of the teams I work with, I am giving them inputs on every single feature they need to build. While I dislike doing this for every feature, its upto how the engineering leader envisions their team to function. For some, unless there are jira tickets, properly prioritized, with designs ready, they dont want to involve engineering teammates.
Is it any different from Ant Design (https://ant.design/)?
Also, almost every company I worked with (> 500 employees), eventually built their own UI components. And in every company, developers seldom use these, always customize or use something else.
Which brings the question - Why do we invest (internally) and open source components? Whats the value?
If the purpose of this exercise is to improve your overall understanding, I would recommend something more fundamental than above (software-specific business books). Read some Macro Economics, articles around industries you are interested in (SaaS, Mobile, etc.) - especially historic ones which give you more foundational understanding.
Also, I strongly recommend not doing an MBA program if knowledge is what you seek.
1) Creativity Inc
2) Competing Against Luck: The Story of Innovation and Customer Choice
3) Start With Why
4) Inspired: How to Create Products Customers Love
5) The Hard Thing about Hard Thing: Building a Business When There are No Easy Answers
I only managed to finish ~50% of my planned reading in 2019
We do have a constants file which has all the messages but a PM does not access to code/commit and has to go via a Dev.