Ben

flutter | coding | learning | pokemon

[Dmitrii Kovanikov @ChShersh]

I miss the times when people used to create tech web pages just for one niche yet useful topic

https://t.co/USp8q0eCAu

[Flightradar24 @flightradar24]

Some celebrate with a party, some celebrate with fireworks, this pilot is celebrating America’s semiquincentennial with a very special flight. #America250

[Ben @begin4ga1n]

@lildeimos @ASalvadorini @spydon @FlutterDev @FlutterComm Thanks for making this 🙏

[Ben @begin4ga1n]

Software job interview is too broken 🥲

[Michael Bushe 💙🧘‍♂️🌎⚾ @michaelbushe]

If you aren't good enough to actual make things that people use, then I guess that's a fallback, an expensive (time) and useless fallback.

Why don't software developers interview like every other profession?
Do you give your Carpenters a dollhouse project to take home?
After you ask your lawyer a few legal test trivia how hard does he laugh as he asks you for a retainer?
I asked a mechanical engineering friend if he asks such engineering questions during interviews. He scoffed at the rudeness and said, "No, The professionals that's supposed to be able to figure it out. We're trying to get to know the person and see if they're a good fit and if they'll work hard."

[Ben @begin4ga1n]

🥲🥲🥲🥲

[Owen Carey @owenthcarey]

Practicing LeetCode at 32 years old.

[Lukas Klingsbo 💙🔥 @spydon]

Do you want to make sure that a Flutter upgrade doesn't break your project?
Add a script so that your tests run in the Flutter Customer Test Registry! I just did so for Flame.

These tests run with every commit to Flutter to verify that no breaking changes have been introduced.

[Ben @begin4ga1n]

@puf Is there a pathway to avoid such dystopian future? I would give it a read if the author attempted to explore at least some solution and not just add more fuel to the fire because I think for most sensible software developers, the doom is quite clear.

[Ben @begin4ga1n]

@ivannahere @GeminiApp @GoogleDeepMind @googledevs This is so dystopian 😭

[Ben @begin4ga1n]

@pavanpodila @RydMike This is really cool! Looking forward to it!

[Palantir @PalantirTech]

Our thoughts on the importance of AI sovereignty.

1. Your AI sovereignty dictates your institution’s future. Sovereignty is the precondition for choice. Relinquishing sovereignty transfers the future choices of your institution to others, who are likely to exploit it for their gain and your loss.

2. Data retention is your treasure. Transfer it at your own peril. Your ability to win is dictated by your ability to recognize and use your unique edges, and you keep winning by compounding the underlying data to generate new insights. Transferring that data hands over access to your pre-existing winning plays and yields the means of production for new ones.

3. Tokenmaxxing hijacks your value orientation and decreases your institutional fortitude and intelligence. The pursuit of high token usage incentivizes disposable scripts over robust software — with the addictive feeling of false progress. There is a reason why those selling tokens refuse to charge based on value.

4. Controlling your weights is controlling your fate. Weights are the distilled form of hard-won, accumulated institutional knowledge. If you let others control your weights, you are allowing them to migrate the alpha of your business to theirs.

5. There is no contradiction between sovereignty and alpha. The architecture that maximally preserves sovereignty is one that enables institutions to own their tribal knowledge, and to compound it as alpha.

6. Politicizing the technical issues involving sovereignty is what your adversary wants. Techno-politicization is the wellspring of false sovereignty. Techno-politicization drives decisions that seem to reduce dependency, but ultimately limit agency — especially on the battlefield in the West.

7. Real expertise is existential. Allowing politics or favoritism to determine your technical decisions rewards whoever is best at politics, not whoever is right. Listen to those closest to the problems, not those speaking most compellingly about them.

8. Learn from institutions that are winning or that have consistently delivered. Institutions facing existential threats do not have the luxury of making technical decisions based on political preferences.

9. Only listen to institutions, countries, and people who have a proven record of being right. A track record of correctness is the best and only signal for future correctness. Judging something as right or wrong based on who you like is exceedingly misguided.

[Ben @begin4ga1n]

@ClementDelangue @Stanford 🥲 poor people crying in unpaid bills

[Oh, Shenandoah @longhunter09]

Woodstock, VA downtown

[Ben @begin4ga1n]

Loop engineering and Flutter 👀

[Ben @begin4ga1n]

@SYSTEM964278 @Google @NotebookLM It’s not real right someone else can see it 😰

[Ben @begin4ga1n]

@valigo 🤯

[Ben @begin4ga1n]

I remember I read another post about GenAI only making simple apps… well, not anymore 🥲

[Maxime Chevalier @Love2Code]

I had Claude vibe code a parser for textual LLVM IR in Rust, with the goal of parsing the output of compiling Doom with Clang (~112K lines long). It completed the task in ~20 minutes 👀

[Flutter @FlutterDev]

Deciding between A2UI and MCP Apps for your agentic interfaces? You don't have to choose 💫

This guide breaks down 3 architectural patterns for combining the best of declarative and custom UIs, including how A2UI and MCP Apps can seamlessly interact with each other.

[Ben @begin4ga1n]

@seif_ib I’m curious if these vibe coded apps got users 🤔 like would App Store demote the apps simply because it’s vibe coded?

[Ben @begin4ga1n]

@ThomasBurkhartB @elonmusk @nikitabier What’s your other account?

[Emma Twersky @twerske]

Please fill out the annual survey!
https://t.co/Hb7NwKiBSf

Yes we have some spicy questions.
TLDR no, there are no plans to transfer Flutter ownership.

We are simply asking to get a pulse check on governance, and this will be a new recurring question in every future survey.

Our goal is only to assess how successfully we are expanding governance to target platforms and meeting our goals to make Flutter possible everywhere. nonGoogle maintainers have always been a part of that strategy, but that doesn't mean the framework is going anywhere :)