Did anyone else solve the puzzle after finding a bug in today's puzzle where on step 13 the circle you were trying to match didn't change, but should have?
Oh, nevermind, it appears others noticed this bug, too!
Cleaning up of feature flags was something that I excelled at failing to do. If you are the one cleaning them up, then you sir deserve a raise. Don't question it. It's a service.
Now if your site was named wafflehurricanetracker.org it would have probably survived trademark issues. The scraping issues would have been better if they were anonymized - it wouldn't necessarily be obvious that it was Waffle House (TM) that you had scraped, but if you suggested it was made by slow scraping websites of one or more popular breakfast establishments, then it wouldn't have been obvious.
It's also worth noting that in systems that get as large as Google's that you end up with commits landing around the clock. It gets so that it's impossible to test everything for an individual commit, so you have a 2nd kind of test that launches all tests for all branches and monitors their status. At Google, we called this the Test Automation Platform (TAP). One cool thing was that it continuously started a new testing run of all testable builds every so often -- say, 15 minutes, and then your team had a status based on the flaky test failures vs solid test failures of if anyone in any dependency broke your code.
So if your code is testing fine, and someone makes a major refactor across the main codebase, and then your code fails, you have narrowed the commit window to only 15 minutes of changes to sort through. As a result, people who commit changes that break a lot of things that their pre-commit testing would be too large to determine can validate their commits after the fact.
There's always some amount of uncertainty with any change, but the test it all methodology helps raise confidence in a timely fashion. Also decent coding practices include: Don't submit your code at the end of the day right before becoming unavailable for your commute...
I'm working on an engine based in C++, Luau, and OpenGL - started almost 2 months ago. I aim for it to me MIT license open source, but it's too early for sharing. When it is, I do plan to post a show HN with the Github link.
You realize that you just gave hacker news gave enough details to commit some satellite controlling backdoor into their system... It's not like some of us aren't going to be like: "Yeah, let's get 'em!" Not me. I'm the ethical type, but some people might think:
Step 1: Modify OSS repository to gain control of satellites
Step 2: ...
Step 3: Profit!
"At first, the senior director didn't outright tell me I couldn't stay in the old domain, but made it very clear it was in my best interest to move to the new domain, where there wasn't a staff+ engineer."
Do you think this was good advice? You took their advice, even if it seemed a bitter pill at the time. They were most certainly part of the process for your promotion.
It feels like this senior director is in your corner. I'd schedule a 1:1 with a simple agenda of "looking for advice".
Definitely start with a compliment. "I remember that you advised me to move to X, Y time ago, and you were right that it was great for my career and promotion."
Be clear and specific about your desires - "I miss working on X technology. I was wondering if you have any visibility into any 2025 Q2, Q3, H2 projects or opportunities related to X technology that I might be able to [contribute to or transition to]." Sometimes you can be 50/50 to try something out or dip your toe in the water if you are attached to the success of something else. It's important that you be clear and specific. Maybe you could do this via email - it depends on if you are introverted or extroverted.
I once had an EM go back to Principal IC in an area that he loved. He's still working on it.
Oh, nevermind, it appears others noticed this bug, too!