@MaxPW777
Account based inFrance
About this account
- Account based in
- France
- Connected via
- France App Store
Account-level information from X, not a live location or the device used for a specific post.
slop whisperer, based nix enjoyer / opinion haver
Joined June 2019
- Tweets18
- Following602
- Followers5
- Likes145
I fully agree, but as a junior developer I struggle to see, in a professional context, where the line is between fast and functional versus deep understanding. I know I can move fast with AI and ship something that works, and I know I can fully understand a system given enough time.
How do I balance needing to understand the entire flow of what I'm writing when a productive developer is defined by speed and quality—which for some means swarms of agents and so much context switching that you don't follow most changes?
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage.
I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care.
But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently.
For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios.
But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
I’m almost 100% @AmpCode pilled. But I still reach for my Pi setup when I need to think harder on an issue.
I don’t think I fully get the Amp team’s vision for planning and review. from what i understand for them it’s atomic commits, no PRs, push to main, lots of small releases (really awesome and seems to work great).
amp code looks to follow that vision: It feels so natural to talk with puck about an issue and boom have a fleet of orbs working on the same task then having puck ship it, even for small changes orbs are so easy to use i just fix the problem, small review and press 🚀
Which feels like my old flow of iterating deeply on a plan with call stacks and code snippets hand crafted with something like plannotator feels harder to do when the tool pushes for this same flow, is this the vision ? — am I misusing it?
Would love the team’s view on where plan iteration sits
