The publishers have a weaker hand to play today, since it's easy to go to market with minimal marketing and distribution spend, but that has the side effect of making it more common to see tiny studios that run a sweatshop churning out bad products.
252 karma · joined October 9, 2018
The publishers have a weaker hand to play today, since it's easy to go to market with minimal marketing and distribution spend, but that has the side effect of making it more common to see tiny studios that run a sweatshop churning out bad products.
I find an increasingly strong case to be made for going the community-college-then-transfer route since it brings together a bunch of points that affect most students in some fashion:
* Cost(obviously)
* Transitioning to independent life(less pressure to be a study machine rushing through the degree)
* Indecisiveness about career and motivations(easier, less stressful classes)
Going to a "tough" or "prestigious" school allows you to tell a certain story about yourself, but it usually doesn't lead to well-roundedness, which sets the stage for that common story of a high-achieving student who gets on the perfect parent-approved career track and then abandons it - whether in the middle of the degree, shortly after the first job, or after a few years of work - due to burnout.
Every once in a while I imagine something anxiety inducing about them, or catch a glimpse(and more often than not a positive one) in the automatic reply emails Reddit likes to send me. Sometimes I will look back at the thread, if I really want to know.
But I don't use these platforms to converse, even though I will happily make a reply to an existing thread. They are both too fast and too slow to be conversational. I use comment threads as a writing prompt instead, and by ignoring external feedback I don't experience pain from them, even though some of the time this might result in someone asking me something and never hearing a reply. If my idea is good, someone copies it and I see it in a later thread.
With an investment in a game, you pay for the game and the equipment once, and can then have a multitude of experiences with no financial consequence. Negative elements have been guardrailed and smoothed out for you into minor irritants, allowing you to get through a day without experiencing stress, panic or anxiety even if your mind and mood are at a low level of resilience.
What games often don't do is guide their players back into views and habits that aid in overall life satisfaction. Most forms of human development involve struggling with more and more things - but in a liberated sense, where you are taking it on because you want to grow and challenge yourself. The escapist fantasy can't do that - which doesn't mean they shouldn't exist, but society is conflicted with how they should be used.
The alternative is that I spend the first hour of the day in the way that I spend the last hour of the day, in front of a screen. Which doesn't seem to work well for me.
What this means in practice is that we have a lot of software that makes it easy to bring a group of strangers in to pseudonoymously vandalize a whiteboard by drawing dicks on it - a true "cacophony of monologues." See also: most comment threads.
Except that it makes a point that is subtly different from the one pg originally raised in discussing Blub paradox: If you only care about shipping something, you aren't inclined to think about abstraction as a goal state, and that's what these other languages are doing: handling things with a goal of adding abstraction that for a C++ user is out of reach or requires considerable knowledge of the C++ standard. Users of Python or JS don't know what a pointer is, and that's intended by design, because for most applications it is an implementation detail and automating it away is desirable.
When most software was written in assembler, data structures more complex than an array were often avoided, because it was difficult to code and debug them. And if you were an assembly coder of that era, you might well say that you didn't see the point of structured programming, or that you could easily get the same effect in fewer bytes. And to some degree, you'd be right, because you would just design a smaller scope of application that makes those techniques viable.
Trying to write something resembling modern C++ style in x86 assembly, in contrast, would be as fruitless as a JS coder trying to use C++ like JS, since your abstractions wouldn't be there. You'd have to learn the thought process of a lower level coder and apply those strategies instead of the ones you are comfortable with.
As of right now I have these thoughts:
* I think the focus on crypto could be a long shot, because my observation is that it's premised on capturing the notoriously fickle dev tools market...
* ...But in the end, Red has to get into a niche and own it and the team is, as some in this thread are suggesting, fanatical enough about what they're doing and confident in its strengths, that they are likely to go farther than anyone else had considered. Which is good enough to make me speculate on it.
* Although Red produces some great demos right now, the lineage of Rebol has its downsides too, since with a lot of these demos, when you get past the trivial and start customizing the UX in fine grain detail, a brick wall of unconventional paradigms is exposed which means that even if I'm experienced in other systems, I start needing a higher level of documentation and handholding. This is not an issue exclusive to Red and frequently impacts software libraries, but one way in which a lot of projects cheat on this problem is to emulate an existing API with lots of adoption and say, "Look, we're the same!" And then they don't have to document, they just steal the existing users.
* Regarding the pace of announcements, there's a rule of thumb Valve worked out for updates of Team Fortress 2 years ago(discussed in one of the articles or talks from then) that I see as more-or-less applicable to all software: Roughly every two months, make a large release with a detailed summary narrative. Project news is a great marketing tool when it's sized like this. Smaller releases tend to not make headlines, larger ones don't have a larger impact. So that's a proposed benchmark for what Red could be doing. The fact that this post blew up is a sign that something is going well, though :)
The most important thing for me is to put dates, and sometimes times, on things. The second most important thing is, when I have a brainstorm, filter it into a coherent[0] set of ideas right then and there. My previous "idea generation" strategy held on too long to ideas that don't cohere. As a result I had many ideas that didn't go anywhere and weren't memorable. Making a coherence is much more powerful, since it creates a web of ideas that catch other ideas. My "hit rate" has improved a ton since I changed strategy.
But then they swapped it out for another mode yesterday and I got pissed off by the hitscan and sniper weapons(which of course are the preference of cheaters). It was a much less satisfying experience.
I've heard this about marketing other media: that it's hard to target older audiences because their tastes diverge more. Teenagers remain teenagers each year, and will reliably fall for the same scenarios and stories with a fresh coat of paint. And I don't think games are any different, in that games where you shoot things, go on a quest or adventure, solve puzzles, gain power and wealth, and compete against others have all been reliably popular in every era, in a multitude of permutations. A popular, accessible video game has to have an appropriate mix of fantasy (what you imagine you do) and reality (the actions you actually perform which should cohere with the stated fantasy). A mismatch of the two makes for incoherent gobbledegook.
So the challenge game developers face(and aren't fully aware of, since most folks trying their hand at it are still young game fans themselves) is in doing something that's actually differentiated while maintaining a compelling marketing message. If it leans too much on the usual tropes, any kind of underlying design wizardry is obscured. If it looks too "weird", it becomes hard to engage with on the level of fantasy.
After getting annoyed with Fortnite last night, I sampled a few other recent games. First I tried free-to-play "Dreadnought", in which you control a giant spaceship in slow-paced team battles. I got annoyed immediately by the opacity of the strategy: it threw a bunch of different classes of ships at me and told me to pick one and not worry, basically. The game was bulked up with systems upon systems that were clearly intended to hold my attention for the long term, but without knowing what to focus on, and not really feeling the core fantasy in what I had right in front of me, I just played it like it was homework and then stopped after about an hour. This is a very typical reaction I have to AAA experiences: they're overconfident in their ability to stall me by leaning on levels and unlocks and item loadouts and so forth, instead of communicating something about how I should start appreciating the game.
Then I went on itch.io and after browsing tried "Skitopia", a ski resort management sim. Even though it's an indie project at a proof-of-concept level of development, has almost no features and started experiencing GC thrashing after about 50 guests, I was having a good time building chairlifts and ski runs.
Indie games would be amazing if they could all just hit the mark like that, but that's the exception, of course. Most of them lose their way in trying to be mini-AAA experiences, so they both communicate nothing and do it poorly.
So, instead of envisioning it as "5 minivans vs 1 bus", it's a system that smoothly transfers you from street to car to bus to train to plane and back. You get the "now" of low latency, and then you transfer up a step to get speed and efficiency.
Right now we have very primitive notions of multi-mode: every transfer is time consuming and difficult on the psyche, often involving new fare systems, security checks, navigating transfer points, delays, tolls, parking, and so on. This is a big factor in our tendency to bias towards a single mode and overbuild infrastructure for that mode.
Portable electrics are a big step forward in moving up the baseline: they're roughly person-sized without too much additional weight. An imagined standard for docking them in a larger vehicle or running them in a convoy is not too far-fetched, but will probably still take a lifetime to be realized with all the involved political factors.
Look up "Thinking Forth" for more in this vein.
But I usually go with onboard sound these days. I did get a FiiO E10K when I got new headphones recently, but I've put it away even though the sound is noticably smoother and less compressed-sounding than my onboard sound - it's another cable and associated hassle.
The reason to go for pricier stuff in my mind is to get more I/O. Good audio interfaces for recording can run you hundreds, and you're paying there mostly for having more channels and some recording features. There's more of an expectation of getting what you paid for.
The key for me is that it's not about the format. The format changes with the context: I have a different logging strategy for fitness(Fitnotes app, and since I was just gifted one this past week, a Fitbit) from the logging used for programming notes(repetitive short block comments with date, time, and sometimes title). I have a generic diary text file that contains catch-all musings, but I am increasingly using different logs for different tasks since I don't currently face a lot of time contention that would necessitate a detailed calendar.
My logs are not just what happened but also what I wanted to happen on that date. I'll often copy-paste the same to-do list when I didn't finish it that day, or "redraft" the same thought an hour after I first logged it, with some elaborations. Keeping it around, I learn what is or isn't working at a glance by skimming over these repeats hours to months later.
Having the date and time is essential to this because it makes the log a progression: my recent activity is my most important, most of the time, and so in the case of the programming logs, I can gradually edit and eliminate them as the code changes and the momentary thoughts of "I need to do this next" grow irrelevant, while if it's something like a log of weight/reps/sets, I just want to copy, increment the numbers a little higher, and add a note about anything weird that day that may have made me change plans.
When I really need freeform notes I will turn to paper, and I can see bullet journaling techniques being worth trying in the future for adding some structure to those. As long as I have dates I can usually recreate the context of any particular note, though.
Something I just thought of: is there a browser extension that would automate logging my history when I want to research something? That's a pretty common task that I currently address manually with a lot of right clicks and ctrl+C's.
I will stick with my D3 supplements, TYVM.
That said, the benefits of scaling up runtime game performance are diminishing as asset costs increasingly dominate the discussion: the extra scene detail comes with a price to the production cycle, and that may be what breaks the games-graphics-tech alliance before any fundamental limits to the technology are reached.
Before you have the features, you mostly want to find the boundaries on the problem so that you can slice it up into modules and optimize those independently. It's unusual in contemporary programming to have to do a whole-program micro-optimization pass, but that's the only kind you can do within a small program, so it's common to get the wrong idea and start shaving off bytes and cycles before the architecture is ready for it. In a large program, it's specific combinations of features that create performance spikes, and those tend to be addressed by building a new custom code path. When you scale up the data changes, so your view of the problem changes too, and you start being able to optimize by creating a codepath that combines a whole bunch of specific processing steps.
Go through Knuth AOCP. You don't have to work every problem(nobody really does) but the book is there to point you towards fundamental computing concepts.
Strip down your language in the process. If you're used to something bulky like C++, try hopping over to Go or Lua and see how you like those.
Finally, throw out any abstraction and try coding in a primitive way for a while: use basic loops, arrays, and rarely a function call. Hold off even on defining structures with fields. Doing this will get you in the appropriate mindset for solving real problems, because it leaves no room for burying the design underneath the abstraction - you just apply one algorithm after another and rely on good commenting to know what it does.
Aim to read more code from real projects, open-source ones that people are using. Good code that is in production mostly contains necessary complications. It often doesn't do things in a fancy, code-challenge style or a style that takes a performance optimization because it is aiming only towards surfacing the feature as quickly and reliably as possible. That is a good goal to aim for with any real project.
And Go is just a little bit closer to the sweet spot than C was, since a greater proportion of Go code seems to successfully avoid extensive preprocessing.
On the other hand, it might be a bit too restrictive for prototyping to have these power limits. I definitely have an easier time feeling my way through an unknown data modelling problem if I can start slinging things together dynamically.
1. Automate for spec and quality first(make it work, get it right, make it fast)
2. Add opt-outs(write to the limits of your debug system, apply the Principle of Least Power, use common formats and protocols)
3. Automate the easy parts first and limit scope(short build scripts, mockup UI, placeholder systems, set scalability targets, etc.)
Software projects are ultimately about the full automation of a complex data processing task. The difficulty is in learning enough about the problem and knowing where to set boundaries. Writing software that "does anything" is one of those philosophical black holes that is easy to fall into in small increments, because the system can surely always do more, and you might have a library that solves 90% of the problem...
The actual computations around what changed can be pure, but turning them into a concurrently operating loop is done most effectively with a static sequencing(and hence, straightline imperative).
Or in other terms, he is using a different strategy for different parts of the codebase. At the top level it's imperative, but when you drill down into the callstack, it isn't.
A lot of folks work on request-response systems all day, and in those, the necessary state changes tend to be once-per-request and wrapped in transaction or session logic. So it's a lot less crucial to have this kind of strategy for debugging purposes.
What separates the high achievers, apart from any basic talent and training, is a personality that doesn't experience the relevant kind of pain or discomfort that would discourage them from the task.
For a lot of sports, that means overcompetitive asshole. For a lot of businesses, the same. That personality gets a lot of leeway to optimize towards linear goals. But then you go looking at certain niches and there is nuance. Sometimes it's endurance - masochism. Someone who runs ultramarathons, or repeatedly starts over a speedrun of a classic video game. Sometimes it's a poker player or day trader who can't feel the weight of moving around big stakes. There are many roles where the successful personality isn't the competitive narcissist. But in the specific case of small companies that get very big very quickly, they are prolific.
And that's a point which helps me personally, since I know some things about my comfort zone by now and where the standard advice is going to fail. Only some people are numbed enough to simply "hustle" and succeed. For the rest it's more like a quest to find the right kinds of challenges, the ones that they are most likely to engage with at a high level. When they can do that, people call them a genius. But from their own perspective, it's ordinary, or only somewhat more painful than doing nothing. And this quality of personality matching a high level skillset runs throughout our fictional characters, despite Western society nominally engaging with beliefs of anyone being equally able to learn to do anything. I think we know this and turn our back on it because it uproots several of our major founding myths about society and its potential and whom we should support and how.