๐๐ฆ๐จ๐ฅ๐ญ๐๐ค ๐๐จ๐ โ We are looking for a ๐๐ก๐๐ซ๐๐๐ญ๐๐ซ๐ข๐ณ๐๐ญ๐ข๐จ๐ง ๐๐ง๐ ๐๐๐ฅ๐ข๐๐๐ข๐ฅ๐ข๐ญ๐ฒ ๐๐ง๐ ๐ข๐ง๐๐๐ซ.
You will do electrical characterization and reliability assessment of our ALD-based dielectric stacks and CNF-MIM capacitors.
smoltek.com/smoltek-semi/aboโฆ
Philip Lessner retweeted
Every time we've made it easier to write software, we've ended up writing exponentially more of it.
When high-level languages replaced assembly, programmers didn't write less code - they wrote orders of magnitude more, tackling problems that would have been economically impossible before. When frameworks abstracted away the plumbing, we didn't reduce our output - we built more ambitious applications. When cloud platforms eliminated infrastructure management, we didn't scale back - we spun up services for use cases that never would have justified a server room.
@levie recently articulated why this pattern is about to repeat itself at a scale we haven't seen before, using Jevons Paradox as the frame. The argument resonates because it's playing out in real-time in our developer tools. The initial question everyone asks is "will this replace developers?" but just watch what actually happens. Teams that adopt these tools don't always shrink their engineering headcount - they expand their product surface area. The three-person startup that could only maintain one product now maintains four. The enterprise team that could only experiment with two approaches now tries seven.
The constraint being removed isn't competence but it's the activation energy required to start something new. Think about that internal tool you've been putting off because "it would take someone two weeks and we can't spare anyone"? Now it takes three hours. That refactoring you've been deferring because the risk/reward math didn't work? The math just changed.
This matters because software engineers are uniquely positioned to understand what's coming. We've seen this movie before, just in smaller domains. Every abstraction layer - from assembly to C to Python to frameworks to low-code - followed the same pattern. Each one was supposed to mean we'd need fewer developers. Each one instead enabled us to build more software.
Here's the part that deserves more attention imo: the barrier being lowered isn't just about writing code faster. It's about the types of problems that become economically viable to solve with software. Think about all the internal tools that don't exist at your company. Not because no one thought of them, but because the ROI calculation never cleared the bar. The custom dashboard that would make one team 10% more efficient but would take a week to build. The data pipeline that would unlock insights but requires specialized knowledge. The integration that would smooth a workflow but touches three different systems.
These aren't failing the cost-benefit analysis because the benefit is low - they're failing because the cost is high. Lower that cost by "10x", and suddenly you have an explosion of viable projects. This is exactly what's happening with AI-assisted development, and it's going to be more dramatic than previous transitions because we're making previously "impossible" work possible.
The second-order effects get really interesting when you consider that every new tool creates demand for more tools. When we made it easier to build web applications, we didn't just get more web applications - we got an entire ecosystem of monitoring tools, deployment platforms, debugging tools, and testing frameworks. Each of these spawned their own ecosystems. The compounding effect is nonlinear.
Now apply this logic to every domain where we're lowering the barrier to entry. Every new capability unlocked creates demand for supporting capabilities. Every workflow that becomes tractable creates demand for adjacent workflows. The surface area of what's economically viable expands in all directions.
For engineers specifically, this changes the calculus of what we choose to work on. Right now, we're trained to be incredibly selective about what we build because our time is the scarce resource. But when the cost of building drops dramatically, the limiting factor becomes imagination, "taste" and judgment, not implementation capacity. The skill shifts from "what can I build given my constraints?" to "what should we build given that constraints have in some ways been evaporated?"
The meta-point here is that we keep making the same prediction error. Every time we make something more efficient, we predict it will mean less of that thing. But efficiency improvements don't reduce demand - they reveal latent demand that was previously uneconomic to address. Coal. Computing. Cloud infrastructure. And now, knowledge work.
The pattern is so consistent that the burden of proof should shift. Instead of asking "will AI agents reduce the need for human knowledge workers?" we should be asking "what orders of magnitude increase in knowledge work output are we about to see?"
For software engineers it's the same transition we've navigated successfully several times already. The developers who thrived weren't the ones who resisted higher-level abstractions; they were the ones who used those abstractions to build more ambitious systems. The same logic applies now, just at a larger scale.
The real question is whether we're prepared for a world where the bottleneck shifts from "can we build this?" to "should we build this?" That's a fundamentally different problem space, and it requires fundamentally different skills.
We're about to find out what happens when the cost of knowledge work drops by an order of magnitude. History suggests we (perhaps) won't do less work - we'll discover we've been massively under-investing in knowledge work because it was too expensive to do all the things that were actually worth doing.
The paradox isn't that efficiency creates abundance. The paradox is that we keep being surprised by it.
Philip Lessner retweeted
Don't forget! Join YAGEO Group along with DigiKey for our upcoming technical seminar, where we're dedicated to simplifying the process of choosing inductors. Secure your spot today โ REGISTER NOW! hubs.la/Q02219TH0
Philip Lessner retweeted
โOne good test is worth a thousand expert opinions.โ
โ Wernher von Braun
Philip Lessner retweeted
Electronic Specifier Insights Podcast โ Innovations in passive components for power densification. Out this Friday! ๐
We spoke to Peter A. Blaise, Senior Director Application Engineering at KEMET.
๐spoti.fi/3iEhZZ5
#podcast #insights #episode #newepisode #tech
Philip Lessner retweeted
Educate yourself about things. Study hard what interests you the most. Don't worry about what others think of you, that's none of your business. Train your mind to think, doubt, and question. That's how you grow. ๐ง
Philip Lessner retweeted
It's true that good, simple tools really need no replacement.
Replying to @hackaday
I use MS Paint all the time, as well as Notepad. They do exactly what I need without adding crazy formatting, requiring a subscription or contacting a dozen servers to steal my data. We have lost the concept of simple, dependable offline performance in computing.
Philip Lessner retweeted
Sources say @elonmusk offered to buy the FBIโbut Mark Zuckerberg refused to sell.
Philip Lessner retweeted
โWe've arranged a society based on science and technology, in which nobody understands anything about science technology. And this combustible mixture of ignorance and power, sooner or later, is going to blow up in our faces.โ
- Carl Sagan
Philip Lessner retweeted
'The year 2000 was essentially the point at which it became cheaper to collect information than to understand it.' -- Freeman Dyson
Philip Lessner retweeted
Read the latest in our series of DESIGN TIPS from ADI: Bypass Capacitor and Coupling Capacitor: Stabilising Voltage the Right Way @New_Electronics @ADI_News #Electronics
newelectronics.co.uk/contentโฆ
Philip Lessner retweeted
Whether it is @lyft, @Uber, or @netflix --eventually inability to find new ways to keep growing leads to embracing the modern internet's first original (and easiest) sin -- advertising. It doesn't have to be effective, consumers can't do shit about it, & of course, some easy $$$
Lyft plans to offer more ads inside cars, on its app and at bike-share stations.
"A portion of revenue from the display and tablet ads will go to Lyft drivers, though the company declined to say how much."
wsj.com/articles/lyft-createโฆ via @PatrickCoffee
Philip Lessner retweeted
the combo big bank/coffee shop has FREE coffee w/ every new checking account + credit card signup โ checkmate, socialists! ๐ฅฐ
Philip Lessner retweeted
KEMET Introduces 1kV Automotive Grade Common Mode Choke zpr.io/WGGgrpnPYbVM
Philip Lessner retweeted
The @KEMETCapacitors KC-LINKโข with KONNEKTโข Technology brings high efficiency to power applications. It features low ESR, high ripple current, wide bandgap (WGB), EV/HEV and wireless charging and much more... Check it out: https://teapawt.org/t.co/Kp7I3Fpo4W
Philip Lessner retweeted
KEMET Extends Lifetime of AO-CAP Aluminum Polymer SMD Chip Capacitors zpr.io/u4MFV6QQKezJ
Philip Lessner retweeted
Mouser offers a comprehensive portfolio of the newest YAGEO Group solutions, including resistors, capacitors, inductors, transformers, relays, antennas, wireless components, & circuit protection components.
Adding new products every day: mou.sr/yageo-TW @YageoCorp
































