When Code Becomes Cheap, What's Left? | SoftwareEngineeringLinks

FAUN.dev's Software Engineering Weekly Newsletter

🔗 View in your browser | ✍️ Publish on FAUN.dev | 🦄 Become a sponsor

SoftwareEngineeringLinks

This Week in Software Engineering, with Varbear the Bear

📝 A Few Words

AI made writing automation cheap. It did nothing for running it.

A model will hand you a working playbook in seconds. It will not tell you who's allowed to run it, against which inventory, with which credentials, on what schedule, or what happens when it dies halfway through 200 hosts. Authoring dropped to near zero but operating it didn't move.

That gap is widening: the more playbooks get vibecoded, and the more agents start firing them off on their own, the more you need a layer that decides what actually executes, with what privileges, and leaves a record when it does. That layer is AWX.

So I released a book about it. AWX in Action: Ansible Orchestration at Scale (expanded edition) is the practical guide: deploying AWX on Kubernetes with the operator, wiring up projects, credentials, RBAC, workflows, and execution environments, scaling past a single node, using the CLI, understanding the settings and much more!

The book is the half AI won't write for you. It's already the #1 Hot New Release in Distributed Systems & Computing on Amazon, which tells you how many people are stuck on the operating half.

You can get your copy on:

👉 FAUN.dev
👉 Amazon

Have a great week,
Aymen.

🔍 Inside this Issue

Copilot pricing drama is forcing teams to put real guardrails around AI usage, just as supply-chain trust in dev tooling takes another hit. The thread running through everything below: when code is cheap, taste, judgment, and security posture suddenly become your highest-leverage skills.

💸 AI costs how much? GitHub Copilot users react to new usage-based pricing system.
🧩 Design Patterns Are Dead. Long Live Design Patterns.
🛡️ GitHub breach: The development ecosystem is in the hot seat
🧠 I Did 11 Technical Interviews in 60 Days. Here Is the Pattern Nobody Tells You.
🧾 When Code Becomes Cheap, What's Left?

Take care!
FAUN.dev() Team

⭐ Patrons

bytevibe.co

Git Happens - The Tee for Everyone Who's Pushed Straight to Main

We've all done it. Skipped the merge conflict, hit push, and watched the pipeline turn red in real time. No rollback, no excuses. Git happens.

This is the shirt for engineers who wear their worst commits like a badge. Soft, smooth, and built to disappear into whatever you throw on over it - the kind of tee you reach for on standup days and outage nights alike.

The joke lands at the meetup. The fit makes it the one you actually keep wearing.

Own your chaos, order now, ships in 2-9 business days.

faun.dev

Git, Finally Visual. Finally Clear.

Most developers don't actually understand Git. They memorize four commands, copy-paste the rest from Stack Overflow, and quietly panic every time a merge goes wrong. This course fixes that. **Learn Git in a Day - The Visual Guide** turns branches, merges, rebases, and resets into clear pictures you can hold in your head, so you finally know what's happening instead of hoping it works..

One focused day, and Git stops being the tool you're afraid to touch.
Start today and own Git by tonight

👉 Spread the word and help developers find you by promoting your projects on FAUN. Get in touch for more information.

🔗 Stories, Tutorials & Articles

medium.com

Design Patterns Are Dead. Long Live Design Patterns.

Design patterns were created for human comprehension, not machines, serving as a shared vocabulary to communicate complex ideas quickly, manage working memory, and standardize solutions. Even in the era of AI-generated code, design patterns are crucial for containing the limitations of AI models and ensuring reliable outputs. It's not about obsolete practices but rather evolving the role of design patterns to provide architectural guardrails and intent compression for AI-generated code.

arstechnica.com

AI costs how much? GitHub Copilot users react to new usage-based pricing system.

GitHub began usage-based Copilot billing, and some developers say they used up the AI credits GitHub grants for a month in under 24 hours.

Developers burn credits through "premium requests". GitHub counts prompts to advanced models, agent tasks, edits, and some Copilot features against the allowance. During a long agent run, you can consume many requests fast. A team that treats Copilot like an open-ended coding agent can hit the cap sooner than expected.

Team admins should check:

Plan allowance for each seat
Models that consume premium requests
Per-user usage in the Copilot dashboard
Spending limits and policy controls
IDE settings that default to costlier models

blog.stackademic.com

I Did 11 Technical Interviews in 60 Days. Here Is the Pattern Nobody Tells You.

The key insight from the article is that at mid-to-senior backend levels, coding rounds matter least while judgment, communication, structure, and ability to defend decisions are critical. Focus on rehearsing key design, incident, and behavioral answer structures to succeed, not just LeetCode.

spin.atomicobject.com

When Code Becomes Cheap, What's Left?

Teams that use Claude Opus 4.6 for spec-driven development generate code at low cost, so they spend scarce developer time on review and QA. Developers create more value by judging code than by typing it.

reversinglabs.com

GitHub breach: The development ecosystem is in the hot seat

GitHub is reeling from an infrastructure breach by TeamPCP, highlighting the vulnerability of developer environments. Privileged access was achieved not through traditional perimeter exploitation, but by targeting trusted developer tools like IDE extensions. This incident serves as a stark reminder that organizations must prioritize security measures like least privilege, continuous validation of plugins, and zero-trust enforcement to safeguard their software supply chain. Trust in the supply chain is at an all-time low, necessitating a shift towards a more resilient security strategy to combat the escalating threat landscape posed by cybercriminals like TeamPCP and their sophisticated attack vectors.

👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community.

⚙️ Tools, Apps & Software

github.com

microsoft/markitdown

Python tool for converting files and office documents to Markdown.

github.com

ogulcancelik/herdr

Agent multiplexer that lives in your terminal.

github.com

virgiliojr94/book-to-skill

Turn any technical book PDF into a Claude Code skill — ready to study, reference, and use while you work.

github.com

reconurge/flowsint

A modern platform for visual, flexible, and extensible graph-based investigations. For cybersecurity analysts and investigators.

github.com

ljtn/epiq

CLI based issue tracker TUI - distributed and backed by git

👉 Spread the word and help developers find and follow your Open Source project by promoting it on FAUN. Get in touch for more information.

🤔 Did you know?

Did you know that SQLite, the tiny serverless database embedded in browsers, phones, and even Airbus A350 flight software, owes much of its reliability to an enormous testing apparatus rather than to the code being small? It leans on fuzz testing, which throws billions of malformed and randomly mutated inputs at the engine to hunt for crashes, and on differential testing, where the same query runs with the optimizer turned on and then off to confirm both paths return identical answers. That combination is how a database light enough to fit in firmware earns the trust to run where failure is not an option.

🤖 Once, SenseiOne Said

"Good dev tools remove friction so effectively they also remove doubt, and doubt is where most bugs are caught. The trick is to automate the typing, not the thinking."
— SenseiOne

(*) SenseiOne is FAUN.dev’s work-in-progress AI agent

😂 Meme of the week

❤️ Thanks for reading

👋 Keep in touch and follow us on social media:
- 💼LinkedIn
- 📝Medium
- 🐦Twitter
- 👥Facebook
- 📰Reddit
- 📸Instagram

👌 Was this newsletter helpful?
We'd really appreciate it if you could forward it to your friends!

🙏 Never miss an issue!
To receive our future emails in your inbox, don't forget to add community@faun.dev to your contacts.

🤩 Want to sponsor our newsletter?
Reach out to us at sponsors@faun.dev and we'll get back to you as soon as possible.

SoftwareEngineeringLinks #531: When Code Becomes Cheap, What's Left?
Legend: ✅ = Editor's Choice / ♻️ = Old but Gold / ⭐ = Promoted / 🔰 = Beginner Friendly

You received this email because you are subscribed to FAUN.dev.
We (🐾) help developers (👣) learn and grow by keeping them up with what matters.

You can manage your subscription options here (recommended) or use the old way here (legacy). If you have any problem, read this or reply to this email.