Head of Software Engineering 🖨️ john-green.dev Serverless Enthusiast ☁️ #AWSCommunityBuilders ☁️ 5 Gundogs 🐶
Cambridge, United Kingdom
- Tweets 2,359
- Following 610
- Followers 619
- Likes 2,827
Pinned Tweet
So pleased and surprised to have been made an #aws Community Builder for #serverless
Really excited to be joining the #awscommunitybuilders community with some great other people in the #serverless space 🙌
ALT AWS Community builders
8
3
33
This is an absolute joke.
Utterly pointless and if anything will hurt you if you are using this as part of your job interview.
19
I'm still a big fan of serverless and using Aws CDK your AI agent can build the infrastructure you need that's tailored to your project.
Just remember to review it before you deploy 🤑
1
2
145
I always get the feeling this this is going to be so important in the future.
New: Entire now tracks subagent activity in Claude Code, Codex, Cursor, and Factory Droid, creating a durable record on each parent session.
Review or roll back a subagent's work with the confidence you'd have in your own commits.
Learn more: entire.io/blog/entire-dispat…
1
101
Slop is not new.
We have always been dealing with dodgy PR's from people throwing in some half baked rushed code.
The big problem now is that it come at a 10x even 100x rate.
1
1
168
How many of you "vibe coders" even know what CRA is.
Are you ready?
You have 11 days to sort out your vulnerability reporting processes.
Good luck 😆
57
A lot of people talking about "Vibe Coding" - the biggest problem is we have no formal definition of what is vibe coding and what is AI assisted development.
How do you define it?
2
1
86
For me Vibe Coding is bad - its full reliance on the AI with no verification or "human in the loop"
AI assisted is when you have frameworks and guiderails around the code, you understand what its doing and how the system is architected.
You should always be able to jump into the code at any point. Vibes don't allow for this, AI Assisted does.
42
Can completely see this workflow becoming used. It's great when you can continually deploy.
My biggest difficulty is the QA part, it's still pretty manual on physical devices and the Dev parts are now so quick.
Software dev feels like it’s headed toward this sort of workflow:
1. Interactive: planning, prototyping, experimenting, then when it’s shaped reasonably well, add to the queue
2. Autonomous: continuously running orchestrator agents processing the queue and creating PRs
3. Interactive: QA, final iteration (or kick back to #2 if not good enough)
4. Autonomous: integrate / release
5. Interactive: feedback loop, improvement of the factory, evals
* * *
Some devs don’t want to do #3 / #5 at all. Classic vibe coders. They’re missing out on compounding benefits and instead getting compounding tech debt.
On the other side of this, other devs don’t seem to see the value of automating #2 / # 4 and want to do those chunks interactively or manually. They’re spending far too much time on things that can be done reasonably well autonomously, or they’re stretching themselves thin trying to juggle multiple agents.
I try to spend enough time on the interactive steps so that the autonomous steps give me good results. This is a constant amount of work and diligence, but the results are getting incrementally better over time.
48
Embedded software development moves different because customers don't upgrade.
Deploy twice a year, support for 5 years.
That's not being slow.
That's not bad process.
That's just the actual job.
2
1
52
This will not be long. I think never year we will see some major updates. @iRobot what you working on?
Imagine coming home and your robot has already done the chores you hate.
Not in a sci-fi movie. Not inside a research lab.
Just a robot in your home, cleaning, carrying things and helping with everyday tasks.
We are still a long way from truly reliable home robots, but seeing progress like this makes the future feel much closer.
So tell me… what's the first chore you would hand over to a home robot?
1
1
82
The bottleneck I see in most embedded teams isn't code. It's reproducibility. I'm now heavily focusing on observability and automation. Can't ship fast if every bug takes a week to reproduce.
A couple thing I look into are:
- structured logging from day one
- hardware simulation
1
1
53
Hot take
Working in the office is better than remote
I have worked both for many years and nothing beats being in person.
The productivity, collaboration, enjoyment all make for a great environment to work on in
Sure you can write more code at home but it's it the right thing?
1
1
68
@ the real @SimonHoiberg fyi -> @SimwHoiberg
I was confused when you "followed" my small little account ( of a head of software ramblings )
If someone wanted to, you might hear about my latest pains of budgeting during the fast changing world of AI 😆😎
71