Agents can use Google. They can also see all the same signals humans do to judge quality. Maybe there's a need for a specialized directory, but does it need a spec or an acronym? No.
11,490 karma · joined December 18, 2009
@iandanforth
Source available - https://www.openhumans.org/member/iandanforth/
meet.hn/city/us-Pittsburgh
Agents can use Google. They can also see all the same signals humans do to judge quality. Maybe there's a need for a specialized directory, but does it need a spec or an acronym? No.
The predicate is "given how we practice medicine and the limits of humans ability to interpret the imaging modalities we have."
The more specific predicate is "for my specialty would this replace or prove superior to the tools that I have?"
Both of these are totally reasonable, however the history of medicine, and science in general, is that creating new ways to look at things has a tendency to reveal information that we never knew we needed.
For example, for years I thought of blood sugar as something that was either in a good or bad range. Then I tried a continuous blood sugar monitor. The full picture of the body's response to specific foods that I ate was eye opening. There's so much more to learn when you get a higher resolution (temporal in that case) view into your body.
Another wonderfully hopeful example is the retinal imaging ML work done by google. A completely non-invasive image of the retina for diabetic issues, that also happened to be able to predict things like age, sex, smoking status, previous cardiac events and more! Just take high-res pictures of things! The body is interconnected in ways that you can infer from one system so much about others.
So while I don't think anything the Dr. said is "wrong", I think it represents a very common blinkered mindset of pragmatic practitioners who need to deliver reliable performance daily.
The selfish / corrupt thing to do is to do this after you've fleeced the public.
This sounds exactly like the opening line from an apocalyptic sci-fi film.
I learnt a lot about the domain and how to effectively write programs for it: PCI compliance, double-entry ledgers, escrows, reconciliation, payment lifecycles, bank transfer idempotency, etc.
It was, then, obvious that I should focus my career on becoming an expert on that domain to stand out as a professional and differentiate myself in a field that showed signs of an increasing need for domain specialists."
"This organization is controlled by Trump loyalists. They are not scientists. You do not owe them respect. Speak over them. Let no manipulation go unchallenged or derided."
"We're firing a bunch of people because we think we don't need them anymore due to AI and we'll make more money without them."
There are times when businesses must fire people to stay afloat and it's a business that objectively needs to exist. This isn't one of them, so don't waste everyone's time with your BS, please.
This is a personal thought experiment so think it through for yourself. What would the consequence be if the agents really were better than you and you acknowledged that?
The major premise of "It's a trap!" is that it matters if you lose your coding skill. (I'll gloss over general critical thinking and stick with coding for now) However in the world where on any given task it would be done to a higher level of quality and faster if you gave it to the agent, then what are you doing trying to do it yourself? There's plenty of room for that kind of thinking in hobbies, but in the professional world?
Maybe you can add some value in code reviews, but you may also be better off never reading the code at all. Maybe the how of coding stops mattering and the what of products needs to be your top concern.
I can tell you that the agents that I use today are much better coders than I am in the language we're using. I don't write it at all. I couldn't fizzbuzz in it. But with a small team we are building useful internal tools and features at a breakneck pace. I certainly feel the same feelings of getting dumber and losing my coding chops, but I have to step back and say, could what we've built have been built in 5x the time without agents? And the answer is probably no.
The thing I'm mastering now is conjuring software with agents. What lets them rip, what slows them down, where they are today and where they will likely be tomorrow.
I can tell you that you should re-invest in small, modular systems, because agents can build modules and greenfield projects instantly. I can tell you that there is a point at which agents fall over completely even on mid-sized projects, but that that point is receding with each new generation of model, and that Codex 5.4 XHigh Fast set to 500K context window is a beast. (5.5 has yet to win me over)
I can tell you that pushing direct to main is viable, that PRs slow down fully agentic teams, and if your agents have sufficient permissions they can fix things fast enough to be let loose even knowing they may delete your service. I wouldn't do it with your main product yet (unless you're starting your startup today) and I wouldn't try it with a large legacy project. But maybe that rewrite you've always wanted to do is here and just a prompt away.
Now, the sane among you will note that agents are not better today, that they might not ever be, and either way you should never trust a computer to make a decision because it can't suffer the consequences of its actions. Or more down to earth, there are some things that are too important to yolo.
But I will argue that a huge swath of us work in domains where if you're willing to challenge some of the basic assumptions of software development (you should understand the code, it should be maintainable by humans, it should be built to last) then you'll be able to provide very useful software much more quickly than you would otherwise be able to do. Save the skill for your hobbies, and build things people want.