301 karma · joined October 31, 2016
Feels like the time is ripe for something like that, too. I think you're right, that would really up Craigslist's game.
Puzzmo - collection of daily puzzles, including crossword, really bad chess, and more (https://www.puzzmo.com/)
[0]: https://www.gameinformer.com/b/news/archive/2013/11/20/the-t...
Let me make sure I understand the point I think you're trying to make. Because people with DACA status were in violation of the law at some point in their lives, it's acceptable to thrust upon them a broken system? So, they deserve it? I just want to be sure because it sounds like you're saying it's acceptable for this system to mistreat or otherwise neglect a subset of people because reasons.
Setting aside the fact that DACA status is Deferred Action for Childhood Arrivals, namely, people brought to this country as children at a time in their lives when they could not have known what was happening let alone had the agency to say, "hey wait, have you tried the normal way to immigrate into this country, mom and / or dad?"
The point I was trying to make with DACA is that the system is broken, not because of long wait times for paperwork, but because at any point the entire thing can be taken away. DACA status has been threatened multiple times. Imagine living a life you didn't ask for, not native to the land in which you live, and not native to the one you were forcibly taken from, and living under the shadow of the threat of being forcibly taken back to a strange country. That's one part of the system that is fundamentally broken, and because these people are "in violation of the law", they deserve it?
The machine doesn't work unless the parts do. Or to quote Solomon Burke, if "one of us are chained, none of us are free."
It's easy to dismiss a single piece that doesn't impact your life directly. "Great! The illegals have a hard time with immigration. Maybe they should not have broken the law, then!"
But to many it is their entire lives, and through no fault of their own. It's this contentment with injustice elsewhere that's utterly infuriating and really shines a light on the privilege of some on this forum.
Not even going to touch the "economic migrant" bit. Sounds a little too close to a dog whistle to me. Not even sure why I felt the need to engage this much.
In any case, the instant you fall just a little outside the prescribed lines is when things start to get hairy. Have a talk with any DACA recipient and you will quickly learn how broken the system can be. Or someone seeking refugee status around the time the annual ceiling is being reached.
An well-designed API should behave so that you can fudge up whatever is happening behind the scenes, so long as the outputs remain the same based on the inputs. Design for consistency and idempotency. Implementation (read: behind the scenes) details are just that, details, and subject to change. If your implementation is tied to your interface, there are bigger problems and you skipped the Make It Right part.
While learning Thai -- which is a difficult language already -- I continually struggled with word definitions that should have been easy. How hard is it to remember the words for the various parts of your head and body? With just word definitions, apparently, it's really, really hard.
But then I supplemented this with other tools. One teaches a few words, then throw those words into full phrases in little quizlets. You pick out the written phrase which you think matches the spoken phrase. It always includes one or some of the words you've learned. It puts the words in context, cementing the definition, teaching you grammar, and "foreshadowing" new words. It's skyrocketed my retention and comprehension.
Pictures also help. Children's books with audio narrating are huge.
I guess my point is, Anki with word definitions alone is definitely garbage, or less than ideal at best. Which is why most language learning resources stress that it alone isn't enough - and most learning resources who push Anki (or SRS in general) don't say "do only this." It's part of a balanced breakfast, so to speak. Incorporate it into your workflow, but don't make it the workflow.
I think you're right. Recently I spent a bit of time writing about and playing with various shuffling algorithms, trying to see if I could find something that works better for me than the built-in shuffle.
The answer is: it's hard! An algorithm that works for a well-distributed set won't work so well for something with large clusters of similar stuff (think a mixtape vs a playlist consisted of a dozen albums from six different artists). And even when you think you've come up with a good solution, it works well six times, and then the seventh you start to find something that doesn't work quite how you like. It's a process of tweaking.
My final test case was a large playlist like you describe, since I have a few of these, too.
This is what I found worked best for me:
- (Optionally) Fisher-Yates shuffle the whole thing, then - Slice the playlist into X chunks - Shuffle the order of the chunks using Fisher-Yates - Analyze the contents of the chunks - Pick a suitable shuffling algorithm based on the contents - Shuffle the contents of each chunk
There are lots of details around things like, how recently was this artist/album/compilation played? What's the relative tempo or genre of the most recent X songs, and how "harshly" are we willing to change it up? Is this a playlist with a lot of disparate songs (by artist/album/compilation) or is it a collection of like-minded albums and artists? Is the playlist just someone's discography? etc.
It takes a lot of passes and a lot of listening to find and tweak these things to find something that works and feels good. And in the end, I don't think the people who can do this are incentivized to actually do this. Especially considering the linked Spotify article is an entire decade old by now, and the Every Noise at Once guy was let go seemingly at random by Spotify. They care about "good enough for now" more than Actual Quality.
[0]: https://www.sqlservercentral.com/stairways/stairway-to-t-sql...
I don't appreciate this assumption; lumping me into a group of characters based on nothing I've said / something you have assumed, based on no evidence, is quite counterproductive to a healthy conversation. If you're going to try to make an argument at least base it on the content of my post and not some inference you've made based on nothing I've provided.
I'm sympathetic to your situation, and do wish you the best in staying on your feet. And I am quite, quite far from a capitalist / capitalist-apologist / what-have-you.
It sounds like you're talking toward using AI tools to effectively "duplicate" yourself, to reduce the scarcity of your own time. I hope I'm interpreting that correctly. I'm 100% on-board with letting the computers do the work so we can all go off and enjoy our lives. It's dismaying that "productivity increase" means "do more in the same amount of time" instead of "do the same in less time and then go live."
This is still a far cry from duplicating the creative work of others (cloning a performer's ability, potentially for profit), and it's still got nothing to do with actual "artificial scarcity." Again, this is real scarcity. There are only so many hours in a day. You only have so much brain power to expend within those hours. These aren't pro-capitalist statements and I'm not insinuating that anything follows from them. I'm only being pedantic here. :)
That's... not artificial scarcity. By definition (and using your own words) it is actual scarcity.
A person's performance -- which is more than just their voice reading lines -- is not held back behind some imaginary wall. It's literally limited by the hours in the day, the person's ability to get from place A to place B, etc.; it's not like David Attenborough is a Santa Claus figure and can be in California narrating a documentary and in New York providing some random dude a personal voiceover for his life simultaneously.
Probably, but I hope not (or at least not for long).
I think it's normal for people to want to retell stories (see the way we pass jokes around like viruses, or the oral tradition, or the million "re-imaginings" of classics). I also think that inclination has been weaponized and turned against us. Producers -- movie, music, or other -- push or are pushed to maximize gain while minimizing risk. And what feels better than nostalgia? What feels better than a story that doesn't challenge you, doesn't prompt any sort of introspection, or hell, any inspection at all?
I think it's a symptom of the push for profit over all else. I do think we ache for new things, but the ship of monoculture is a big one and takes a long time to steer. A lot of momentum is behind where we're at and it's going to take a lot to get away.
I point this out because I think the idea of comparing ourselves to recent tech is more about using the technology as a metaphor for self, and it's worth incorporating the other ways we have done so historically for context.
[1]: https://online.ucpress.edu/SLA/article/2/4/542/83344/The-Bra...
[source]: https://www.hollywoodreporter.com/news/general-news/tvs-new-...
This is in Firefox; I haven't looked with Chrome.
If it's general gamedev resources for C#, then I would suggest Cynthia McMahon's Eyes of the Dragon series[1], for C# / Monogame. It goes through topics like input handling, drawing, tooling, etc. A thing I like about this as well is that it's not "perfect" off the bat -- an entry later will return to code written previously and talk about its benefits and drawbacks, and then refactor that code for a new goal or sometimes to just make it better. If you're new to C#, development, or game development, it offers a good perspective into what doing this "for real" looks like.
[0]: http://sadconsole.com/v8/articles/tutorials/get-started/draw...
[1]: https://cynthiamcmahon.ca/blog/category/eyes-of-the-dragon/
Much better than Spotify, which only ever "recommended" artists I've already listened to, or artists I didn't like, or genres I didn't. If you listen to a wide variety of music, it doesn't know how to handle this apparently.
Remote: Yes
Willing to relocate: No
Technologies: C#, SQL + SQL administration + db design, Javascript, VueJS, Python
Résumé/CV: Real thing on request; summary: two years of professional development experience with several years prior of informal experience (writing code as QA), a few years of analyst and IT work, and before that, some more years in freelance web development & design (nearly 10 years ago).
Email: tallain@gmail.com