Problem is that HAM radio also has social filters you broadcast to everyone and you don’t know who is listening. Encrypted communication is not allowed in HAM.

You are not supposed to use it for „communication” as in Facebook. You are supposed to use spectrum to test your gear and keep transmissions short to leave space for others.

I was in local HAM club and passed the exam for license but never got license to transmit mostly because you are not supposed to chat frivolously over the radio.

I do agree.

But at the same time there is a quote by Stanisław Lem...

"Until I used the Internet, I didn't know there were so many idiots in the world"

I guess that’s how you get to be in Forbes 30 under 30 right?

I was under the impression you just paid for that

Joke is more about the fact that quite a lot of 30 under 30 end up serving prison time - mostly because they think they are smarter than everyone and that they can BS and get away with such things like one from TFA.

I hate awesome lists they are garbage.

This resource also seems like waste of time so not much better.

There is still a lot of engineering to be done with LLMs. Maybe not exactly writing code but I think a lot of optimization problems will be there no matter what.

Some people treat toilet as magic hole where they throw stuff in flush and think it is fine.

If you throw garbage in you will at some point have problems.

We are in stage where people think it is fine to drop everything into LLM but then they will see the bill for usage and might be surprised that they burned money and the result was not exactly what they expected.

Yep. I hate to predict the future but I’m betting on small, open models, used as tools here and there. Which is great, you can get 90% of the speed up with 5-10% of the cost once you account for the full costs in both time and money.

The economics and security model on full agents running in loops all day may come home to roost faster than expertise rot.

Market values bulldozers for bulldozing jobs. No one is going to use bulldozers to mow a lawn.

If Bob is going to spend $500 in tokens for something I can do for $50.

I think Bob is not going to stay long in lawn mowing market driving a bulldozer.

If I am writing backend code I am mostly in a single IDE window moving tabs with code files to other screens is working but is inconvenient.

When I work on frontend I much rather have preview on second screen and most likely reference next to it.

When writing documentation or requirements I cannot imagine working on a single screen as essentially I am integrating multiple data sources into one, like I need to see how app looks now and before release, what changed and still have my working space for draft.

Switching windows to quickly look up documentation is fine but when creating requirements having time to understand what needs to be in which place how it has to evolve I need to have it right there so that my imagination doesn’t runaway.

I would argue that „doing shit” should be done by dummy automations. AI should be used to help build that automations or step in when dummy automation breaks.

For now too many people will use AI for stuff that deterministic stupid code would be much more efficient.

F16 pilot on radio with airliner.

Doing barrel roll, twist and speed up - radio to airliner „see buddy can you do that?”

Airliner „wait a moment” - some time passes nothing happens - airliner „hey buddy you seen that?” - f16 „what? Nothing happened” - airliner „I went to toilet on the back, took dump, made myself a coffee and strolled back to cockpit”.

I would definitely fight against calling anything I work on „digital escort”.

Yeah, it’s not a great name. But it originates from the government. When somebody without a security clearance needs to go to a secure area, they must be escorted by somebody.

When the blog post mentioned Hegseth and “digital escort” in the same sentence, I was surprised to learn it wasn’t about his OnlyFans habit at his work desktop.