IndieWeb post types

This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:

29 October 2026

 Like

Liked Dare Obasanjo (@carnage4life@mas.to)
Post details
Attached: 1 image An Anthropic engineering manager argues coding interviews are poor predictors of engineering impact, which I strongly agree with. His advice to junior engineers? Work where the company makes money, challenge established assumptions, and build prototypes instead of waiting for permission. That’s been good advice for decades. AI just makes execution cheaper. https://felixrieseberg.com/hunger-beats-tenure-advice-for-junior-engineers/

by Jamie Tanna's profile image Jamie Tanna .

28 October 2026

 Listen

My favourite thing I heard second hand was "we don't have any incidents caused by AI, because we don't count them as AI - if a human vibe coded a PR, that's on them" which I partially agree with but also enjoy you can avoid blaming an AI mandate if you don't measure it 🙃

Listened to AI and Incidents with Sylvain Kalache
Post details
Sylvain Kalache, who runs the AI lab at Rootly, walks Matty through what AI SREs can and can't do during an incident. They get into why handing every small…

by Jamie Tanna's profile image Jamie Tanna . #ai #incident-management.

 Listen

🍿👀

Listened to Can You Trust Code Written Without AI? Agents, Security, and Software Careers in 2026 by Overcommitted | Software Engineering and Programming Insights
Post details
Can you trust software written without AI? We examine the risks of manual coding versus automated vulnerability exploits.At Rails World 2026, a show of hands revealed that writing material amounts of code by hand is becoming a rarity. We discuss whether that human-written code is actually safer, especially after reviewing the eMudhra certificate authority compromise where private keys were recovered in under a second. Between open-weight models demonstrating Mythos-class exploit skills and the ongoing debate over AI consciousness, the security landscape has shifted significantly.This conversation is for engineers navigating the reality of AI mandates at work and the impact of agents that continue running after you log off. We also cover the practical side of professional development, from Bethany building a holiday gift-list app to Brittany replacing cloud subscriptions with local transcription tools. By analyzing these technical shifts, we aim to help you maintain a grounded perspective on your career trajectory.Subscribe for weekly software engineering breakdowns, and comment on which professional challenge you want us to tackle next.HostsOvercommitted: https://overcommitted.devBethany Janos: https://www.trustyduck.devBrittany Ellich: https://brittanyellich.com

by Jamie Tanna's profile image Jamie Tanna .

27 October 2026

 Like

Liked kat cosgrove (@kat.lol)
Post details
I was going to write something flowery and post a bunch of photos but I just don't fucking have it in me. I had to put Espresso to sleep. She was just a couple weeks shy of her 23rd birthday and she was perfect. I am not ok and am taking some time for myself. If you need something, no you don't.

by Jamie Tanna's profile image Jamie Tanna . #grief.

26 October 2026

25 October 2026

 Repost

Reposted Josh Bressers (@joshbressers@infosec.exchange)
Post details
I'm not sure claiming "everything is on fire" is the correct takeaway here There is a pile of flammable materials we've been ignoring for decades. It catches on fire sometimes. It caught on fire a lot this week And the people who put out the fires, for free, put the fire out again The current plan is to just keep throwing more oily rags on the pile. We could try to help the volunteers, but that costs more than adding oily rags to the pile

by Jamie Tanna's profile image Jamie Tanna . #open-source.

24 October 2026

 Like

Liked BrianKrebs (@briankrebs@infosec.exchange)
Post details
Got some unwelcome news first thing today: Someone I've known for many years recently took their own life. Feeling angry and sad and like a shit friend because we lost touch at some point, and I had no idea of their struggles. But I definitely could have been more curious. My response so far since hearing this news has been to reach out to a few people I've not checked in w/ for a while.

by Jamie Tanna's profile image Jamie Tanna . #grief.

 Like

Liked Andrea (Drea) Tamar Pinski (@pinskia@hachyderm.io)
Post details
Maintainers of open source projects should be mentoring folks to become their replacements. Not just thinking this is about controlling their project. I have learned this the hard way for gcc. You can't just think it is your way or the highway. Also gsoc is NOT a replacement for mentoring inside the project. It should supplement the mentoring that is done, just like an internship. Also this is not unique to gcc, it is many open source projects. And then there is the gaming of github stats, the one or two commits in llvm and leave issue. Those are used to gain stats for a job. Seriously open source is broken because of the gaming of the system. Even inside companies where you have the person with the most open source commits. Or the person who opened the most issue. Or the person who reviewed the most. (What is funny is that i am that person but I am not trying to play the game of counting, I am just trying to push gcc forward). At the same time I am mentoring folks both inside and outside of qualcomm on both gcc (and even to a less sense llvm) and performance analysis. But going back to my original point is mentoring and maintainship overlaps. It is not one or the other but rather both in the same role. By the time you step down you should have at least mentored a few to be able to take you from you. If you have not you partially failed a as a maintainer as the project will no longer can be maintained in the future.

by Jamie Tanna's profile image Jamie Tanna . #open-source.

23 October 2026

22 October 2026

 Listen

Listened to Raising An Agent: The Company of the Future
Post details
Quinn and Thorsten sit down together in San Francisco to answer the question they get asked most: how does the Amp team work? They walk through a week at Amp, from Thorsten's Sunday post and the single Monday meeting to writing down goals in silence. They explain why Amp has no quarterly goals, no departments and no territory, and how feature flags and the work in progress, orb good and orb bad channels keep a team of 21 in sync. They also cover reviewing changes with agents, pushing to main without mandatory code review, and why they think more companies will soon work like this.

by Jamie Tanna's profile image Jamie Tanna .

Browse by date

Every post of these types, by when it was posted. The brighter a month, the more was posted that month.

JanFebMarAprMayJunJulAugSepOctNovDec
2026197117135154207129124151112214
2025333195178180192161171144121154188137
2024396379413323349225233182177199215323
202310198101014498381355261595709730692593
2022109066410451673119212881236688635109920441463
20214712573624474133162772442834935551132
2020580747900611777682676611522483321450
2019433554466756729798179197339
2018403050694754334035374132
2017514761557664585760412536
201633111034343536
2015112
201412