raviisoccupied

>If you are not a software engineer you can judge code the same way as you can judge design while not being a designer.

Very true.

I am not an engineer, I can't look at code and determine if it is good, performant, or elegant. However, I can look at designs and make a judgement. I'm curious to see how Claude Design changes how I think about AI and its capabilities.

'It's not X, it's Y' sentence formulations are usually indicative of LLM assisted writing.

I don’t think this is a spicy take at all. A PM’s job is to prioritise, and the most important/high priority projects will naturally be handled by Engineers enabled with AI-coding workflows. The high priority/impact work should be allocated to the folks with the highest level of skill.

I feel like PMs coding unlocks a whole new category of work, mainly addressing the long tail of cool ideas/small optimisations that ordinarily would not be addressed. Time will tell how valuable these items are in the long term.

And I say this as a PM.

> If you don't schedule it, it's not real

Personally I find this kind of approach infantilizing. I don't think it's fair to have an expectation of yourself or of your colleagues to spell out in Google Calendar what you/they are spending their time doing throughout the day. People should look at gaps in people's diaries not as opportunities for new meetings, but as time someone is probably spending doing something important or interesting.

Honestly, I'd suggest a prioritsation matrix here.

Classify all the tasks with an impact / ease score from 0-5. Multiply the numbers together to understand the relative priority of each item.

It won't be perfect but it will a good place to start.

You also do this at a product level instead, and invest all your time onto one product to begin with. This might reduce your switching costs working between projects/products.

I’m an Obsidian user. I pay for Obsidian sync, and I love the philosophy behind their product. However, and I feel stupid for saying this, but I just find it confusing to use. It’s difficult for me to wrap my head around plugins, and understanding how it wants me to use it.

For now, I’m just sticking to using it for daily notes, but I feel there’s so much I’m missing.

I'm curious as to what risk means in this context?

UX feedback: When I scroll to the bottom of the page linked in the post, and click on the API/Pricing links in the footer, it fails to redirect me.

Former Product Marketing Manager here. When I saw the word 'designs' on your landing page, I assumed the application would convert my screenshot into a Figma file/equivalent. Instead it looks like your app creates social ready images of screenshotted UI. I wonder if there's a better word to use than 'designs' that better captures what looks like the intended use case.

Thank you for linking this