Since its launch two-and-a-half years ago, our 12-megapixel autofocus Raspberry Pi Camera Module 3 has found a home in countless enthusiast projects, and in a wide range of industrial and embedded applications.

But we’ve found that some of our embedded customers want to integrate our camera technology into smaller form factors than our 25 × 24mm module footprint can support. To help these customers, we’re pleased to announce that the Raspberry Pi Camera Module 3 Sensor Assemblies are now available to purchase as standalone products, priced from just $15.

Raspberry Pi Camera Module 3 Sensor Assemblies offer the same IMX708 4608×2592 (11.9 megapixel) sensor, with 1.40μm pixels, and the same Phase Detection Autofocus (PDAF) capability as Camera Module 3. We are providing reference schematics and a bill of materials to assist you in integrating the required support components onto your own PCB.

Like Camera Module 3, Camera Module 3 Sensor Assemblies are available in both visible-light and infrared-sensitive (NoIR) variants, and with either a standard (75° diagonal) or a wide (120° diagonal) field of view; and like Camera Module 3, there is a $10 price difference between the standard FOV variants and the wide FOV variants.

Cameras are the original Raspberry Pi accessory, dating back to the launch of Camera Module 1 in May 2013. They are already found in applications as diverse as workplace safety, wildlife conservation, glacier stability monitoring, manufacturing quality control and museum-based education. We look forward to seeing Raspberry Pi Camera Module 3 Sensor Assemblies take our imaging technology to new and exciting places!

The post Available now from $15: Raspberry Pi Camera Module 3 Sensor Assemblies appeared first on Raspberry Pi.

I’ve been hearing it more and more lately.

“I’m just glad I still have a job.”

“It’s not ideal, but hey… it pays the bills.”

“Better to stay put than risk making a move right now.”

Look – I get it.

We’re living through one of the most unpredictable seasons in recent memory:

🛑 Layoffs in every sector
🛑 AI shifting the ground beneath us
🛑 Rising inflation, political tension, global unrest

It’s tempting to shrink back.

To cling tightly to what you’ve got.

To convince yourself that “stability” is the same as security.

But here’s the truth most won’t say out loud:

You’re not stuck because of the market.

You’re stuck because of a scarcity mindset.

And if you don’t snap out of it soon, your career will pay the price.

Let’s talk about what’s really going on—and how to get back into motion.

#1 – Scarcity shrinks your vision

When engineers operate in fear, the first thing they do is lower the bar.

The dream role becomes “whatever’s available.”

The 5-year plan becomes “survive the next quarter.”

The bold voice becomes silent at the table.

You stop leading—and start clinging.

But here’s the truth: no one promotes clingers.

No exec is saying, “Let’s invest in the engineer who’s just barely hanging on.”

Abundance starts by raising your vision again.

Don’t ask what can I hold onto?

Ask: What do I want to build next?

#2 – Scarcity glorifies gratitude (in the wrong way)

Gratitude is powerful.

But too often, I see engineers weaponize it against themselves.

“I should be grateful I even have a job.”

“People have it worse—I shouldn’t complain.”

Hear me: gratitude does not mean complacency.

You can be thankful for what you have and still want more.

You’re allowed to say: “This job served me—but it’s no longer aligned.”

That’s not betrayal. That’s wisdom.

The engineers who break through stagnation are those who say:

“Thank you… and I’m still growing.”

#3 – Scarcity keeps you playing defense

Engineers who wait for the economy to “get better” are engineers who get left behind.

Because here’s what the top 5% are doing right now:

• Getting clear on their Zone of Genius
• Networking intentionally while others stay quiet
• Upleveling their leadership skills
• Positioning themselves for the next opportunity, not the last one

This is the moment to go on offense.

The people who win in down cycles aren’t lucky.

They’re abundant thinkers who took courageous action when others froze.

#4 – Scarcity blames the environment. Abundance builds from within.

Is the market hard right now? Sure.

But you know what else is true?

You have skills. Experience. A track record of solving tough problems.

You’ve led teams, launched products, shipped code, saved millions.

You have value.

Scarcity will convince you to wait until someone else recognizes it.

Abundance tells you to own it now.

Update your resume.

Refine your personal brand.

Speak with confidence about your value—even if no one’s asked (yet).

Because you don’t get hired for what you might do someday.

You get hired for what you already believe you can deliver.

#5 – Scarcity keeps you isolated. Abundance gets support.

This is not the season to try and figure it out alone.

You need people in your corner who will:

✅ Challenge your assumptions

✅ Help you see blind spots

✅ Hold you to a higher standard

✅ Remind you of your potential

That’s what we do every day inside the Lifestyle Engineering Blueprint™️.

I’ve coached engineering managers who felt completely stuck…

…and 90 days later, they were back in motion, interviewing for roles they thought were out of reach.

The shift didn’t start with a new offer.

It started with a new mindset.

The post Scarcity Mindset in Engineering: 5 Ways a It Silently Kills Your Dream Career appeared first on OACO.

In this future-facing episode, Josh Anderson and Bob Galen make the case that great product leadership is more important than ever—especially in a world of AI-driven development, vibe coding, and accelerating speed. They argue that no matter how fast you can build, if you’re not building the right things for the right reasons, you’re setting yourself up for failure.

Josh shares lessons from his own real-time experience building a product with AI, discovering that clear context, product thinking, and human leadership remain the key unlocks for success. Together, they explore how to maximize the value of every line of code, why clarity is the real differentiator, and how product leadership is everyone's job—not just people with the title.

🔴 Join Josh's CTO Office Hours

Need help with your technology leadership challenges? Join Josh every Thursday at 11AM ET for live problem-solving sessions. Bring your scaling issues, team challenges, or technical decisions - get real answers from 25+ years in the trenches.

Free advice, zero sales pitch.

Watch live: Twitch/YouTube

More info: kazi.io

Robert C. Martin, more often known as Uncle Bob, has been programming since 1970 and has served as a mentor to generations of software engineers. He’s one of the original authors of the Agile Manifesto and played a foundational role in forming the Agile Alliance, where he served as its first chairman. But beyond titles and organizations, Bob’s lasting impact comes through his writing, his lectures, and his philosophy of software craftsmanship. He has spoken at conferences around the world — QCon, Agile 20XX, IT Days, and countless other industry gatherings — always advocating for clarity, discipline, and ethical responsibility in code. And if you’ve ever read Clean Code, The Clean Coder, or Clean Architecture, you know that he doesn’t just teach how to build systems — he challenges us to become better professionals in the process. His most recent work, Functional Design, continues this legacy, distilling decades of experience into patterns and principles that are just as relevant today as they were when he first put finger to keyboard.

Topics of Discussion:

[2:22] Uncle Bob’s advice for young programmers entering the field: Be cautious with AI tools, learn fundamental programming skills, and understand that AI won’t replace programmers.

[4:42] Get to the basics first, and then you can move on: Master core programming skills and fundamentals before relying too heavily on AI or advanced tools.

[8:19] The impact of AI on experienced developers.

[15:44] Highlighting the role of programmers in managing low-level details that managers and customers don’t want to think about.

[18:43] Programmers as language learners.

[27:19] The state of Agile methodologies.

[29:33] The original Agile goal of making small teams work efficiently together, which remains a crucial challenge.

[35:37] Discussing the limitations of university computer science programs and the potential of trade school or apprenticeship models.

[36:07] What’s next for Uncle Bob?

Mentioned in this Episode:

Clear Measure Way

Architect Forum

Software Engineer Forum

Programming with Palermo — New Video Podcast! Email us at programming@palermo.net.

Clear Measure, Inc. (Sponsor)

Clean Agile: Back to Basics 

Clean Code: A Handbook of Agile Software Craftsmanship

We, Programmers: A Chronicle of Coders from Ada to AI

“Uncle Bob Martin: Clean Code and How to Do Software Well - Episode 283”

Functional Design: Principles, Patterns, and Practices

UncleBob on GitHub

The Clean Code Blog

Agile Principles, Patterns, Practices

Clean Coders

Want to Learn More?

Visit AzureDevOps.Show for show notes and additional episodes.

For a while now, AI and tech headlines have been dominated by layoffs and market shifts. But what if a crucial, yet often overlooked, factor was at play? I'm experimenting with a new narrative style in this video to break down Section 174 of the US tax code. Discover how changes to this R&D deduction policy, from its inception in 1954 to the impactful 2017 Tax Cuts and Jobs Act, quietly impacted everything from startup funding to the massive tech layoffs we've seen. We'll also cover the breaking news of its recent reversal on July 4th, 2025, and what that means for the future of innovation in the US.

#AILayoffs #TaxCode #Section174 #RDTaxCredit #TechLayoffs