Bryant Ung

...

[Bryant Ung @UngBryant]

@systemdesignone Classification

[Bryant Ung @UngBryant]

@DanielSmidstrup Opencode?

[Bryant Ung @UngBryant]

@thatguybg @grok is this real?

[greg @greg16676935420]

This guy is ChatGPT’s worst nightmare 🤣

[Bryant Ung @UngBryant]

@thsottiaux The name ChatGPT? Even you call it codex…

[Bryant Ung @UngBryant]

@JinjingLiang In the world of engineering it’s about trade offs. the large code bases that I’ve worked in were not that well organized or structured, it’s just that there was someone who had a deep understanding and context of how it all worked. AI can get it wrong sometimes.

[Bryant Ung @UngBryant]

@JinjingLiang Lots of emotions go into a layoff. Hope your friend is doing ok

[Bryant Ung @UngBryant]

@axhiii88547 Eclipse

[Bryant Ung @UngBryant]

@thsottiaux Yeah, I heard this company named Anthropic is still using Opus

[Orca ADE @orca_build]

Orca now supports GitHub stacked pull requests.

The whole stack lives in the sidebar — which PR you're on, what's under it, what it's based on. When everything below is ready, one button merges all of it into main, in order.

Three PRs. One merge. Available on v1.4.180+

[Bryant Ung @UngBryant]

@ycombinator @zach_yadegari @grok does y combinator say this?

[Elon Musk @elonmusk]

🇪🇸 🇪🇸 Congratulations Spain!! 🇪🇸 🇪🇸

[Bryant Ung @UngBryant]

@realAkashAnand VIDEO SKILLS

[OpenAI @OpenAI]

GPT-5.6 Sol, along with Terra and Luna, will launch publicly this Thursday.

We’re expanding preview access globally now.

[Andrej Karpathy @karpathy]

This is the the quote I've been citing a lot recently.

[Andrej Karpathy @karpathy]

This works really well btw, at the end of your query ask your LLM to "structure your response as HTML", then view the generated file in your browser. I've also had some success asking the LLM to present its output as slideshows, etc.

More generally, imo audio is the human-preferred input to AIs but vision (images/animations/video) is the preferred output from them. Around a ~third of our brains are a massively parallel processor dedicated to vision, it is the 10-lane superhighway of information into brain. As AI improves, I think we'll see a progression that takes advantage:

1) raw text (hard/effortful to read)
2) markdown (bold, italic, headings, tables, a bit easier on the eyes) <-- current default
3) HTML (still procedural with underlying code, but a lot more flexibility on the graphics, layout, even interactivity) <-- early but forming new good default
...4,5,6,...
n) interactive neural videos/simulations

Imo the extrapolation (though the technology doesn't exist just yet) ends in some kind of interactive videos generated directly by a diffusion neural net. Many open questions as to how exact/procedural "Software 1.0" artifacts (e.g. interactive simulations) may be woven together with neural artifacts (diffusion grids), but generally something in the direction of the recently viral https://t.co/z21CP5iQfu

There are also improvements necessary and pending at the input. Audio nor text nor video alone are not enough, e.g. I feel a need to point/gesture to things on the screen, similar to all the things you would do with a person physically next to you and your computer screen.

TLDR The input/output mind meld between humans and AIs is ongoing and there is a lot of work to do and significant progress to be made, way before jumping all the way into neuralink-esque BCIs and all that. For what's worth exploring at the current stage, hot tip try ask for HTML.

[Bryant Ung @UngBryant]

@felixrieseberg Congrats Felix!

[Aditya @_adityaa21]

2025:
- 90% of the code is written by AI.
- Developers are celebrating.
- “Finally, no more boilerplate 😌”
- Productivity charts going up.
- Managers tweeting about 10x efficiency.

2026:
- 100% of the code is written by AI.
- Hackathons are just prompts.
- PRs are auto-approved.
- Standups sound like:
“AI generated it, looks fine to me.”
- Tech Twitter declares: Software engineering is dead.

2027:
Reality hits.

- 10% of the code is written by AI.
- 90% of the time is spent understanding, debugging, rewriting, and apologizing for AI-written code.

Senior SWEs are now paid 10x.
Not to write code, But :
- to figure out why it works
– explain how it broke
– clean the “clever” abstractions
– delete 5,000 lines and replace it with 50
– tell management “yes, this is unmaintainable” in polite English

Junior devs can generate code.
Mid-level devs can ship features.
Senior devs can save companies from their own AI optimism.

AI didn’t kill software engineers.
It just made judgement, architecture, debugging, ownership, and taste insanely valuable.

Writing code was never the hard part.
Understanding code always was.

[artificial intelligence, generative ai, software engineering, clean code, debugging, system design, scalability, tech layoffs, developer productivity, startup culture, big tech, senior engineers, code quality, refactoring, tech twitter, future of work, programming reality]

[Bryant Ung @UngBryant]

@elonmusk Will it still be sustainable?

[Bryant Ung @UngBryant]

@SYNESTHEIZURE @grok is this AI generated?