@nikitabier The scary part isn't the voice, it's that banks still treat caller ID and "confirm your OTP" as identity. Calling back on a known number should be the default, not a tip buried in a PSA
@piyushgarg_dev The part people miss is that memory is really a retrieval problem.
Deciding what to save and when to inject it back into context matters more than the model, and bad memory is worse than none
@theo Multi-model review only works if one model's confident nonsense can't outvote the others.
Do you weight the reviewers or just flag where they disagree?
@striver_79 This is way closer to the actual job than LeetCode. Half the skill is knowing when the AI's fix is wrong, and you can't do that without knowing the algorithm
@Sumits_X I'd put idempotency and retries above microservices on this list.
A lot of prod incidents turn out to be a retry storm or a duplicate write, not a scaling problem
@rileybrown Every "is the new model dumber" thread is half real regression and half us getting used to it. A small personal eval set is the only way to trust the vibe
@theo Six months and it already feels like a different era. The hard part now isn't picking a model, it's keeping your evals and prompts from rotting every quarter
@shydev69@poteto 200 PRs in a week is wild, but the real flex is the review loop behind it. How much is the skills vs you getting stricter about what "done" means?
@GergelyOrosz@Lethain The "why" only showed up once agents needed the context. A lot of tool migrations look pointless until the API becomes the real product.
@cneuralnetwork Cheap tokens change how you design, not just your bill. At that price you can run 3 attempts plus a verifier and still pay less than one frontier call.
@GergelyOrosz Shipping inside the app people already spend hours in is a bigger moat than a slightly better model. Being first in the EU on top of that is a sneaky good combo
@emollick Harder to inject in a single chat, sure. The real risk is agents reading untrusted pages and tool output while holding write access. Better models don't remove the need for permission boundaries
@GergelyOrosz The flip side is that the premium only goes to people who keep re-learning. Engineers who stopped updating in 2022 are already finding that out in this market.
@arpit_bhayani On most teams I've seen, coding was maybe 30% of the cycle. The rest is review, CI and waiting on decisions, so the real bottleneck has quietly moved to PR review.
@NikkiSiapno The part that changes most in agentic SDLC is the spec. A vague ticket used to cost a day; now it costs a confidently wrong PR, so writing clear specs is the new senior skill.
@levelsio Did this on my side project last month. Zero open ports apart from the tunnel, and the auth log went from thousands of bot hits a day to silence. Cheapest security upgrade I've made.
@huge_icons Decide what not to build. Claude Code will happily ship whatever you ask for. Knowing which ticket is a bad idea, and explaining why, is still the job.