The Counting House (Steve Yegge)
An October 2026 essay by Steve Yegge on a pattern he sees emerging in how enterprises adopt and pay for AI coding tools.
Resource Hub
3488 hand-picked resources for students, job seekers, career changers, founders, and AI learners — 100% free to browse with no account required.
Filtered by tag
Answers come only from resources in this hub, with the sources listed.
95 resources
An October 2026 essay by Steve Yegge on a pattern he sees emerging in how enterprises adopt and pay for AI coding tools.
A blog post arguing that organizations which do not give employees time to practice with AI coding tools risk falling behind competitors that do, with examples of workflow shifts in software engineering teams.
Blog post by Sujith Jay Nair (September 22, 2026) on how staff engineers on platform teams, which usually lack a product manager or roadmap, decide what to build next. It groups the signals into four sources: the systems, the users, the organization and the wider industry.
Blog post by software consultant Graham Lee (Structure and Interpretation of Computer Programmers), published October 6, 2026. It lists common objections to AI-generated code — code as art, AI as a job thief, software engineering as a set of rules, and AI companies as bad actors — and argues against each from the author's point of view, including a section on how programming jobs relate to automation.
Technical newsletter by Vinoth Govindarajan taking AI agents apart: control loops, memory, orchestration, evaluation and what breaks in production. Recent series walks through the OpenCode architecture end to end.
Why I recommend it: Free to subscribe, over 2,000 readers; written for people who build software, not for beginners. Substack publications can add paid-only posts at any time, so check the top of a post before counting on it.
A free library of technical-interview material from CodeSignal: practice guidance, explanations of how coding assessments are scored, interview question breakdowns and hiring-process write-ups. Useful preparation if a company has sent you a timed coding assessment.
Why I recommend it: The resource library is free to read. Bear in mind CodeSignal sells assessment software to employers, so the writing naturally presents these tests as a fair measure of skill — read it for what it tells you about how the tests work and what they reward, which is useful when one lands in your inbox.
IEEE Spectrum article on how AI is shifting entry-level engineering work toward higher-order thinking, review and collaboration skills, and what recent graduates can do about it.
From the site: How can recent grads navigate a job market transformed by AI? Learn how to make AI work for you, not against you.
Why I recommend it: Free to read on IEEE Spectrum. Practical if you are early-career: it describes what junior work is turning into rather than predicting job counts.
Joe Procopio argues that "vibe coding"—letting AI write code without real understanding—is sliding into production disasters worth naming differently.
Why I recommend it: Inc. may show ads or meter premium articles; the link was accessible when it was added.
Question banks for more than 100 technical roles — Node.js, Azure, Golang, Kubernetes, OAuth and more — each with sample answers, updated regularly. Free to read with no sign-up.
From the site: Ready-to-use technical interview questions and structured guides for developer roles and frameworks, from Remix to Magento. Updated September 2026.
Why I recommend it: Written for the people doing the interviewing, which is exactly why it is useful — you get to see the questions and the answers they are grading against.
Technical writing on legacy modernisation, monoliths and microservices, technical debt, cloud migration and where AI coding tools break down on large old codebases.
From the site: Check out all latest posts from vFunction including modernization strategies, cloud migration best practices, and company updates.
Why I recommend it: technical rather than promotional, though vFunction sells modernization software. The pieces on AI assistants meeting million-line codebases are the honest ones.
A vetted marketplace matching senior engineers, researchers and AI specialists with companies. Free for engineers to apply and be matched; companies pay only on hire.
From the site: Hire global, AI-first engineers with Index.dev. Skip delays and scale your tech team with pre-verified, secure, and compliant talent to build faster.
Why I recommend it: Free on the candidate side — you are the product being placed. Expect a real vetting process rather than a quick apply button.
Articles on building and managing remote engineering teams, offshore hiring, and the day-to-day of software delivery — free to read.
From the site: Explore the nCube Blog for expert insights on software development, team building, and the latest tech trends. Stay updated and empower your business with knowledge.
Why I recommend it: A staffing company's blog, so it argues for hiring remote teams. Useful for understanding how distributed engineering teams actually get staffed and run.
Free public documentation explaining how an autonomous AI software engineer plans, runs and reviews coding work, including its limits and where human review is required.
From the site: Devin is the AI software engineer, built to help ambitious engineering teams crush their backlogs.
Why I recommend it: The product costs money but the docs are free — read them to understand what "AI engineer" tools actually do and do not do before anyone tells you your job is gone.
A technical design paper by Alice Poteat (Anthropic, August 2026) setting out how function hooks let plugins extend Claude Code — the event model, composition order, rendering and enterprise controls.
Why I recommend it: Advanced and unapologetically technical. Read it as an example of a clear design document as much as for the AI tooling itself.
A Breaking Change blog post on building tooling to build the tooling — an honest walkthrough of automating a small side business with AI assistance.
Why I recommend it: A good antidote to launch-day stories: most of the work is plumbing, and this shows the plumbing.
A free open format for writing structured assumptions and requirements next to the code itself, so AI coding agents build against stated rules rather than guesses.
Why I recommend it: Relevant even if you do not write code: it is a clear example of writing requirements precisely enough that a machine can follow them.
The public GitHub discussion where Anthropic and the community designed function hooks — a way for plugins to extend Claude Code — including the shipped design decisions and community feedback.
Why I recommend it: A rare look at how an AI product feature gets designed in public. Useful if you want to see how technical feedback is actually written.
XDA Developers had Claude Code (Opus 5), Codex (GPT-5.6) and Google Antigravity (Gemini 3.8) rebuild the same website from the same brief. The comparison shows which agent handles detail, polish and real-world edge cases best.
Why I recommend it: Useful if you are choosing an AI coding assistant for side projects or learning to prompt more effectively. The winner is not necessarily the one you would expect.
Barclays' technology internship track for software engineering, cybersecurity, infrastructure and product roles, with details on the programme and application process.
Why I recommend it: Worth applying to even if you picture yourself at a tech company — bank engineering internships pay well and teach you scale and security practices you rarely see elsewhere.
An AI design tool for product teams: turn a prompt, product requirement, or screenshot into high-fidelity UI, match existing design tokens, and explore directions before committing engineering time.
Why I recommend it: For founders without a designer: make something visual before you ask anyone to build it. The free tier is enough to test an idea.
An AI platform that designs, builds, and hosts a business website and the full-stack product behind it from a plain description, with hosting on your own domain included.
Why I recommend it: One of several build-by-describing tools now. Try a free project before paying anyone to build a simple business site.
Free ebook on building, monitoring, and troubleshooting AI agents in production: what to instrument, where agents fail, and the practices teams use to keep them reliable.
Why I recommend it: Useful even if you never build an agent yourself — it shows what serious teams actually worry about, which is good language to have in an interview about AI work.
Anthropic's free learning hub for Claude: structured courses with video lessons and quizzes covering Claude.ai, Claude Code, Cowork, the API, and MCP, with completion badges.
Why I recommend it: A free, name-brand AI credential path. The Claude 101 course alone gives you something concrete to put under "skills" instead of vaguely claiming AI experience.
A technical learning platform with 60,000+ books, 30,000+ hours of video, live online events, and interactive labs and sandboxes from O'Reilly and nearly 200 other publishers.
Why I recommend it: Check your public library card and any school or employer account before paying — many library systems give full O'Reilly access for free, and some live events are open to anyone.