Franziska Hinkelmann, PhD

8.9K posts

Franziska Hinkelmann, PhD banner
Franziska Hinkelmann, PhD

Franziska Hinkelmann, PhD

@fhinkel

Gemini CLI and agents @Google. @nodejs TSC member. Former Chrome @v8js.

North Carolina Katılım Aralık 2008
3K Takip Edilen18.2K Takipçiler
Franziska Hinkelmann, PhD retweetledi
Firebase
Firebase@Firebase·
Firebase now integrates with @GoogleAIStudio, accelerating your path from prompt to production 💫 With a single prompt, you can build full-stack apps connected to Firestore for secure storage and Firebase Authentication for user identity.
English
21
48
345
102.8K
Nikita Bier
Nikita Bier@nikitabier·
The financial incentive to spam on X will decline enormously over the next 30 days and soon be negative.
English
4.8K
2.3K
39.1K
3.1M
Franziska Hinkelmann, PhD retweetledi
Bryan Morgan
Bryan Morgan@bdmorgan·
Gemini CLI users - please see this important announcement here: github.com/google-gemini/… Quick summary: ( 1 ) Users using the product for free ("Code Assist for Individuals") will lose access to Pro models on March 25. ( 2 ) We will be increasingly prioritizing traffic based on subscription type and account standing.
English
8
7
55
13.4K
Hank Yeomans
Hank Yeomans@HankYeomans·
I miss the grit and struggle. Now it feels like a struggle to have grit and struggle. People telling us “why bother learning anything deep just do x” There is a certain satisfaction of having that deep connection with something even though it’s easily handled. You know that if the systems failed you could pick it up and move forward. Like sailors. The ship drives itself, but if it all failed they could watch the stars. I feel like we’re pushed to not want both. Theres things in my brain I’ll probably never forget. I feel bad for the people that will miss out on that.
English
1
0
1
61
Franziska Hinkelmann, PhD
Remember Introduction to Algorithms, the actual book, and how much fun it was to get lost in a specific algorithm in pseudo code? You'd sit in the library, debugging code on physical paper, trying to visualize how a Red-Black tree actually balanced itself. There was a certain grit to it. You had to actually understand the complexity because you didn't have a safety net. If your logic was flawed, you didn't pass CS 101 (Informatik I in my hometown). Then Hackerrank and Leetcode showed up with their automatic test cases. No more careful debugging, just hitting Run and hoping for green checkmarks. You weren't studying to understand the soul of the algorithm anymore. You were studying to pass the test cases. If the console stayed green, you were a genius. If it turned red, you tweaked the code until it worked. We traded deep architectural intuition for high-speed pattern recognition. I got a better understanding without the safety net of test cases. Cases that somebody else engineered for me. Now we take it a step further with AI coding tools. How are people actually learning algorithms today? And if they're not learning algorithms, is that a problem?
Franziska Hinkelmann, PhD tweet media
English
6
0
19
1K
Tomasz Ducin
Tomasz Ducin@tomasz_ducin·
@fhinkel "Most devs are using AI agents wrong" too much clickbait recently, disappointed, unfollow.
English
1
0
1
42
Franziska Hinkelmann, PhD
Most devs are using AI agents wrong. You prompt, it breaks your codebase, you spend an hour reverting. We fixed this with Plan Mode in the Gemini CLI. It’s a read-only reasoning loop that maps your entire dependency tree before it even attempts a file write. But the real reason this changes everything isn't just safety. It's the fact that it can now use the /ask_user tool to pause its own logic, verify your intent, and then execute with a 95% first-pass accuracy. geminicli.com/docs/cli/plan-…
English
10
3
41
2.7K
Jay W
Jay W@JayD0ubleu·
@fhinkel Let me guess .. you are using Gemini. This thing is absolutely useless for anything agentic even something like scheduling calendar events doesn't work from Android. Claude on the other hand ? Works every time
English
1
0
1
37
Franziska Hinkelmann, PhD
AI is going to take our jobs! The AI: I've successfully rescheduled your 1-1 with Bob to start at 2:35 PM. The rescheduled meeting: no title, no guest. Guess I'll just meet with myself. Or I should probably file a bug. "AI, file a bug for me..."
Franziska Hinkelmann, PhD tweet media
English
10
1
25
1.6K
Franziska Hinkelmann, PhD
Did NemoClaw just make 90% of current agentic startups redundant?
João Moura@joaomdmoura

Your agent is only as trustworthy as the environment it runs in. So today we launch something new with @NVIDIA. AI agents have gone from prompt-and-response tools to autonomous systems that run for hours, write their own code, build their own tools, and learn as they go. The OpenClaw project earlier this year made this concrete, self-evolving agents that plan complex tasks, generate their own tools, and run continuous workflows. We built CrewAI for exactly this. Long-running multi-agent systems. Persistent memory. A dual-layer architecture where Flows handle deterministic control, and Crews handle reasoning. Developers get precise control over how much autonomy each part of the system gets. But here's what keeps coming up with enterprise teams. When an agent can install packages, write files, and generate its own tools, it can also do things you didn't plan for. Most agents inherit the full permissions of whoever launched them. Security checks are usually built inside the agent — so a self-evolving agent could, in theory, work around its own guardrails. This is the trust gap. The real reason most enterprise agent projects don't make it to production. CrewAI addresses a lot of this at the orchestration layer: guardrails, human-in-the-loop, and hierarchical task scoping. But orchestration alone can't close the full gap. You also need enforcement at the infrastructure level, below the agent, where the agent can't reach. That's why we're working with NVIDIA on NemoClaw. NVIDIA NemoClaw is an open-source stack that simplifies running OpenClaw always-on assistants safely, with a single command. It includes the NVIDIA OpenShell Runtime with three core capabilities: A sandbox for isolated execution — agents operate freely without affecting the host. A policy engine that evaluates every action at the binary, destination, and network level. A privacy router that directs inference to local or external models based on your enterprise policies. The critical design choice: enforcement happens at the infrastructure layer, not inside the agent's code. Even if an agent's logic changes unexpectedly, the runtime blocks anything that violates policy. Agents start with zero permissions. Every escalation requires human approval. Every decision gets logged. CrewAI handles orchestration. NemoClaw handles the secure runtime. Together, organizations can run powerful autonomous agents while maintaining real control over their infrastructure and data. We've powered roughly 2 billion agentic executions over the past year and work with more than 60% of the Fortune 500. NemoClaw's infrastructure layer closes the gap between what these agents can do and what enterprises need to trust them in production.

English
3
1
11
2.2K
Franziska Hinkelmann, PhD
@broady Admittedly, I don't have detailed insights into his org. But I've seen plenty of orgs behind held back by poor leadership.
English
0
0
0
24
cbro
cbro@broady·
@fhinkel Agree! I read more about that ex CTO and what he did in his 4 years and it didn't sound good.
English
1
0
1
30
Franziska Hinkelmann, PhD
Atlassian just announced they're cutting 1,600 jobs. Roughly 10% of their global workforce. And they aren't just downsizing. This is Atlassian admitting that their existing engineering DNA is a liability in an agentic world. They are decapitating their legacy engineering leadership. CTO Rajeev Rajan is out (no comment yet), and in his place, they've split the role between two CTOs. Atlassian described them as next generation AI talent. This isn't a restructure. It's an admission that the old guard can't build what comes next.
English
54
6
106
29.9K
cbro
cbro@broady·
@fhinkel Is there any evidence the layoffs are weighted towards the old guard? If I recall, the CTO was only around for 4 years, so I would not consider him old guard. (I used to work there but have no financial interest in TEAM)
English
1
0
2
181
J.J.
J.J.@JJ_BarSinister·
@fhinkel That's if you believe what Atlassian just did is that sort of admission. There's an equally good chance they have no idea what they're doing. I've used their product.
English
1
0
1
76
Thomas Muders
Thomas Muders@thmuders·
@fhinkel Let’s see how many bugs and issues we will see in Atlassian products soon. Then he will wish he had not fired them.
English
1
0
2
248