I used to write case studies for B2B tech and the writing part was honestly fine. The real pain was tracking down the devs and PMs who built the thing.
By the time marketing wants the story, half the team forgot the numbers or moved to another project. You end up Spending weeks chasing people on slack just to get basic details.
Is this normal everywhere or were my old companies just bad at documentation?
I spent months tweaking copy trying to fix mobile conversions, only to realize my main button was totally pushed below the fold on smaller screens.
Turned out IPhone 12 and smaller users couldn't even see the without scrolling.
I only caught it by accident on a friends phone since it looked fine on mine. Now i'm wondering how many basic design bugs i'm missing just by testing on my own device.
Do you manually check your site on older phones or rely on tools to flag this?
Found about MCP servers earlier this year, but only the last few weeks im getting my hands dirty with them. Im doing things with Typescript and Im struggling with integrating custom clients with mcp servers. Is anyone going through the same path?
PS: Im not asking about building an MCP server or connecting it to Claude Desktop, Cursor or something like that. That is easy, and Youtube is packed with videos about it. Im talking about custom frontends/clients and how to easily integrate them with MCP servers.
I used to skip writing down anything because it was just me and i had everything in my head. But then i took a short break recently and completely forgot why i made certain decisions in the code. Spent hours trying to figure out my own stuff.
Now i just leave quick notes on things that aren't super obvious. Nothing fancy just a line or two so future me doesn't get stuck.
Where do you draw the line between useful notes and just wasting time on docs?
Launch week retention is easy to get. I want to hear about week 6, when the novelty is gone and your tool is competing with the spreadsheet it replaced.
If you've shipped something that took over from a Google Sheet or a Notion table, what kept people in it past the first month? And what did the ones who left go back to?
My first instinct was to show one simple count. Then I ran into a problem: writers usually care about visible characters, while browser form limits can use UTF-16 code units. A draft can look fine in one counter and still fail a form field.
I m considering two approaches:
Show only a simple count until someone selects a target like web form .
Show both counts from the start, with a short explanation.
I lean toward the first option because most people should not need Unicode terminology while writing.