Exactly. Posts that say "I got great results" are just advertisements. Tell me what you're doing that's working good for you. What is your workflow, tooling, what kind of projects have you made.
>Over the past year, I’ve been actively using Claude Code for development. Many people believed AI could already assist with programming—seemingly replacing programmers—but I never felt it brought any revolutionary change to the way I work.
Funny, because just last month, HN was drowning in blog posts saying Claude Code is what enables them to step away from the desk, is definitely going to replace programmers, and lets people code "all through chatting on [their] phone" (being able to code from your phone while sitting on the bus seems to be the magic threshold that makes all the datacenters worth it).
>only to have it completely obsoleted a few years later
Almost nothing goes obsolete in software; it just becomes unpopular. You can still write every website you see on the Internet with just jQuery. There are perfectly functional HTTP frameworks for Cobol.
> Look at who’s about to get angry about OpenClaw-style automation: LinkedIn, Facebook, anyone with a walled garden and a careful API strategy.
Browser automation tools have existed for a very long time. Openclaw is not much different in this regard than asking an LLM to generate you a playwright script. Yes, it makes it easier to automate arbitrary tasks, but it's not like it's some sort of breakthrough that completely destroys walled gardens.
Microsoft has consistently proven over the last five years that they have zero ability to execute. It's an astounding failure after failure to do anything right.
It was so ridiculously shortsighted of them to decide as a strategy to underpay all their employees compared to the industry standard, especially considering their ambitions are still fairly unbounded (meaning it's not like they said everything we do will be easier than Google or Meta so we don't need to compete for the same pool of talent).
But maybe such a decision was inevitable in their culture. And now it's very difficult to correct.
>A master like antirez had to wrap his head around concepts alien to the human mind. Bits, bytes, arrays, memory layout, processors, compilers, interfaces, abstractions, constraints, types, concurrency do not exist in the savannas that forged brains.
You still need to know these things if you're doing anything more complicated than making some CRUD dashboard. LLMs assist with some code generation, and assist with some knowledge lookup. That's pretty much it.
What seems to be the case is that you need to know everything you needed to know before, and* become good at leveraging AI tooling to make you go faster.
*Even this is optional. There is absolutely nothing stopping anyone from just ignoring everything about AI and keep developing software like pre-2022. The efficiency difference isn't even significance in the grand scheme of things. It's not like people had reams of perfect software specs just lying around waiting to be implemented. That's just not how people develop software; usually the spec emerges while you're writing the program.
As a Clojure developer I have the opposite experience. The more they ignore my open source work, the more they never call up any of my references, the more they give me useless test jobs and assignments unrelated to the actual work, the more it's a signal of a place with poor engineering culture and generally also not that great salaries.
However the places that actually do read my open source work, do contact my references, and where the interview has had no tech assignments of any kind other than a simple discussion about a variety of topics, perhaps just going over some of my OSS projects, the higher the salary has been.
This is in Northern Europe though, your mileage may vary.
To be fair, "you're fired!" doesn't happen in the US tech industry either. Even for performance-based firings, the employee almost always gets a few months of salary and garden leave in exchange for a release of claims. One of the positive effects of America being an overly litigious society. Unemployment insurance also kicks in.
2. Central banks rotating into gold to de-risk from USD combined with their usual slow bureaucratic processes. By the time they've decided that gold needs to be bought, the price has already run up by 50% and it's no longer a good idea to buy, but they still need to execute on their decisions anyway.
The USD isn't going anywhere for the simple reason that the USA can simply counterfeit any non-USD currency and there's nothing the issuer can do about it, whereas if anyone tries to counterfeit USD, they should expect a nice little missile to land inside their room no matter where they are in the world. "Reserve currency" status is entirely based on how effective the issuing entity is at taking care of counterfeiting.
The scale doesn't seem to be large enough to warrant military action. It seems NK had mostly used it as pocket money for its embassy staff and has now stopped.
"The U.S. Secret Service estimates that North Korea has produced $45 million in superdollars since 1989. [...] Since 2004, the United States has frequently called for pressure against North Korea in an attempt to end the alleged distribution of supernotes. It has investigated the Bank of China, Banco Delta Asia, and Seng Heng Bank. The U.S. eventually prohibited Americans from banking with Banco Delta Asia. [...] The United States has threatened North Korea with sanctions over its alleged involvement with the supernotes, though it said those sanctions would be a separate issue from the nuclear sanctions."
Exactly. Airfoil is an optimization. There is a common misconception that planes wouldn't get off the ground if you didn't have airfoil. No, most of the lift (depends on the plane but in the ballpark of 80-90%) comes from the overall shape of the wings. ~20% is from leading edge airfoil deflection dynamics.
And if, say, airfoil was never discovered, we'd probably design the whole wing slightly differently to compensate for it, so the actual difference wouldn't even be 20%.
Airfoil is about as important as winglets, and planes fly without winglets just fine. But nobody points to winglets and says that's the crucial bit that makes the whole thing work.
Two ratios dominate aircraft design. Lift/Drag, Thrust/Weight
To get off the ground Lift > Weight, Thrust > Drag, or to simplify to stay aloft Lift = Weight, Thrust = Drag
Bigger engines weigh more.
To get off the ground you need an engine powerful enough to overcome the drag necessary to generate enough lift.
That is what enabled powered flight especially at the beginning. Wing design with a good enough lift to drag ratio and engine+propeller design that had a good enough thrust to drag ratio to come together for more lift than the aircraft weighed.
I was obsessed with fighter jets in my adolescence. My favorite plane was the F-15 Eagle; its thrust:weight ratio was greater than 1 -- meaning it could take off, point its nose straight up to vertical, and keep accelerating past mach 1. Amazing.
>Over the past year, I’ve been actively using Claude Code for development. Many people believed AI could already assist with programming—seemingly replacing programmers—but I never felt it brought any revolutionary change to the way I work.
Funny, because just last month, HN was drowning in blog posts saying Claude Code is what enables them to step away from the desk, is definitely going to replace programmers, and lets people code "all through chatting on [their] phone" (being able to code from your phone while sitting on the bus seems to be the magic threshold that makes all the datacenters worth it).
reply