@Hiteshdotcom Labs with AI built in is the right shape for learning now. Breaking a real container and working out why teaches system design faster than any diagram
@theo Nightly users are great QA until they become the loudest voice in your feedback. Their bugs are real, but their priorities aren't your typical user's
@GergelyOrosz Hiring managers look up your handle before the interview. Disagree hard with the idea, never with the person, and it actually helps your career
@piyushgarg_dev One real user teaches you what 100 tutorials can't: weird inputs, slow pages, the feature nobody touches. That feedback loop is the actual resume
@theo Cutting a feature power users rely on just to "simplify" is what happens when a team optimizes for dashboards instead of the people using the product
@piyushgarg_dev The real comparison isn't speed per token, it's deciding what's worth building.
Models write the code now, picking the right problem is still the expensive part
Opus 5.5 week made one thing obvious: writing code isn't the scarce skill anymore.
Deciding what to build, writing a spec an agent can't misread, and knowing which tradeoffs matter at scale is the job now.
@theo At this point the ceiling usually isn't the model, it's how clearly you can describe what you actually want built. Spec quality is the new bottleneck
@theo Option 3: Microsoft never really ports the debt and just ships a translation layer good enough that nobody notices. That's what made Apple's switch work, not the porting