Hola github.com/rsinger86/django-…

About Getting or Setting a Cache Value djangotricks.com/tricks/58SW…

In my experience, you can find enormous (and often obvious) performance wins in most systems because no one else has bothered to look

My current experience with coding models.

software engineering in 2026: - your package manager is compromised - your cloud provider blocks your account - github itself is hacked software is solved

There will be a regression to the mean. For now, every developer is under pressure to do more with AI, even at the price of losing observability and understanding of their code base. Eventually, we'll regress to a point where we get the productivity boost from LLMs while still staying in control of what the code does and taking ownership. It will probably take a few large-scale disasters for that to happen. But it eventually will. There is no free lunch in AI.

We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.

didYouAskClaude

nothingUnexpectedCanEverHappenInASprint

Si todo es urgente, nada lo es.

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

legendaryCommentUpdated

what it feels like to log onto this app these days

whatIsTheUrgency

weUsedTo

⏰ ¡Se acaba el tiempo! Solo queda una semana para enviar tu propuesta a PyConES 2026. El reloj corre y no queremos que te quedes fuera. ¡Envía tu charla o taller ya! 🐍🔥 📅 Deadline: 17 de mayo 🔗 pretalx.com/pycones-2026/cfp #CfP #CallForSpeakers #SpeakerAlert

Todos los puentes festivos dejan la misma lección: necesitamos que todos los fines de semana sean de 3 días.

🔁 ¡Ampliamos el plazo de la llamada a propuestas de PyConES 2026 2 semanas más! ¿No sabes por dónde empezar? ¡Contamos con mentoría en charlas@2026.es.pycon.org! 🗓 Nuevo deadline: 17 de mayo 🔗 pretalx.com/pycones-2026/cfp #CfP #CallForSpeakers #SpeakerAlert