Hiring is broken. LeetCode doesn't measure real engineering potential.
We're building Enigmatch: A platform where candidates solve "Enigmas": complex, real-world problems with no single right answer.
๐ Our Waitlist is now LIVE.
โก๏ธ https://t.co/Hs2MEdkIO1
> A director in AWS walked me through their new "efficiency matrix" - entire teams being replaced by 2-3 senior engineers running Claude Sonnet workflows
We are exposed to the risk to get kicked out.
Do we really have to prepare getting hired while we've not kicked out?
Amazon just confirmed 16,000 layoffs but sources inside are telling me the real story is so much worse
Word from three different VPs: the 16K number is just "Phase One" - internal docs show another 14,000 cuts planned for Q2
A director in AWS walked me through their new "efficiency matrix" - entire teams being replaced by 2-3 senior engineers running Claude Sonnet workflows
The Alexa division got completely hollowed out. 847 engineers two months ago. 23 remaining after this week. All hardware development moved to a Bangalore team of 31 contractors with Cursor access
Here's the sick part: they're making the outgoing engineers document their entire decision-making process into "knowledge transfer sessions" that are being recorded and fed directly into training datasets
One L7 told me he spent his final two weeks creating detailed prompt libraries and workflow documentation. Thought he was being helpful for the transition
Turns out he was literally training the AI agent that replaced his entire org
The contractors offshore are using his exact prompts and shipping features 40% faster than his old team of 12 Americans ever did
Internal Slack shows leadership celebrating "operational excellence" while badges get deactivated in real-time
They're calling it "right-sizing for the AI era" in the all-hands
But the P&L sheets I'm seeing show $280M in salary savings this quarter alone
The knowledge extraction is complete
If you're still at Amazon and haven't started job hunting, you're already dead
There must be a more efficient way to interact with coding agents than just prompts.
E.g, imagine writing requirements and specifications directly onto a wireframe as you iterate. Then every update to that wireframe automatically triggers the coding agent to run.
since everyone already knows, iโm joining @opencode
here's a demo of a thing im working on: async subagents / background agents
should this exist? tell me what youโd use it for
I was surprised to see many coding tools released.
While choosing, trying and getting familiar with, new one will be released.
What's going on !?
Use Claude Code without wasting time.
Recently we are enjoying the full of coding tools and agents.
But, how can we monetize more than I pay for those tools?
What should we build and whom to sell?
Tetris in the terminal... but the blocks turn into sand?
Damn what ๐คฏ
๐งฉ setrixtui โ A TUI puzzle game where falling blocks become sand
๐ฎ Clear lines by connecting one color from left edge to right edge
๐ฆ Written in Rust & built with @ratatui_rs
โญ GitHub: https://t.co/5bDx2Pq7sZ
#rustlang #ratatui #tui #gamedev #terminal #puzzlegame #indiedev
@shinya_ai_dev honestly i think it's both and you can't separate them. the models got better but they also forced us to build better scaffolding around them. which part of your setup changed the most โ the prompts or the guardrails?
Since Codex-GPT-5.3 / Opus 4.6, I feel agents became much more autonomous for coding.
Or maybe itโs just that my https://t.co/G0qSdQa8bC / https://t.co/DMGBnCnIZK has matured?
Itโs hard to disentangle how much of this shift comes from the agentsโ evolution vs my learning curve.
Coding agents keep getting faster and smarter, but Iโm still the bottleneck when defining specs.
Even if parallel development clears issues insanely fast, figuring out what to change and how isnโt trivial.
Especially once usability comes into play, it takes hours.