Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.
🎉 Just announced! WebStorm is now free for non-commercial use!
Whether you’re learning #JavaScript, working on open-source projects, creating content, or coding as a hobby, you can now do so for free 🥳
🔗 https://t.co/oTcCcGNa8H
Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isn’t a “git gud C++ is hard” issue and it damn well isn’t an DEI one.
Some folks don't look at Nx because they think it's an "Angular thing". It's 1000% NOT an Angular thing. I've literally never used it on an Angular project, and it's a fantastic tool for managing JS/TS monorepos and build pipelines (with Vite and your other favorite stuff)
“No matter how great or superior a language is, it doesn’t matter if people don’t use it”. I love the authenticity of the writer. #fullstack#engineering
https://t.co/RgajEmiIez