Concluded the NeetCode redesign - huge congrats to @xilken
He made the entire UX so much cleaner, while still preserving the original design & functionality. Really really great attention to detail, especially the roadmap page.
Originally he implemented it with React and react specific deps - unfortunately we use Angular, but he quickly ported things over anyway.
Intelligence is supposedly a commodity now (lol), but deep effort & attention to detail are not. To me this just reinforces what I already believed, people who enjoy their work and put in extra effort always end up ahead.
Btw he's graduating next year and he's open to internships. Hire him before I do (seriously, i just dont have the time right now otherwise I would).
Side note: glad I waited a bit before deciding, in hindsight I was too ocd early on. There were a lot of really good designs. I gave away a total of $5k and it felt pretty good.
Will def do more contests, more than just UX
https://t.co/guhiG7CLan
because i dont want to be seen as a bully, lets make this a contest
if someone can create some mocks / redesigns that I actually use I will pay you $2,500 usd
if you have the skills to then implement it in the codebase i may also hire you
like i said, the bar to make it look better is pretty low, but please don't give me slop
@neetcode1 just launched a really good "Build your own GPT" from scratch project on NeetCode
check it out if you really wanna get your hands on your first ML project
I took the liberty to see how it'd look like on the redesign challenge site:
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
A lot of Google hate lately, most of which is deserved. But I just wanna remind people there’s a VERY long list of people that took a Google internal tool or paper and later started an entire company out of it, by making it available to the public.
If there’s problems at Google, they’re not with the people, they’re cultural.
There’s a wide distribution of engineers obviously, so even dummies like me get lumped in with the genius level programmers, but I would never bet against Google.
I wonder how much damage this does to Google Cloud, let alone Railway.
Has to be at least $1B for google long term.
As someone who worked in gcp, I would describe the culture as the opposite of customer obsession. I have a few horror stories I’ll keep to myself, but let’s just say there’s many smart people who are just not incentivized to care about the long term success of its services.
We are working to restore the Google Cloud infrastructure that powers our dashboard, API, and internal network's control plane. We are in direct contact with Google Cloud's support team. We do not have an ETA at this time.
We will continue to post updates on https://t.co/yyqjvnCDLD
@ngeloxyz@ryanvogel@JustJake I know we’ll see more in the post mortem, but doesn’t that kinda defeat the purpose of having your own infra? Not trying to dunk, but even if google didn’t block your guys’ account, a normal outage would’ve had similar effects right
We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.
"nearly three times as many executives at companies using or exploring AI said they were increasing junior-level hiring in 2026 than cutting back" - WSJ
Kinda goes back to what we all knew at the beginning. Jobs will change as a result of AI.
Sometimes the simplest answers are the most correct.