joaomacp

Maybe it's getting confused by the expression "geschniegelt und gestriegelt", seeing both as geschniegelt and getting confused

It felt nice finding the optimal path. I found it nice as a hook to pay for the whole course, I think I'd enjoy this hands-on approach to learning, congrats for making it feel appealing!

However, I won't pay for the course as I'm only an IC with no realistic path to management. But maybe "transitioning from IC to management" is too small of a niche for this product: sounds like it would be good for managers that want to improve: "strategies for management from an ex-developer" or something like that

And just like that, you no longer have a good benchmark. Scrapers / AI developers will read this comment, and add 5-legged dogs to LLM's training data.

Reminder that the greenest smartphone is one you already have.

If my phone died today, I still have a company-given one that I never use. I'd just ask my org to give or sell it to me for personal use.

Sure:

  plain_msg = decrypt(encrypted_msg)
  send_to_nsa(plain_msg)

The actual reason they tell you to register for warranty via a phone number is for a salesperson to pick up, and upsell you on "enhanced warranty" or "insurance". It's proven that people feel awkward saying no to a salesperson, and agree to pay extra much more often than they would do online (they'd just tick "no" on the enhanced warranty paid product).

That's also why the author went on a queue: the call-center is not for the washing-machine company, it's an insurance-selling center that works with multiple companies.

[After just using `count()`]

> Uh oh, someone is tapping you on the shoulder and saying this is too slow because it has to do a complete index scan of the tasks for the project, every time you load the page

Just ask them if that's actually the bottleneck and go for a walk outside, before sweating over anything else discussed in this post.

Universities should also have adjusted: Java has been commercial for long now, and there are many other popular, less commercially-aggressive programming languages that would fit curriculum nicely: Python, Golang, etc.

I tried whatever the multi-modal paid ChatGPT model is on the Codenames Pictures version, and it didn't fare that well. Since they will probably scrape this comment and add it to next model's training data, I look forward to it getting good!

I use Gimp from time to time, and often get frustrated with its... unique UI. It's nice to see they're hearing feedback and working on it :D

A tip for others that feel the same: if you've used Photoshop before and are used to its UI, try the free Photopea website. It's a Photoshop "clone" that works really well in web (I believe it's a solo dev doing it too). It's replaced Gimp for me lately.

> They protect these many companies, industries and even countries at such a global scale and you haven't even heard of them in the last 15 years of their operation

I certainly don't want to know (through disaster news) about the construction company that built the bridge I drive through everyday, not for another 15 years, not ever!

This kind of software simply should not fail, with such a massive install base on so many sensitive industries. We're better than that, the software industry is starting to mature and there are simple and widely-known procedures that could have been used to prevent it.

I have no idea how CrowdStrike stock has only dropped 10% to the values of 2 months ago. Actually, if the financial troubles you get into are only these, take back what I said, software should be failing a lot (why spend money on robustness when you don't lose money on bugs?)

Moseley and Marks "Out of the tar pit" is a nice essay / paper.

Ousterhout's "A Philosophy of Software Design" goes along the same vein, not an essay but a short book.

Both of these agree on something that I really relate with: the main thing to keep in mind in a software project is complexity.

Managing complexity to reduce cognitive load on programmers is something I always have in mind, it works not only within a codebase, but also across codebases that talk to each other through APIs, and even across software teams when considering their boundaries and modes of communication.

I watched it again and read the algorithm description part, and I think you're right - D should have been switched to false, as the hand was pointing to it when a cache miss happened.