avk

I’m intrigued by the ideas presented here:

– “Most tools… devalue the role of design – prioritizing how things look over how they work over or what problems they solve.“

– “… A designer work should amount to more than static mock ups that’s slowly drift from implementation.“

- “A new, human-readable, AI-friendly language for product design.”

– “Nobody can rent you limited access via other MCP server.“

- “…an interconnected design system of not just buttons and components, but screens, flows, and use cases. A home for design decisions, and a living source of truth…”

I’m in a similar boat. I do like the idea of code as material and this could be a version of that.

I find conceptual work is sending me back to paper and lower fidelity even more these days with AI. The fundamentals thrive with more freeform tools.

I still find system tests useful and more realistic, despite their speed. They’ve caught bigger, breaking changes for me than unit or controller tests.

Good read, but the abrupt end surprised me. It didn't dive deeper into the solution to evaluate whether it actually addressed the observed issue.

Also, isn't the accessibility of radio buttons for keyboard users something you simply learn? <Tab> isn't the panacea of getting around a web page with a keyboard. I think of <Tab> as navigating interactive elements by default, but within those elements the arrow keys allow more granularity. Several instances of that behavior, including radio buttons, shown here: https://webaim.org/techniques/keyboard/#testing

Have you seen the Short Story Substack[1]? I appreciate how forthcoming the editor is with the stats.

[1]: https://shortstory.substack.com/

Yes, but it depends on where you submit. I've seen literary journals pay in contributor copies (aka nothing), token amounts—a few dollars, a rate per page, or a fixed rate up front. Genres like sci-fi, fantasy, horror, and crime or mystery are more likely to pay per word. Not sure why that is.

Congrats to superamit! Well done with your persistence and I hope Uncanny is receptive to your future submissions. I'm excited to read the story.

Disclaimer: light self-promo. Are others interested in more publishing posts like these? I've documented the journey to publication stories with stats, rejections, and a sense of the work involved for most of the short fiction I've published in literary journals. It's been cathartic and encouraging to share the entire process.

My most notable piece[1] ended up making it into The Best American Mystery Stories[2] a few years ago.

[1]: https://arsenalofwords.com/2018/10/30/how-loathing-travel-pu...

[2]: https://arsenalofwords.com/2019/10/01/how-a-regional-writing...

I've been tinkering with something similar too. This is for timing checklists not individual items—so typically multiple steps that repeat from time to time: https://tusklist.com

Can you say more about why it's useful to time routine work?

That's what I'm curious about. A consistent set of steps that you're committed to doing on some frequency—do you see value in timing things like that?

Has anyone else applied product or agile techniques to creative endeavors? Thinking about retro made me wonder whether doing a regular standup with my writing could lead to new insights, akin to freewriting or journaling.

you misspelled "test" as "tets" on the sign in page

Likewise, I found it distracting and off-putting.

Sorry for the resubmit. Just surprised this didn't garner any previous discussion.

The part that resonated most with me was: "What bone you were meant to have, no dog will drag away." It made me think that it's worth considering which bones are yours and which you only think you'd like to have and improve on. Maybe it's worth re-evaluating what you do spend time on versus what you never feel bad spending time on?

> "This is an instance of a more general rule: focus on users, not competitors. The most important information about competitors is what you learn via users anyway."

I found this to be the strongest way of saying don't obsess about your competition. Focusing on users will probably help address other issues as well (i.e. working on the wrong problem, building the wrong thing, not making as much of an impact as you could be, etc).

Cool hack. Have you considered linking to the startup's Github page or the pages of the developers?