office

Attention over time

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

Final complete day: 2026-10-15. Attention was 0.2% — this entity appeared in 5 of 2,852 analyzed posts/comments in the seven days ending that day (6 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-10-15 21:55 UTCComment

   AI is used to determine how to shit at my office. Can’t have any meeting that are not AI focused.

2. 2026-10-14 15:53 UTCComment

   Honest answer that needs to be said. I could teach this to my wife in an afternoon, she'd need to practice syntax, but conceptually, it's there. That being said, I have gotten tied up on the dumbest stuff due to being stresses out in an interview. My two favorites were: - writing a "memory-less" stopwatch in TDD: I was interviewing for the fornt and lead for the intuit turbo tax team, the two snarky engineer interviewers were so condescending in how they interacted I spent more time panick brainstorming a way to politely decline finishing the interview while I stare blankly at my pseudo code on a white board. I got there in the end, solved it via TDD, wrote the pedudo code for the tests. They said I did well, but they just ghosted me. The job was using Handlebars.js, so, I took the unorthodox approach of being bold and I built an entire todo application in handlebars to show I knew the language, they didn't even look at it. - iterating over 100 cats, adding a hat to each cat via a loop where the loop increments the step count by one each iteration : I was interviewing for AppAcademy, I thought it'd be such an amazing opportunity and I was desparate. I had spent all night panicked about the interview. It was an application for their ruby on rails program. I'd even gone up to SF the weeks prior to check the place out. In hindsight it was actually super sketchy, there were students who couldn't afford housing in the city just calling out in the office with sleeping bags. That's not the only time I've heard of that at bootcamps, though. Anyhow, I spent so much time panicking when I had the interview I LITERALLY FORGOT HOW TO WRITE RUBY... I was doing RoR the last year or so, even on a paid client project. I panicked and did the entire interview in PHP, lol.

3. 2026-10-12 21:02 UTCComment

   Never take a job you don't know the return on or are unwilling to accept zero. Sometimes I know it m9ght be zero or a six pack or pizza or something. I do those just to do something nice. But if it's a business, we have an agreement. I'm supposed to do some networking for this lawyer's office. Even though its for a friend of a friend's sister and I'll be working as a favor to my good buddy, we're still charging...it's a law firm...

4. 2026-10-12 17:26 UTCComment

   That's why I don't do anything on my own for a company, unless I'm really well paid. You have to think the office way, when a regular Joe gets an office, its mind and values change completely. Never expect they'll fulfill their promises, they'll sell you and your knowledge, or scrapt your work like trash. In their eyes, we the people, the workers are expendable, just labor. American companies are like communists, they like freebies more than the poors, and expect we the people to give them our knowledge for free, or very cheap.

5. 2026-10-12 13:56 UTCComment

   For the NAT case, one option that doesn't creep toward fingerprinting: an ephemeral tab-scoped id. Generate a random id client-side on page load, hold it in memory (or sessionStorage so reloads don't inflate), and send it with each event. You never store it beyond the session window and it dies with the tab, so there's still no cross-day identity. Two people behind the same office NAT + same UA now get distinct sessions, which is exactly the collision that breaks your 30-min session logic. Trade-off is it mildly over-counts multi-tab users, but that's usually smaller than the NAT under-count. Nice writeup btw — the visibilitychange flush over unload is a detail a lot of people get wrong.