For example, I work with a source of data that requires a particularly hairy JOIN strategy. The logic is the same for any table with the same “shape”, but no one can reuse it without copy / paste.

This - as a listener, quality is the hard problem. It is encouraging that the proposal affirms the value of curative functions (like labels).

As an artist, I actually don’t really care about music’s commercial problems - I’m more annoyed by the constraints on musical art objects inherent in all music platforms.

Like, experiencing art objects in a gallery hits different vs scrolling through bandcamp. The internet is, already, the gallery but it’s like we replaced all of the paintings with tiny prints, eclipsed by the placards.

The thing I would really love is a music platform that feels like a hosting platform, not a marketplace. Where a user can simultaneously act as a listener, an artist, a curator or a critic.

Comments URL: https://news.ycombinator.com/item?id=41362878

Points: 2

# Comments: 0

Improved UX at query development time is nice, but data teams need so much more than this. Stuff like lineage, linting, cross-dialect interop - these are no longer niche concerns, they are table stakes, and they come from having a shared syntax for data transformation.

These days, we have tooling that can generate an IR for SQL and transpile it to any dialect (see: sqlglot).

Doesn’t coupling SQL syntax to dialect-specific SQL semantics throw a wrench in this?

To get the freeform format with newer, “shinier”, and often more electronic sounding music, I also like NTS.

That being said, I generally don’t agree with conclusions like “culture is frozen”. You are correct that there is _more_ high quality material available than ever before. The challenge is just that it’s harder than ever to find it.

- The search space for music is really large and noisy. Most of the stuff out there isn’t very good, and the stuff that is good isn’t always discoverable with a single strategy - The best strategies almost always exploit human connections

Some strategies I use:

- Spatial locality, who is performing with or near artists that I like? - Publishing locality, who is on the same label as an artist that I like? - Artist locality, what other projects has an artist I like contributed to? - Fan locality, what other artists does a fan of an artist that I like enjoy?

——

Note that none of these strategies are as effective as “relinquish control”. For example, there is a freeform radio station near me that I listen to all day at work. I have a rule that I won’t turn the radio off in the middle of a DJs set, even if I don’t like a song. This has helped me “break through” to interesting artists I wouldn’t have discovered otherwise.

To the article’s question, I think the main factor here doesn’t have much to do with music. Cultural production has exploded, and it’s really hard to navigate any cultural space in a non-obsessive way.

I thought it was interesting that the effect of “generational preference for music released when teenaged” seemed to wane around Gen Z. I wonder if this is just exhaustion, perhaps with tendencies towards pastiche as a consequence.

Tools like this are helpful for:

- Rendering SQL in a consistent way, eg for snapshot testing

- Testing SQL business logic in CI against a dialect with less heavyweight dependencies

- Applying AST transformations to take advantage of dialect-specific optimizations

> Electric speed mingles the cultures of prehistory with the dregs of industrial marketeers, the nonliterate with semiliterate and the postliterate. Mental break-down of varying degrees is the very common result of uprooting and inundation with new information and endless new patterns of information.

[1] https://web.mit.edu/allanmc/www/mcluhan.mediummessage.pdf

Curious about why they were struggling with this workload on BigQuery. It just doesn’t seem like very much data. Maybe they were cost-constrained and using a tiny slot reservation?

On using a public channel for coordinating incident response, we have struggled in the past with stakeholders joining the meeting and offering well intended but ultimately distracting input during the incident. We’ve found it best to have one responder play the role of “incident commander” and manage external communication / rope in more stakeholders as needed. This helps avoid conditions that make the incident even more stressful, like say a member of upper management demanding frequent updates or spreading FUD.

I especially liked the phrase “chain of blame”

Comments URL: https://news.ycombinator.com/item?id=27337762

Points: 1

# Comments: 0