sclangdon

Isn't it this case no matter who wrote the code? How do you ever run anything if you're worried about bugs?

He may be referring to the fact that it could be pronounced Auschwitz. I must admit, my immediate thought on reading the name was "why would someone name their app after a concentration camp?"

Most games don't have the time budget for that. Visuals take precedence, and it's not easy to get to 60fps as it is, especially if you're doing a lot of other processing.

And stealth games especially will probably rely a lot on shadows and other visual things, which make rendering more expensive.

I realise for casual users Windows is always going to be the OS of choice if for no other reason than it comes pre-installed and most people don't know how to reinstall an operating system.

However, Windows may be in trouble with more tech-literate people who do know how to change it. I can only speak for myself, but I've been a Windows user since 95. All but one of my programming jobs over the last 20 years have also been working on Windows. But I really dislike the direction Microsoft are taking and I find Windows to be terribly slow these days, with each version seemingly worse than the previous one. So I decided to look elsewhere.

A couple of months ago I bought a new laptop with the express intention of running Linux on it and giving it a good college try (I didn't want to mess around with dual-booting and I still need Windows on my main PC for work... for now). I know very little about Linux, but I've decided I'm not going to use Windows past 10 so it's time to find something else.

I went with Debian running dwm (Debian because I value stability over everything else, and dwm because I like the suckless philosophy) and it's honestly surprised me how good it's been. It's SO snappy. Everything is instant. It's really been a breath of fresh air.

I was especially dreading programming since I've solely used Visual Studio since Visual C++ 4.0 and don't really know anything else. Anyway, I went all-in and started learning Vim, GDB, and Make, and boy do I feel like I've been missing out. I'm really enjoying programming again, which for me has just become a job over the years.

Anyway, my point is, if tech-literate people are willing to give Linux a try, I wonder how many of them would be as surprised as I was and may make the switch permanently. With Windows getting worse, and Linux getting better, maybe more than ever.

It's not that we think it's arcane or that we are in our own "bubbles of thought", it's that we aren't doing math. We're programming a computer. And a competent programmer would know, or at least suspect, that doing it with logarithms will be slower and more complicated for a computer. The author even points out that even he wouldn't use his solution.

P.S. Please look up the word literally.

Maybe, but a circuit designer is pretty high up the list of things that need to be boring and functional.

Things such as function overloading, operator overloading, dynamic dispatch, etc, are all conveinient but also obscure what is actually happening.

To take C++ as an example (I love C++ btw, this isn't another C++ bashing), a line as simple as "variable1 = variable2;", could be doing all kinds of things (including not even assigning) because of the ability to overload the asignment operator. As someone reading this line of code for the first time, you don't really know for sure what is actually happening unless you also go and read the code for "=".

My first job was as a COBOL programmer on an IBM mainframe (OS/370 I believe) for Xerox. The system was absolutely massive and incredibly difficult to navigate. There were thousands of files with names that only had 6 characters. So everything was a two-letter system code, followed by four digits. LP0456, OP0234, SB1245, etc.

Then, in each of those files the variables had similar names in order to cut down on unique identifiers. WP100, WP101, up to the max number you needed at any given time. It was a nightmare. There was as much external documentation to keep track of all of this stuff as there was code.

On top of that, you could only build programs overnight in a batch process with the rest of the system, which was run by a different team in a different country (Spain, I believe). So you would write your program in the day, phone up the guys in Spain and explain that there was a new program going in and you were responsible for it. Problem was, if your program failed to build it would hold up the whole system, which HAD to be up and running and live again by the morning. This meant that every time you made a change that went into the nightly build you also had to be on call.

I remember eagerly watching the build queue at 1AM, waiting for my file's turn. Then immediately shutting everything down and going to sleep the moment it was successful. If it wasn't successful, well, then you had to fix it on the spot and phone Spain again to tell them to give it another try. Unfortunately, you rarely knew why it was failing.

I don't really understand this idea of never taking your hands off the keyboard. Maybe people program differently to me, but most of the time I'm not typing anything. Most of my time is spent thinking. When my thoughts are clear and the problem is solved, then I type. And when I do, it's usually no more than a dozen lines at a time.

I get the impression from these people that they are constantly typing things. In fact, they're typing so much that they can't possibly waste valuable seconds using a mouse. I must be misunderstanding what they mean because that just can't be right.

And what's with the "you can achieve the same thing faster, without breaking your concentration" in regard to using a spell-checker or a calculator or whatever. Are you being serious? I can achieve the same thing faster? I mean how long do you think it takes to check the spelling of a word? Even if I must look it up in a physical dictionary, how long are we talking here?

Guys, seriously, slow down. You're going to burn out. I don't want to judge because I don't know you. Maybe you're a rockstar, but I'd guess that if you're really going this fast, the quality of your code is suffering.

I have a similar nitpick with boolean arguments. How many times have you seen something like: DoSomething(true, false, false)? It's much more readable if you use enums (in a language that doesn't let you specify the argument name at the call site). E.G. DoSomething(ENABLE_REPORTING, USE_UTC, OUTPUT_VERBOSE).

If you're developing on Windows, I find a good way of dealing with this to convert paths to short format before using them (E.G. GetShortPathName in kernel32.dll).

I think the point he's trying to make is even if you know how to deadlift correctly the amount weight involved carries a high risk of injury. Cleans on the other hand involve lower weight and so has a lower risk of injury (assuming you know how to perform it correctly, of course).

>Take a book out of Eddie Hall's playbook who says the exact same thing... And he's literally the strongest man in the world.

Robert Oberst, another WSM competitor also says the same thing and talks about it on the Joe Rogan podcast (#1321 I believe). To quote:

"I went from football to strongman, and in football we never did deadlifts. It was all hang cleans and power cleans, which by the way, quick little tip: if you’re deadlifting to be a better deadlifter fine. If you’re not, (you’re) doing that for deadlift’s sake, don’t fucking do it. The risk to reward ratio is a joke."

"A lot of people are not going to like that I’m saying that. (…) If you go to any NFL gym, any college football gym, any athletics where people are actually getting paid and it matters what they’re doing, they’re not deadlifting. They’re hang cleaning and power cleaning."