#bjarne-stroustrup

#bjarne-stroustrup

Companies hiring developers with several years of experience expect candidates to demonstrate practical reasoning about functional programming patterns, concurrency models, and the Scala type system. A mid-level engineer is usually expected to work independently, contribute to design decisions, and understand the trade-offs behind the tools they use.

Which Algorithm Is This? If you step back, this maps almost perfectly to the Top K Frequent Elements problem.We usually solve it for integers in a list. Here, the "elements" are audience profiles age and body-type combinations. First, define what an audience profile looks like: case class Profile(age: Int, height: Int, weight: Int) What we want is a function like this:

Anthropic has launched Claude Sonnet 4.6, an update to the company's hybrid reasoning model that brings improvements in coding consistency and instruction following, Anthropic said. Introduced February 17, Claude Sonnet 4.6 is a full upgrade of the model's skills across coding, computer use, long-context reasoning, agent planning, design, and knowledge work, according to Anthropic. the model also features a 1M token context window in beta.

If you've been programming for any number of years, you've pretty much lived through a bunch of hype cycles. Whether it's a new development environment, a new language, a new plugin, or some new online service with an oh-so-powerful time-saving API, it's all "revolutionary" and "world-changing," at least according to the PR reps hawking The Big New Thing. And then there's agentic AI coding. When a tool can help you do four years of product development in four days, the impact is world-changing.

XAI just open sourced the X recommendation algorithm, and honestly, it felt like they massacred my boy. I scrolled down expecting to see language stats like the 2023 repo. You know the usual breakdown: Java, Scala, maybe some Python sprinkled in. Instead, there were only two languages listed. Rust and Python. That's it. Which immediately tells you this wasn't a refactor. This was a full rewrite.

The reason for this is Snap - a Linux application packaging format - creates a local Trash folder for each VS Code version, one that's separate from the system-managed Trash, according to a VS Code bug report dating back to November 11, 2024. Not only that, but Snap keeps older versions of VS Code after updates, potentially multiplying the number of local Trash folders and the trashed-but-not-deleted files therein. Emptying the system Trash folder doesn't affect the local instances.