Seems like it was an insanely profitable product, but a risky business.

Material is not just about quality, but rarity or uniqueness. For example, japanese denim can get very expensive in part because it's very low volume. For dress pants, it might be a particularly interesting fabric.

A lot of more expensive pants also have interesting designs or proportions that are very unique or hard to find elsewhere. There is a lot of cool stuff you can get for under $500 USD though, that is still pretty expensive.

Some examples around that price range:

- https://stoffa.co/collections/trousers/products/lavender-woo...

- https://www.lemaire.fr/products/twisted-belted-pants-bl760-d...

- https://www.blueowl.us/collections/pure-blue-japan/products/...

Coding IC work takes a lot of focus and context that someone who is operating at the company-level should not really be in sole possession of.

To me, the whole point of these positions is to take the hit on random bullshit, planning, people management, etc and give your ICs space to do the kind of work he is taking on.

That doesn't mean you have no technical context or involvement in the development process, but it does mean you should probably be at least one step removed from it.

We were not built with the capacity to handle the sheer amount of stimulation the modern world has. You have to put in a lot of effort to not succumb to natural desires that would have been adaptive behaviours until recent history.

E: ok watched an interview the author gave and the answer was very boring. He requested a demotion because he moved from management back to IC.

Maybe more about my unfamiliarity with the Korean address format than anything else tbh.

Some things about Naver I kind of miss from Apple/Google maps, but international software in general feels much more user friendly and better UX than Korean software.

I wouldn't expect things to calm down for a while, even if real-life results are worse. You can make excuses for underperformance of these things for a very long time, especially if the CEO or other executives are invested.

> The real problem we should be discussing is, how do we convince students and apprentices to abstain from AI until they learn the ropes for real

I hate to say it but that's never going to happen :/

This is the whole point. The marginal dev will go to the path of least resistance, which is to skip the understanding and churn out a bunch of code. That is why it's a problem.

You are effectively saying "just be a good dev, there's literally nothing about AI which is stopping you from being a good dev" which is completely correct and also missing the point.

The marginal developer is not going to put in the effort to wield AI in a skillful way. They're going to slop their way through. It is a concern for widespread AI coding, even if it's not a concern for you or your skill peers in particular.

You have to remember this is someone who is almost certainly completely non-technical and purely vibe coding. He won't know what things like code freeze, rollbacks, production database, etc actually mean in real engineering terms and he is putting his full trust in the LLM.