i can't think of any case where exponential growth actually happens, though. exponential decay and logistic curves are common enough, but not exponential growth
316 karma · joined March 23, 2013
i can't think of any case where exponential growth actually happens, though. exponential decay and logistic curves are common enough, but not exponential growth
those gamers often have strong emotional attachments to games/characters that very few people have for google sheets
studios get crazy backlash for nerfs and other changes, so i can see not wanting to attach your name and face to that. in the other direction, i wouldn't want a horde of gamers using my words as evidence that my employer is dogshit, unless that was the goal of my message
one of those groups is entirely contained within the other. contrasting them like that, and being judgmental about the latter, isn't going to be a popular opinion
the set of people that both agree with the class analysis approach, and are fine with the fat shaming, is very small
so rich obesity sufferers are getting it before poorer fat people
although maybe i'd get bored and run the heater and the AC at the same time
i always liked the immediate-mode UI in unity. some people can't stand it, so i can see that being the reason
for private companies, it literally is the people you work with (and whatever legal enchantments they've decided on). some of those people will still fuck you over, but it's not a legally-conjured sentient pile of money the way a C-corp is
B-corps are an interesting attempt to avoid being a sentient pile of money. in theory, it's an egregore that is capable of valuing things other than money. (they haven't really been tested in court. and they might fuck you over in pursuit of some other value, even if they do work. or fucking you over for money might not conflict with its other values)
got me out of a gaslighting relationship, and allowed me to stay at a company during a rough patch (knowing i had a line i'd bail at)
the more volatile it is (and the less you've mitigated the risks), the more expensive your insurance gets
https://www.jsoftware.com/ioj/iojATW.htm
i tried this style for a minute. there are some benefits, and i'll probably continue going for code density in some ways, but way less extreme
there's a tradeoff between how quickly you can ramp up on a project, and how efficiently you can think/communicate once you're loaded up.
(and, in the case of arthur whitney's style, probably some human diversity of skills/abilities. related: i've thought for a while that if i started getting peripheral blindness, i'd probably shorten my variable names; i've heard some blind people describe reading a book like they're reading through a straw)
that said, a tutorial to turn the shipping box for your laptop (or a flat of diet coke) into a stand would be good. useful in a pinch
edit: keyboard box might be the best box to print the fold lines on. you need that for a minimally ergo laptop setup anyway
(on windows, you'd need to handle this with VirtualAlloc. osx and linux let you overcommit with malloc, and handle it with a copy-on-write page fault handler)
this is for a stylus, but people can detect input latency as low as 1ms (possibly lower)
with VR, they use the term "motion to photon latency", and if it's over ~20ms, people start getting dizzy. at 200ms, nobody is going to be keeping their lunch down
google noticed people making fewer searches if they delayed the result by 100ms
edit: if you want an easy demo, open up vim/nano over ssh, and type something. then try it locally
the (forced) licensing deal comes after the development, and hinders it. and it's not to protect development of a related idea, either
if a company sells it to a broker, and it eventually gets traded or licensed to a company that develops it, i'd also consider that working as intended
if patents keep finding their way to companies that have no intention to either develop it themselves, or license it to others, and keep suing companies that do develop things, i'd consider it a failure of the system
pharma patents get traded to non-developers all the time, but pharma patents mostly do their job of incentivizing innovation. there's still flaws, but the troll problem isn't a big issue in that space
if a company doesn't develop products, but they actively license their patents to those that do, that's still patents working as intended, and not trolling. they're still helping to get the tech developed, rather than stifling it
(i think there are a lot of problems with software patents even when used as intended by real companies. mainly, they last too long)
unbiasing/re-biasing a lock can be quite heavy, though. JVM did it by pausing threads (or waiting for GC to do so)
there are a bunch of cases where the simple economic argument is more thorny (like food). "pay to meet someone famous" is one of the least thorny cases i can think of
hubris: the quality that makes you write (and maintain) programs that other people won't want to say bad things about.
once you ship, you don't really need to maintain it the same way as other software. tech debt is free money if you ship before having to pay it back
and players often like complexity and interaction between systems, so there's less benefit to isolating them in code
but, "best-effort" implies that it's doing some effort to ensure delivery, when it's really dropping any packet that looks funny or is unlucky enough to hit a full buffer
i like "lossy", but this is definitely one of the two hard problems
if you inline the red nodes into the black nodes, you get a 2-4 tree node. except that the 3-nodes have chirality. but then, you can just use a 2-4 tree
AVL trees seem not worth learning. they have slightly different performance characteristics than red-black trees. but, if i care about performance beyond big O, i'm probably using a hash table or a cache-aware tree of some kind instead of a CS101 data structure
there's a section on memory allocation patterns
i believe casey muratori talks about allocation patterns in the handmade hero video series, too
edit: ryan fleury has a talk: https://www.rfleury.com/p/enter-the-arena-talk
but it's not batteries-included, and that's often to be a deciding factor at small scales
i think if you're going to dabble in engine dev, you pick which one you want depending on which part of the engine you find interesting. if you want to make a game, you pick up unity or godot or something
in most games, there are about 3 "lifetimes": - permanent/startup - per-level - per-frame
and they're nested. so, you can use a single stack allocator for all of them. at the end of the frame/level, pop back to where it started
there are more complicated patterns, but this one will get you pretty far. you can use it on the CPU and the GPU