elondaits
Joined 7 years ago
Joined 7 years ago
Judging something and understanding something are different processes. The RAE creates guidelines, but people often speak and write without following them, and that's still worthy of examination.
That x is generally pronounced as an “e” in Spanish (i.e. “latine”, not “latin eks” or “latinks” and most certainly not “latinj”, as the j sound of x is only before a vowel, e.g. xavier = javier).
But why write an x and not an e? Because there are consonants that change their sound with an “e”. So, say, the word “chicos” (boys) and “chicas” (girls) would be written as “chiques” in neutral because the c sounds like an s and not like a k with an e in front… but “chiques” doesn’t look like “chicos”… visually it’s not recognizable… while “chicxs” is much easier to parse.
This is how it works. I don’t care to enter a discussion of whether this is nice or not, good or bad. I’ll just leave with the anecdote that I once participated in a project that involved a big survey written in the traditional “neutral” form, which consists of writing “chicos/as” to covers both binary genders. That form quickly becomes very hard to read… “Los chicos/as están sentados/as con sus nuevos/as compañeros/as”. Use of the x has a lot of pushback from some people, but all in all, it’s easier to adapt to.
The loudness war wasn’t about normalizing to 0db vs -3db, but rather about dynamic compression which is a process that raises the volume of softer sounds without affecting the loudest ones as much (or at all). It’s what you use to make the breathiness of a singer’s voice, or a drum kit’s hi hat, more present in a recording.
... but I'm not too bullish on an AI having "taste" because the reason people have taste and a POV is because they're living life. Artistic choices are the consequences of past experiences and associations we make unconsciously, which result in a patchwork that holds meaning. A "great AI" would need to imitate that, and maybe they someday will, but we're talking about imitating embodied experience and thousands of sensory impressions that we normally don't even bother verbalizing, or writing, but as humans are able to transform and share.
- The main issue with AI posters and flyers is almost uniform information density. They read as "too crowded". Posters should, like photographs or paintings, have a rhythm where some areas are high density and others act as negative space, and provide a more restful transition between information areas.
- The icons as bullet-points are a big AI cliche, and for the most part useless. Nobody needs an icon of a cupcake to understand what "cake" means and most of the other icons have no clear interpretation. Icons are only useful when, by themselves, communicate the idea (like the typical toilet icon). It's telling that every poster includes them.
- AI is not brave enough, or wise enough, to leave some blank space. Blank space is the #1 design resource.
- Font and visual style should not be arbitrary aesthetic choices, but rather motivated ones. They could relate to the event or the place through its history, culture, biome, or through the utopian vision of what the organizer is trying to bring to life. There should almost never be a legitimate choice between "Should we use Japanese, Punk or Kid-drawing style?"
- Being honest, earnest, truthful, is better than being cool.
- If a poster for an event calls your attention you can scan for the date, time and place. They will be there somewhere. But before you get there, there'll be important questions: "who organizes this?" "who is this for?" "what's the vibe going to be like?". Only a few of the posters try to partially provide this information through very small sentences (e.g., "A day of music, making and family fun")... but it's hardly enough. In my opinion this is what 80% of the time designing the poster should be spent on... looking nice and "professional" won't inspire trust or create commitment.
I built locally for many many years and I’m much happier with this model since the commit log is a much better reflection of what changed and there are no inconsistencies as whenever you’d commit source and built artifacts that don’t match.
… It demands some extra care in terms of making sure the server can pull the dependencies and run the build scripts, but that also means my colleagues (or me in the future recovering the project from the repo) would be able to build with what was commited and nothing more… which is a requirement in my case.