[-] mattvanlaw@lemmy.world 1 points 1 day ago

I guess you mean like full outtage for all users? My bad just a lot of ways to take the verb "down" for me. Still, though, what a crappy company to not learn but fire from that experience!

[-] mattvanlaw@lemmy.world 1 points 1 day ago

Sorry, but as another reply: pushing bugs to production doesn't immediately equate to firing. Bug tickets are common and likely addressing issues in production.

[-] mattvanlaw@lemmy.world 2 points 1 day ago

It's mainly for developers to follow decisions made over many iterations of files in a code base. A CTO might crawl the gitblame...but it's usually us crunchy devs in the trenches getting by.

[-] mattvanlaw@lemmy.world 2 points 1 day ago* (last edited 1 day ago)

Cursor, an ai/agentic-first ide, is doing this with a blame-style method. Each line as it's modified, added DOES show history of ai versus each human contributor.

So, not nonsense in probability, but in practice -- no real enforcement to turn the feature on.

mattvanlaw

joined 1 month ago