5,690 karma · joined January 27, 2011
People keep claiming these things increase productivity, yet there seems to be very little evidence of productivity increase.
The problem is, work is where a lot of people find meaning in life. For those people, more work means more meaning, and you're hurting them by telling them otherwise, especially if they are too young to know better than what you are telling them. And you're also preventing young people from becoming outliers ... what would be the cost to our society, and to the individuals personally, if Einstein, Dirac, Pauli, or whoever had been told to cut down on the amount of time they spend thinking about physics stuff, they need to achieve good work/life balance.
A lot of people in China are working pretty hard. If you want your country to get whomped by China economically and geopolitically, spread the idea that it's bad to work hard.
Americans in the past, back when America was able to coordinate to do ambitious things, worked pretty hard. So if you want to have a country that is unable to recreate glories of the past, spread the idea that it's bad to work hard.
All this only happens if you have an idea of work as a draining thing, a net negative on the individual doing the work. But I am happier because of the work that I have done. I am a better person than I was before.
Nobody goes to the kung fu school and says "hey it's bad to exercise this much, you shouldn't kick so high or punch so fast, just make sure not to train that much, okay?" But for some reason we have decided it's okay to give people this advice in other realms. You know what, I never felt as good physically as I did when I was in serious kung fu training. (Never looked as good either).
If you are in a job that actually is damaging if you do it too much for too long, then by all means, minimize that -- but you know what, in today's world, there are always proximal things you can do that are not damaging that will improve your job or your ability to do your job over time.
But advice like this does not make the distinction between jobs that are damaging and jobs that aren't. We're losing the idea that the latter thing exists, and I think that is very bad for the overall development of our society.
That said, you can always be surprised, and it’s delightful when this happens, so you don’t want to get on an egotistical high horse and decide you really know the system without playing it. The actual experience of the actual system is your reality check.
But, the more experience you have with that system, the more you can see where things might go (unless it’s intensely chaotic, thus unplayable).
The article says that I like to find ideas by “playtesting” then goes on to describe playtesting as a form of user testing.
Whereas there is some definition of the word playtesting that might be applicable to the way I design puzzles, it is not remotely the one in the article. In fact I think too much “playtesting” as described here will make your game boring, and will degrade your skill as a designer, and over time make you a boring designer. It is important to avoid this.
If you playtest too much it means you don’t really know what you are making or don’t have confidence to determine what playing it can be like. Even if you don’t have these skills or this confidence yet, you should be working on building them. Certain high skill levels of design will not be accessible otherwise.
The amount of playtesting we did on The Witness was very small — about 5 or 6 days over the course of 6.5 years, on a game that takes 50-100 hours to play through.
Whereas I do sometimes get puzzle ideas from bottom-up exploration of a space by myself (which is the definition of “playtesting” that would make sense here), in fact the vast majority of my puzzle ideas just spring to mind after I have built a sufficient understanding of the possibility space. So these are more like two distinct phases of design, and you might switch between them when designing one game. But I think most of the actual puzzle ideas have to come at least semi-intentionally, or the game will not feel very strong.
You have to know where you are trying to drive the truck.
I agree that there is such a thing as writing a program that is only intended to be kind of close to correct, and that this is actually a very powerful real-world technique when problems get complicated. But the assertion that type annotations hinder this process seems dubious to me. In fact they help be a great deal in this process, because I don’t have to think about what I am doing very much, and I will bang into the guardrails if I make a mistake. The fact that the guardrails are there gives me a great deal of confidence, and I can drive much less carefully.
People have expressed to me that functions without declared types are more powerful and more leveragable, but I have never experienced this to be true, and I don’t really understand how it could be true (especially in 2019 when there are lots of static languages with generics).
* How debuggable is it?
* Do most errors get caught at compile time, or do they require that code path to be exercised?
* How understandable are programs to new people who come along? To yourself, N years later?
* How error-prone are the syntax and semantics (i.e. how close is the thing you intended, to something discontinuous that is wrong, that won't be detected until much later, and that doesn't look much different, so you won't spot the bug)?
* How much development friction does it bring (in terms of steps required to develop, run, and debug your program) ... this sounds like a tools issue that is orthogonal to language design, but in reality it is not.
* What are the mood effects of programming in the language? Do you feel like your effort is resulting in productive things all the time, or do you feel like you are doing useless busywork very often? (I am looking at you, C++.) You can argue this is the same thing as programs being shorter, but I don't believe it is. (It is not orthogonal though).
* What is your overall morale of the code's correctness over time? Does the language allow you to have high confidence that what you mean to happen is what is really happening, or are you in a perpetual semi-confused state?
I would weigh concision as a lower priority than all of these, and probably several others I haven't listed.
It's just that modern software is garbage. That's all.
Are you claiming that a contemporary construction project would be able to build the Hoover Dam? That was almost 100 years ago and a lot of things have changed...
There's a fine art to setting the tax rate at a level that people dislike, but not strongly enough to do something about it, because the other benefits of being here outweigh.
That said, it’s not that simple. There are threshold effects (more than X amount of time = your company is dead) and intangibles (how do you feel while programming).
But anyone making a blanket statement without considering these things is participating in a dumb internet argument.
I am sure the company is messed up, but come on.
Not the right way to think about it; the connection latency is irrelevant. What is relevant is that you need to play audio in sync with the video, and that audio is coming to you approximately simultaneously with the video it's meant to be synced with.
As for your first example “you may be relying on a 3rd party service that compares things”, has this ever happened in the history of the universe?