email

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-08-28

Final complete day: 2026-08-28. Attention was 1.4% — this entity appeared in 37 of 2,594 analyzed posts/comments in the seven days ending that day (64 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-08-28 08:25 UTCComment

   You can interact with GitHub issues via email, iirc they come through as one email thread per issue, and replying to the email thread adds a comment. You can get a solution that works for both of you; PM gets to use email and the rest of the team get to use an actual, functional, searchable, linkable, fucking issue tracker

2. 2026-08-28 03:31 UTCComment

   Get written authorization and a full asset inventory before you write any proposal. You cannot price maintenance or infrastructure transfer without knowing the registrar, DNS, hosting, email, SSL, repositories, licenses, and third party services involved.

3. 2026-08-27 17:58 UTCComment

   i stopped trying to convert people and just treat email as the intake form. Copy every message into GitHub issues yourself so you have a searchable record when she inevitably asks about something already decided

4. 2026-08-27 17:26 UTCComment

   Getting PMs to use tasks (in our case it's just Jira at the moment, but it's better than nothing) in a consistent way is a serious struggle at our company. Some won't use them unless we demand it, preferring emails, IMs, or voice chats. Others use them properly but inconsistently, and seem to have personal rules for what "needs" to be a task. The best way is to convince their boss of the right way to do it and have them mandate it, but that's not always possible as you say. The second best way is to ask nicely, explaining the benefits task management give you both: keeping track of all work required and not missing anything, having it in a nicely prioritized list, in your case having it integrated with your devops stuff, etc. But some PMs dgaf, and may actually prefer to not use task tracking precisely because they don't want a paper trail and want you to prioritize their demands over other stuff whether it's important or not. The other way is to establish your own rules which effectively deprioritize non-tasked demands, and follow these consistently until the PM is well-trained. "Sorry, I can't do your thing/talk to you about a thing you want right now, I am working through my task list."

5. 2026-08-27 15:32 UTCComment

   At my agency, our project managers/producers not only create issues, but they set priority (as well as other details) in a gh project board. Emails are a firehose of tasks, whereas issues/project boards can be clearly organized to show importance and if it's a feature, bug, etc. This is all part of the project manager's job to figure out scheduling, priority, etc -- issues/project boards can be a super useful tool for them to keep track on progress. Rather than doing this part yourself, I would share with your PM how useful issues/project boards are (loom/screen recording if you're remote). And firmly, but politely stand your ground that this process is part of the job and needs to be followed -- while welcoming feedback on improving the process.