Rednax

I have noticed a back and forth in engineering companies between prioritizing project teams, who focus on a single customer each, and product teams who focus on generic development, overarching the individual projects.

Upper management will see that a lot of products are sold (each sale is a project), and the company now actually has to deliver projects. So product teams are ripped up, and everyone is dedicated to specific projects, because making these deadlines is the most essential thing in the known universe.

A couple of years later, they hire expensive consultants to tell them how to optimize their business. These consultants will note (after simply asking the engineers) that there is a lot of development being done many times over, once for each project. So the entire organisation is optimized by ripping up the project teams, and placing the engineers in product teams.

The result is a new standardized product, of which the company can sell a lot, which eventually brings us back to step 1.

A good company will realise that going 200% into 1 direction will make it way harder to steer back once the inevitable pull into the other direction arrives. So a more temperate approach, tends to win in the long term. But explaing that to a manager is usually a waste of your time.

Best do that with something that hides the taste well. Maybe create a drink so aggressive that it might as well be a cleaning product. Just add some caramel to paint the whole thing black and you're good to go. People will love you coca product.

NOoo, not both!!! If we do that immediately, the episode will be over before Jeffrey Combs has even shown up.

If an actor studies all data available on your grandma, manages to mimic her voice and looks, and then starts a conversation with you, acting as your grandma; are you then talking to a ghost? Cause that is what an AI does: learn to predict the behaviour of your grandma, and then act out those predictions.

I have barely any experience with raw gdb, but debugging is something that allows for a lot of contextual actions. Even just placing a breakpoint is simpler if you can click the line instead of copy-pasting the line number. But also evaluating expresssions while on a breakpoint, or a graph with an overview of all threads. I doubt these are straight-forward commands in gdb, and if they are, you need to figure out the exact parameters (like line number).

Furthermore, I have tried raw gdb once, and got super confused as to what I was supposed to do or look at. Yet every IDE makes it trivial to use debuggers. Learning the options available to you is much easier in a well designed GUI.

GUIs just being front-ends for a CLI tool is a horrible idea. This is why most git GUIs fail so terribly. I have seen too many of those where all the buttons were just replacements for CLI calls. If it is just a front-end for a CLI, then why the heck not just use the CLI?

A good git GUI has not been designed to just wrap the CLI. Instead, it works with the structure of git (commits, branches, tags, etc), and builds around those from the ground up. Only once the functionality has been designed should the question arise: What CLI commands do we need to implement this?

I remember using mumble in a time when smartphones weren't even a thing yet. Love to see the open source tool outlive everything else!

I'd argue that it may not happen for individuals. But our DNA? Our culture? Or knowledge? I'm pretty sure these things will travel the stars one day.

The Dutch royal family has exactly one job: poster child. So, yeah. That is literally the idea here. Unify by setting an example.

Since google is blocked, google maps is also blocked. Hence, make sure to have a good alternative available. Bing maps, Apple maps, or OSM.

My guess is that he is a DnD player that has to flash out the background of his character, so the DM can start using characters from his background.

With Dirt Rally, you get a pretty damn good simulation experience for a fraction of the cost, a minimal time investment, and zero of the risks. All you need is a PC and a decent steeringwheel.