2,947 karma · joined March 3, 2019
Also why would they not just use the official GitHub MCP?
The deployment part isn't a pain point, the maintenance and optimization is.
Still has a ways to go, but shows promise.
In Cursor for example, it gives the agent the ability to connect to the browser to gather console logs, network logs and take screenshots. The agent will often invoke the tools automatically when it is debugging or verifying it's work, without being explicitly prompted to do so.
It's a little bit of a set up process, as it requires a browser extension on top of the MCP configuration.
https://openai.com/chatgpt/team/ for documentation, coding, debugging, devops issues
https://github.com/features/copilot for coding
Now where I do think there is opportunity is in building out the standalone Gemini app, as ChatGPT has proven with their Teams product that there is business value in having a dedicated chat UI for your business. We are currently subscribed to ChatGPT for Teams and use it every day across product and engineering, there isn't a need for it to be integrated directly into our productivity suite UX, but pulling data out from the suite (e.g Google Drive) into the chat UI is helpful. Organizing project folders, custom GPTs etc also hold value for us.
news.ycombinator.com##body:style(background: #121212;)
news.ycombinator.com##td:style(color: #d0d0d0 !important; line-height: 1.6; font-family: Open Sans, sans-serif !important;)
news.ycombinator.com##td.title:style(font-size:20px !important; font-weight: bold; color: #4e8cbe !important; font-family: system-ui !important; )
news.ycombinator.com##td.subtext:style(font-size:15px !important; color: #a0a0a0; font-family: system-ui !important;)
news.ycombinator.com##table:style(background-color: #1e1e1e; padding: 15px; border-radius: 6px;)
news.ycombinator.com##div.toptext:style(color: #d0d0d0 !important; font-family: system-ui !important;)
news.ycombinator.com##div.commtext:style(color: #d0d0d0 !important; font-size: 1.5em; font-family: system-ui !important;)
news.ycombinator.com##span.c00:style(color: #d0d0d0 !important)
news.ycombinator.com##a:style(color: #4e8cbe !important; text-decoration: none;)
news.ycombinator.com##a:hover:style(color: #6aa0cc !important; text-decoration: underline;)
news.ycombinator.com##span#karma:style(color: #6aa0cc !important)
news.ycombinator.com##span.pagetop:style(color: #d0d0d0 !important)
news.ycombinator.com##textarea:style(color: #d0d0d0 !important; background: #252525; border: 1px solid #333; padding: 5px; border-radius: 3px;)
news.ycombinator.com###hnmain:style(background: #1e1e1e !important; box-shadow: 0 2px 6px rgba(0, 0, 0, 0.3); border-radius: 6px;)
news.ycombinator.com##div.votearrow:style(width: 18px !important; height:18px !important; background-size: 18px !important;)
Talk to your users relentlessly, find out how they use and don't use your product. Get a deep understanding of their workflows and user journeys in the product.
Trim the fat (shift focus) and solve problems they have that the product doesn't solve yet or solve well.
Reduce the steps in their critical user journeys. For example, if it's something they do every day, going from 5 clicks to 3 clicks adds up over time and improves satisfaction.
Dive into metrics and implement quantitative metrics where they don't exist. Survey users for qualitative metrics.
Bring data (metrics, market research, customer quotes etc) to executive meetings to back up your ideas, data speaks louder than your words.
Basically, if your product is in the market you don't need to always guess what to build, your users will guide you. That's not to say you can't innovate too, but a large part of being a PM is bringing the user experience and their frustrations to your team to action.
Works from Apple and Google mobile devices with Spotify