Love the POV that AI better enables junior engineers who have a fresh perspective.
Companies never hired juniors because they were the best coders in the first place 😉
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
2
41
Donald Bough retweeted
Nearly every phone and computer on Earth relies on one plain-text file to know what time it is.
When a country changes its clocks with a few weeks’ notice, or Morocco pauses daylight saving for Ramadan, someone has to update that file. Since 02005, that someone has been Paul Eggert, a computer science professor at UCLA, who does it as a volunteer.
Take a look at this great data visualization to see the full story:
na2.hubs.ly/H08qtQC0
Donald Bough retweeted
Are you kidding me?
The official Xbox response to mega-viral game remixing is "This is good for players. It challenges our business model, so what. We'll start a lab."
Asha should run MS. Never seen anyone this tapped in
Today we're standing up XBOX LABS (labs.xbox.com). Here is the note that I sent to the team:
Team,
The first video games emerged some 75 years ago. In the time since, there have been booms and busts, but every year there are more great games to play, more devices to play them, and best of all, more people than ever playing. That growth helped make XBOX what it is today, and we've helped shape the industry in return, from bringing hard drives to consoles and online gaming through Xbox Live to Game Pass and cloud gaming, alongside franchises that have brought millions of people together.
In recent weeks, we've seen games rapidly decompiled and rebuilt to run on hardware they were never originally designed to support. Windows PC builds have been translated to run on Apple Silicon or ported to run inside a browser through WebAssembly and WebGPU, the latter now approaching 90% global browser support. Perhaps more surprisingly, we've seen many of the biggest games in the world have been remixed into the source code of another.
These experiments challenge long-held assumptions about our industry: the tether between software and hardware, the boundary between creation and play, and how people discover and experience games. While it is hard to predict the future of gaming, it is easy to see the possibilities in making great games easier to access, giving old games new life and allowing more players to become creators and co-creators. These are unmistakably good outcomes for players, even when (and sometimes because) they challenge our existing business models.
To explore these possibilities, I’ve asked Scott to stand-up XBOX LABS, a small group of game makers, engineers and scientists whose job is to turn emerging ideas into things our players and developers can experience. We'll build in the open, learn from what people do, and measure success by whether more people are playing and creating.
I think XBOX has an important role to play here. Coding became the first major workload for agents because they can write, run, and test software. Games share many of those same properties, and people spend more than 72 billion hours a year playing XBOX games, roughly five times the estimated time spent writing code worldwide. We've spent 25 years learning how to make great games, and I want our game makers to help shape what these new technologies make possible. As we learn, we’ll share the tools we build with developers across the industry, just as we always have.
Our priorities aren't changing. We remain committed to the 4Cs, to making great games, to our hardware and to being responsible stewards of IP and the communities built around it. LABS gives us a way to explore new technology that is game design led without abandoning the work already underway.
Asha
Haha this looks surprisingly well done
Chief Design Officer @jgebbia officially unveils America.gov, the new online home for the United States of America
3
45
Donald Bough retweeted
Replying to @GergelyOrosz
Easiest way to accidentally crash an SDK is a bad config like this. Probably a json blob that isn’t type checked on their backend. Easy to set a value that makes sense, but the SDK doesn’t expect.
SDKs must internally catch these exceptions, sprinkle try catch everywhere!
Donald Bough retweeted
We’re announcing Sentience out of closed beta today.
Your Sentience is your digital twin. It looks, sounds, and writes like you, and it operates autonomously.
This is our first milestone in our quest towards uploaded consciousness.
Donald Bough retweeted
testing an idea: who wants to sponsor nitro for the @purduehackers discord server? we have ~3.3k members, growing consistently (+5-7% MoM), with a 53% server engagement rate.
ez win to reach a ton of builders, makers, and talented people from our community for only $60/month! quite a steal for what we normally charge to engage with our members :)
i’ll even have one of our awesome designers custom-make a server banner with your logo! interested? shoot me a dm!!
Donald Bough retweeted
Always remember that your goal is NOT to prove you're smart. It's to make problems go away.
Career progression is all about delivering on projects that grow in scale, complexity, and responsibility. And the #1 way to get those projects is to put pressure on your boss to come up with more work for you.
If a recruiter wants to send me personalized goodies I would be strongly inclined to say yes
On recruiting great ppl:
- great people are (a) rare, and (b) always have tons of options
- therefore once you decide a candidate is great you cannot hesitate or delay. You must drop everything and rearrange heaven and earth to get them
- there are small things (sending flowers), medium things (comp), and big things (their identity and dreams)
- you want the barbell strategy-- put all your energy into small things and big things. Leave medium things till the end
Small things:
- ppl massively underestimate the power of small gestures. TL;DR: love-bomb the candidate
- spend more time than money. Expense accounts are abundant but time is scarce. It's an expensive signal no one can fake
- stay in close contact over text and phone
- send them a first edition used book or an analog oscilloscope or some other random thing they mentioned in passing they like. Make these unique, everyone sends wine
- invite them to computer history museum or moma or something. Spend time with them! Treat these meetings as dates, make them unique. Everyone buys dinner
- be persistent but not annoying. Sometimes ppl need time alone, you should respect that.
Big things:
- there is a gap between what the candidate is doing in life and how they see themselves in the privacy of their dreams. Your job is to help them bridge this gap
- to bridge the gap you must first understand it. Take the candidate on walks to museums and parks. Walks help the candidate drop their guard so you can learn about them. Try hard to get to know them, to understand their dreams
- use your mission, your culture, your people, your company to paint a world for them in which the gap no longer exists. You may need to adjust the role or even change it altogether. For great ppl it is worth it
- don't assume ppl want what you want, dreams can take all kinds of shapes. Maybe they want their work to matter, maybe they want a bigger team, maybe they want to code and avoid meetings, maybe they want to be in the center of the action, maybe they want to learn, maybe all or some or none of the above. Find out!
Medium things (aka closing):
- you've constructed a world the candidate is excited to live in. The purpose of this phase is to remove mundane obstacles to make this world easy to enter
- I don't think I ever sold a candidate on a dream and then lost them on comp. Ppl just want to be compensated fairly and work out some life constraints
- I don't have much to add to all the comp advice out there. My philosophy on comp/closing is to get this part done and move on, don't penny pinch too much, and give more equity
---
Failure modes/don't do this:
- do not ignore candidate's spouse/parents. They have an outsized role in the decision. Most of what I said about the candidate applies to them too (love bomb them, understand their dreams, etc.)
- counterintuitive, but do not talk about the company or even the mission too much. The candidate and their dreams are front and center. At this stage you, the role, the mission are only relevant to the degree they can make candidate's dreams come true
- same w/ perks, what the day is like, etc. Don't blindly talk about these-- use them as tools to reenforce how the candidate seems themselves
- don't get mad if ppl reject you, it happens. Maybe it's not a fit for them now but will be a great fit four years from now. Maybe they become a customer. Maybe you work for them ten years later. Play the long game.
120
Keep your code clean y’all
“The downside of not having a clean codebase is worse than ever.”
just watched an interview from @thdxr explaining why OpenCode’s codebase is now cleaner than it’s ever been.
an agent’s performance is a function of its intelligence, your instruction, and its context (the codebase).
that’s why it’s more important than ever to maintain the codebase regularly, establish patterns, and go back to fix some of the old deprecated ways.
128

































