Roman J.

Amazon you know you had it coming I vowed to troll you for ALL BS layoffs. Because the best thing that Andy Jassy could ship is the Kindle in color and mass firings. 🫏🫏🫏🫏 #softwareengineers #tpms #pms #qa #engineeringmanagers: I’m going to say this many times but this time I’m going to yell it 🎤🎤🎤🎤🎤 IF A COMPANY EVER ASKS YOUR ORG TO DOCUMENT YOUR ENTIRE WORK FLOW YOUR JOB IS TO DOCUMENT IT SO BADLY THAT THE COMPANY WILL GO OUT OF BUSINESS IN 2 WEEKS. I do not understand why people still simp over AI. 🫥🫥🫥 While they tell you to your face: We are LITERALLY taking your work AND then your whole JOB and CAREER. This. Is. Not. A. Drill. 🚨🚨🚨 I don’t care what you do. Put it all in Perl. Vibe code something so bass ackwards that every customer will literally get a picture of the CEO laughing and saying “I fired the person that made this to make myself more money if they push a button.” Make every API call sign your customers up for “More information about Scientology.” Sabotage it. Make plans with your fellow engineers to make sure it is the worst decision that they have ever made. Turn this around and make AI as incompetent as the CEO who decided to fire you after stealing your entire personal IP. I believe in you. You are an engineer. You can F up anything. And yes, this specific stink eye is for you, Prime Video & Amazon MGM Studios - wow. 🫡🫡🫡🫡🫡🫡🫡🫡🫡🫡🫡🫡🫡🫡🫡🫡

21

4 Comments

Who's automating manual QA of visual features? Gotta be smarter than Playwright or general coding agent + browser use, needs to understand the intent behind a feature and come up with edge cases. Literally the last thing left of my build process I haven't been able to delegate.

13

7 Comments

Our team was shipping features on time. But something else was breaking. People stopped asking questions in code reviews. New developers took weeks to ramp up. Decisions that used to take one conversation now needed three meetings. We blamed remote work. Blamed hiring. Blamed Slack. But the real culprit lived in our frontend architecture. See, we'd made a decision two years earlier. We split our app into micro-frontends. Seemed smart then. Each team owned their slice. Independence, right? Wrong. What we actually built was three different patterns for state management. Three approaches to API calls. Three component libraries that looked identical but weren't. Every time a developer moved between teams, they relearned everything. Every cross-team feature became a negotiation about whose pattern to follow. The architecture didn't just create technical debt. It created cultural debt. So what shifted things? I stopped a sprint planning meeting. Asked everyone to map how data flowed through one feature. 4 engineers, 4 different diagrams. That's when it clicked for me. Bad architecture doesn't show up as slow page loads. It shows up as slow conversations. Confusion becomes the default. People stop collaborating because the code itself doesn't collaborate. We spent the next eight weeks building alignment. Not rewriting code. Building shared mental models first. We documented five core patterns everyone would use. Picked one state approach. One API layer. We lost two weeks of feature work. But ramp-up time dropped from three weeks to four days. Code reviews got faster. People started pairing again across teams. Our next three hires hit production contributions in their second week. Your architecture choices aren't just technical. They're hiring decisions. Onboarding decisions. Retention decisions. When your frontend can't explain itself, your people can't either. Look at your team right now. If ramping up takes more than a week, if cross-team work feels like pulling teeth, if your best engineers spend more time in meetings than in code, your architecture is leaking into your culture.

12

Struggling to hire developers? You’re not alone, the best aren’t on job boards. 85% are coding right now, not searching. Here’s your 2-week fix (skip the 2-month wait): - Ditch job ads. Most devs don’t read them. - Find real teams using your tech. Reach out. - Share stories of impact (“Our last hire saved $2M.”) - Offer big missions, not long tests (“Help scale to 10M users?”) - Decide fast. 48 hours > 6 rounds. The myth: “No developers left.” The truth: Bad hiring chases away the right ones. While others ‘post and pray’, you’ll hire the future. What’s the weirdest hiring advice you’ve heard in 2025? 👇 Drop it below. Best one gets a bonus tip. 🔁 Repost: To help someone avoid bad hiring habits. 👤 Follow: For more ROI-first hiring playbooks.

34

37 Comments

The Browser Strikes Back: Rethinking the Modern Dev Stack by Jono Alderson Modern browsers now deliver powerful tools for layout, animation, state, and storage that once required heavy JavaScript libraries and frameworks. Jono Alderson makes a compelling case for treating the browser as an ally rather than an enemy, showing how leaning into native capabilities unlocks simpler, faster, and more resilient ways to build. From CSS Grid to Web Animations API, discover why the tools you need might already be in the browser. Ready to shed framework fatigue and embrace the platform? This talk will transform how you approach your dev stack. Learn more and register now for Dev Summit 2025, taking place in Sydney and online November 2025!

2

1 Comment