codebase

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.5% — this entity appeared in 15 of 2,852 analyzed posts/comments in the seven days ending that day (15 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 23:48 UTCComment

   addressing the argument instead of creeping through my profile requires actual technical logic if believing that unreviewed code causes tech debt makes this sub fucked then i pray for whatever codebase you are managing

2. 2026-10-15 21:56 UTCComment

   that 2 am outage rehire wave is going to be legendary contractors will be naming their price when the whole codebase goes down and management realizes no one knows how to debug it 😄

3. 2026-10-14 13:37 UTCComment

   Currently our PRs tend to be relatively small. Occasionally there will be a massive one, but it's very rare in my team. I think this is largely due to the fact that we're in the middle of rebuilding an old system from the ground up, so there's rarely a need to refactor a huge portion of the codebase. Some of our features are quite complex though. I had to stop the PM a few weeks ago when he tried to make a single ticket for a feature. I told him I'd meet with the team and figure out how we could break it up. We broke that single ticket down into 30 separate tickets. And it's funny how impressed the PM was when we completed 6 of those tickets in a single day yesterday. If we only had his one original ticket it would've been a month before a single PR was put up for review. Instead we look like we're flying along.

4. 2026-10-14 01:51 UTCComment

   Not AI. This is what giving a damn sounds like. Review is not fun, it's necessary. We made it our practice to check out the code in our dev environments (which we could spin up on demand) and functionally tested it, if viable. Running tests is the least I would accept for a review. We didn't have dedicated QA so that was our job too. If someone didn't understand the change or subject well enough to judge, we would usually run a "pair review" where the author would at least walk through the requirements and the change, proving out each and showing how it worked in their environment on a screen share. When you accept a change into your codebase, you accept responsibility to maintain it. And I wasn't willing to take ownership of something I didn't understand and hadn't fully checked. So personally, understanding a PR was a prerequisite for my approval. I was usually the guy who broke down requirements into stories, so I at least understood the ask, I just hadn't seen what the dev came up with to implement it. This all sounds tedious as hell because it is. It's rigour. It's what distinguishes engineering from hackery.

5. 2026-10-13 13:26 UTCComment

   And flash is beyond useless at anything that is not the most basic of apps. I certainly can't use it for any of my work. My last month's api usage was 2.8k$ listen I am not working for kiddy projects that you can code with a basic claude subscription, with my codebase I would run out of usage is less than two hours.