191–200 of 278 posts
Earlier quoted context omitted.
My whole comment was about the need for a thinking, feeling human being. Is it surprising that I am emotional about it?
Emotion takes away from the idea. Instead of thinking: "Oh this is a great point. There is immense economic value here." It becomes: This person is fearful of their job and used feeling to justify their belief.
Earlier quoted context omitted.
Because this is what capital has told us. Capital always wants to reduce the labour cost to $0.
If labor cost is close to $0, even more businesses that weren’t viable before would become viable. Do you not see the logic?
Im not kidding when I say the tone feels AI generated. It’s obviously not AI generated but I’m more speaking to the tonality of the latest gpt. It’s now extremely hard to tell the difference.
Earlier quoted context omitted.
That doesn't make sense. Demand isn't entirely dictated by cost. There is only so much productivity the world is equipped to consume.
What difference does that make? If the cost of an engineer is zero, they can work on all kinds of nonsensical things that will never be used/consumed. It doesn't really matter as it doesn't cost anything.
Good human written docs > AI written docs > no docs > bad human written docs
This was at #1 on the front page like an hour ago, and now after almost 100 new comments it’s off the front page at #40. What happened?
Earlier quoted context omitted.
> They act as stand-ins for actual users and will flag all sorts of usability problems True, but it raises another question, what were your Product Managers doing in the first place if tech writer is finding out about usability problems
Realistically, PMs incentives are often aligned elsewhere. But even if a PM cares about UX, they are often not in a good position to spot problems with designs and flows they are closely involved in and intimately familiar with. Having someone else with a special perspective can be very useful, even if their job provides other beneficial functions, too. Using this "resource" is the job of the PM.
> But even if a PM cares about UX,
How can a PM do their job if they don't *care* about UX?
I mean... I know exactly happens because I've seen it more than once: the product slowly goes to shit. You get a bunch of PMs at various levels of seniority all pursuing separate goals, not collaborating, not actually working together to compose a coherent product; their production teams are actively encouraged to be siloed; features collide and overlap, or worse conflict; every component redefines what a button looks like; bundles bloat; you have three different rendering tools (ok, I've not seen that in practice but it seems to be encouraged by many "best practices") etc etc
AI works well for one kind of documentation. The kind of documentation no one reads, that is just here to please some manager, or meet some compliance requirement. These are, unfortunately, the most common kind I see, by volume. Usually, they are named something like QQF-FFT-44388-IssueD.doc and they are completely outdated with regard to the thing they document despite having seen several revisions, as evidenced by…
not true! it's read by other LLMs! /s