Benjamin Gibbs

312 posts

Benjamin Gibbs banner
Benjamin Gibbs

Benjamin Gibbs

@Benjamin_Gibbs

Greenfield projects | Start-up’s | Full Stack | Actors | Micro services | CI/CD | .net & ng | Been part of @IgniteAccel & @Dotforge family

Cheshire 参加日 Mayıs 2008
2.7K フォロー中750 フォロワー
Benjamin Gibbs がリツイート
James Newton-King ♔
Every developer on my team is maintaining CI automation alongside their code. GitHub Actions literacy is becoming a fundamental skill. Building the car (programming) and building the factory (automation + AI pipelines) are equally important. We're all build engineers now.
English
11
3
60
5.5K
Benjamin Gibbs がリツイート
JetBrains
JetBrains@jetbrains·
Agentic AI speeds up code production, but the challenge is execution and control. JetBrains Central is an open system for agentiс development across the SDLC, with governance, observability, and controlled execution. Early access starts in Q2 2026. Learn more!
English
0
17
151
2.7M
Benjamin Gibbs がリツイート
@jason
@jason@Jason·
Here’s the truth: we’ve already reached AGI — we just haven’t implemented it broadly. Millions of jobs are being lost as we speak. Entire careers will be retired. The rich and powerful investors and founders who implement AGI will get bizarrely rich beyond what makes sense. It will break people's brains on both sides. It’s gonna suck for a lot of our friends and family, who aren’t obsessed with their careers, because things are moving so fast they won’t have even left the starting gate by the time the awards are handed out. We’re gonna have to solve for a lot of second- and third-order effects, some of which will suck (job loss) and some of which will be awesome. AI will create free/cheap energy, free education, cheaper and better food, homes that build themselves and medicine that makes you as healthy as a 30-year-old when you’re 100. … change is hard, but humans are the most adaptable species nature has ever created. We can figure it out.
English
908
372
4.1K
592.2K
Benjamin Gibbs がリツイート
David Fowler
David Fowler@davidfowl·
Left to its own devices, these agents really hate abstractions that bias towards slopping the layers together. Having a decent architecture in place before the agent runs rampant on your codebase can be a huge benefit (if you care about code quality).
English
20
19
215
16.1K
Benjamin Gibbs がリツイート
vitrupo
vitrupo@vitrupo·
Eric Schmidt says the 10x advantage is no longer execution. It is defining what counts as success. A programmer writes a spec and an evaluation function, runs it at 7pm, and wakes up to what was invented overnight. The advantage now belongs to whoever can specify the problem precisely. The rest will be automated.
English
153
338
2.8K
391.6K
Benjamin Gibbs がリツイート
Benjamin Gibbs
Benjamin Gibbs@Benjamin_Gibbs·
@James_M_South Yes, I have been experiencing the same issue for the past two months while on a Pro plan, sometimes during my peak hours when I have used it heavily, and at other times when there appears to be very little usage.
English
0
0
0
72
JimBobSquarePants 🇺🇦
JimBobSquarePants 🇺🇦@James_M_South·
Anyone else suddenly hitting GitHub Copilot limits in Visual Studio? I've the Pro account but barely used it and it errors out saying I've used too many tokens.
English
10
0
8
4.6K
Benjamin Gibbs がリツイート
Allen Holub. https://linkedIn.com/in/allenholub
A user story is not a code word for specification or a requirement or any description of work. It is not a ticket. It is not a to-do item. It is not something you can build. The fact that the term has been corrupted by the Jira-slinging ticket-money pseudo-Agile Scrummy culture is a real shame, because it's a valuable concept: A "user story" is literally the user's story. It is a description of a problem, not a solution. It is not a specification. It cannot be estimated. It's the topic of conversation that we have with our users/customers to understand their problems and collaboratively develop the smallest, best solution. The story is not the solution—it's the beginning of the conversation you have to arrive at the solution. A story describes our users' work, not ours. The idea is that the best software solves real problems that real people have, and that, by identifying those problems, we can build something that's actually useful. By working on the software one small problem at a time, we guarantee that every release does something useful. People who talk about user stories being dead never understood what they were to begin with. You cannot build software without them.
English
8
24
162
9.4K
Benjamin Gibbs がリツイート
Allen Holub. https://linkedIn.com/in/allenholub
I'm not a fan of story points; I don't use or recommend them. That said, they can have some value inside the team when used as originally intended. The original XP team invented story points to obfuscate time estimates from management. They were using "ideal-time" (no distractions, dependencies, &c.) estimates as a point of comparison when selecting what to work on next. If two stories provided the same user/customer value, they'd use points as one factor in picking the story. A time-obsessed manager started treating ideal time as actual time, so they came up with story points to prevent that particular dysfunction. The whole point was that they made no sense to management. If you can convert points to time, or if you're using them for anything other than comparison, you're not using them as intended. If you really want to use points, I'd recommend that the team stop using numbers, T-shirt sizes, or anything else a manager can convert to time: All other things being equal, given a 👠 story and a 🦆 story, go wth the 🦆. Keep their meaning secret. Change the secret if anybody catches on.
English
13
9
90
10.1K
Benjamin Gibbs がリツイート
Gergely Orosz
Gergely Orosz@GergelyOrosz·
From a director at a more “traditional” company: “We’re starting to rename 2-pizza teams to 1-pizza teams. With AI large teams just no longer make sense and slows things down.” Teams are getting smaller in most places - even here
English
45
19
521
47K
Benjamin Gibbs がリツイート
David Fowler
David Fowler@davidfowl·
Here's an experiment I ran last weekend to use a ralph loop to reduce developer toil . The idea was to build a prompt and setup the environment to make it possible for an agent to automatically reproduce bugs and do code reviews. davidfowl.github.io/ralph-experime… Coding agents aren't just for coding, they are for automation. This isn't perfect by any means but it ran for ~1 day and was about $200 worth of tokens to do the bug repros. This is just the beginning...
English
10
23
150
19.7K
Benjamin Gibbs がリツイート
Gergely Orosz
Gergely Orosz@GergelyOrosz·
I'm kind of starting to get the voices on "SaaS" is in trouble. SaaS that is low value and easy to build from scratch (this is a static site where I have not changed much eg not added testimonials for 1-2 years): easy to move away now...
English
4
3
91
10.4K
Benjamin Gibbs がリツイート
Gergely Orosz
Gergely Orosz@GergelyOrosz·
One interesting observation: inside a Big Tech, the internal token leaderboard is dominated by… very very experienced engineers. Distinguished-level folks who you rarely saw code day to day before LLMs. Also, some VPs (!!)
English
87
38
1.5K
269.2K
Benjamin Gibbs がリツイート
Yoko
Yoko@stuffyokodraws·
One reason vibe coding is so addictive is that you are always *almost* there but not 100% there. The agent implements an amazing feature and got maybe 10% of the thing wrong, and you are like "hey I can fix this if i just prompt it for 5 more mins" And that was 5 hrs ago
English
714
622
11.1K
610.4K
Benjamin Gibbs がリツイート
David Fowler
David Fowler@davidfowl·
My team is having a dry January (no product features) to see how much of our technical debt we can automate away with AI. Will report back at the end of the month.
English
47
16
636
36.7K
Benjamin Gibbs がリツイート
Codie Sanchez
Codie Sanchez@Codie_Sanchez·
Best money I've ever spent as a CEO... an internal AI transformation hire. He doesn't care about title. He just wants to ship. And he goes across your entire org, sales, revenue, hr, apps, tech and kills stupid manual processes. Such an underrated unlock.
English
349
221
4.4K
639K
Benjamin Gibbs がリツイート
steve caldwell 👨‍🍳
steve caldwell 👨‍🍳@stevecaldwell·
PSA for a CTO, Head of AI, VP/Dir of Engineering, CXO: This is going to be one of the most important "back to work" weeks of your career. You must get your team aligned on agentic dev ASAP. If you're feeling behind or overwhelmed, here are some good reads to get you inspired 🧵
English
43
115
1.9K
297.7K
Benjamin Gibbs がリツイート
Robert Scoble
Robert Scoble@Scobleizer·
Been screaming this for weeks. Right on.
Aakash Gupta@aakashgupta

The entire robotics industry is about to compress a decade of progress into 18 months, and nobody’s pricing it in. The hardware has been ready for years. Boston Dynamics had Atlas doing backflips in 2018. The bottleneck was never motors or actuators. It was that every robot behavior had to be hand-coded. Pick up a box? That’s one program. Pick up a bottle? Different program. Move the box from shelf A to shelf B in a warehouse with slightly different lighting? Start over. Foundation models broke this completely. Before VLAs, teaching a robot one skill gave you exactly one skill. Zero compounding. Zero transfer. A robot trained to fold shirts couldn’t fold towels without starting from scratch. The labor intensity of data generation meant robotics datasets stayed narrow, robots overfit, and small variations like object weight or table height caused failures. Now a single Gemini Robotics model handles tasks it has never seen in training. Google’s On-Device model learns new behaviors with 50-100 demonstrations. Not 50,000. Fifty. That’s a 1000x reduction in the data requirement for new capabilities. The speed implications cascade through everything. First order: deployment timelines collapse. What took robotics teams 6-12 months of custom programming now takes days of fine-tuning. Second order: the addressable market explodes. Tasks that were never economical to automate suddenly are, because the integration cost dropped by orders of magnitude. Third order: the data flywheel accelerates. Every robot running Gemini Robotics feeds learning back into the foundation model. More deployments means faster improvement means more deployments. Physical Intelligence raised at $2.4B because investors finally understood this. Boston Dynamics partnered with Toyota Research Institute to bolt Large Behavior Models onto Atlas. Every humanoid company is scrambling to either build or license the intelligence layer they don’t have. The market is still valuing robotics companies on their hardware differentiation. But hardware is commoditizing. Boston Dynamics spent a decade perfecting locomotion, and now that’s table stakes. The value is migrating entirely to whoever owns the foundation model that generalizes across embodiments. Google trained Gemini on the largest multimodal corpus ever assembled. Then they added physical actions as an output modality. That’s not a robotics company bolting on AI. That’s an AI company whose models now output motor commands. The companies pricing this correctly are building around foundation model access, not around proprietary hardware. The companies pricing this wrong are still acting like the moat is in the mechanical engineering. AGI moving into the physical world isn’t a 10-year prediction. Gemini Robotics shipped in March. The 1.5 version with chain-of-thought reasoning shipped in September. They’re iterating on a 6-month release cycle while hardware companies iterate on 3-year cycles. The gap between software intelligence timelines and hardware development timelines is the entire trade.

English
24
30
894
180.7K