I think a query language would be great, with a way to subquery/chain data from previous requests (e.g. by jsonpath) to subsequent ones.
The closest I’ve gotten is to wrap the APIs with GraphQL. This achieves joining, but requires strict typing and coding the schema+relationships ahead of time which restricts query flexibility for unforeseen edge cases.
Another is a workflow automation tool like n8n which isn’t as strict and is more user-friendly, but still isn’t very dynamic either.
Postman supports chaining, but in a static way with getting/setting env variables in pre/post request JS scripts.
Bash piping is another option, and seems like a more natural fit, but isn’t super reusable for data sources (e.g. with complex client/auth setup) and I’m not sure how well it would support batch requests.
It would be an interesting tool/language to build, but I figure there has to be a solution out there already.
Somewhat off-topic, but is there a tool which integrates something like this/jq/fx and API requests? I’d like to be able to do some ETL-like operations and join JSON responses declaratively, without having to write a script.
I made this web application to help me learn some music theory in real time whenever I stumble upon happy accidents such as chords, chord progressions, or scales that sound good, all without breaking the creative flow. The application can also fuzzy-find everything when I don't play the exact notes.
Written in ClojureScript and is a private/static site hosted on Github Pages.
We use this at https://languageroadmap.com, but for difficulty rankings between titles in the context of language learning using media. It does seem to work pretty well and we disclaim rankings with the confidence score.
As for the grandparent comment: recency bias, as pointed out by another commenter is a thing, as is the tediousness of doing a bunch of pairwise decisions. I think a happier medium is to have everyone fill in tier charts (with variable number of tiers) and build the pairwise rankings from that.
I’m learning French with reading/media too and realized media will never exhaust itself like beginner apps do. I wanted an open-ended platform to to follow that reasoning, so I created https://languageroadmap.com as a way to keep finding interesting target-language media at my skill level.
While there are probably some tools to do this, I'd suggest taking the plunge and just doing native subs (or no subs!). Part of the immersion process is being comfortable in being uncomfortable. Removing the crutches can be a big leap, but IMO our brains need it in order to progress.
If I have native subs, I find myself falling back on them and not really learning. Less information on-screen is also less our brain has to process, which is already quite a bit when learning a new language.
Also finding subs (and good ones at that) are frustratingly difficult, so finding a pair that is synced up sounds like quite the task!
Thank you for checking out the site and for the comment!
I'm happy to announce the release of a site I've been working on to help find immersion content that's engaging _and_ at your level (without sacrificing one for the other).
It's part-catalog, part-immersion tracker, and part-recommendation system.
Find content by genre/theme or media type (movie, TV, book, podcast, YouTube channel), add it to your library or bookmark it for later, give it a thumbs up/down rating, and rank its difficulty to help us build a global difficulty scale!
I'm happy to announce the release of a site I've been working on to help find immersion content that's engaging _and_ at your level (without sacrificing one for the other).
It's part-catalog, part-immersion tracker, and part-recommendation system.
Find content by genre/theme or media type (movie, TV, book, podcast, YouTube channel), add it to your library or bookmark it for later, give it a thumbs up/down rating, and rank its difficulty to help us build a global difficulty scale!
I'm happy to announce the release of a site I've been working on to help find immersion content that's compelling and comprehensible. It's part-catalog, part-immersion tracker, and soon-to-be part-recommendation system.
Find content by genre/theme or media type (movie, TV, book, podcast, YouTube channel), add it to your library or bookmark it for later, give it a thumbs up/down rating, and rank its difficulty to help us build a global difficulty scale!
Check it out, give it a test run, and let me know what you think (you can DM me any feedback or reply in this thread).
While this draws from mostly right-leaning concerns about higher education[0] despite claiming itself more open, I get the sentiment.
However, costs usually rank higher among concerns but they are not addressed that much in the article. I’d be interested to see how that will be addressed. New school might spend less on amenities and focus on accreditation, but professors still need to be paid competitively to attract and retain talent, and they will have to fight the uphill battle of falling state support[1].
Done mainly to learn latest React/Redux. It’s coming along nicely. Also hosted on GitHub pages as a type of progressive web app (https://cofinley.github.io/free-roam). I love the idea of offline apps where you bring your own data. Kind of like the Beaker Browser.
Thanks for the input. I plan on creating a version for authors too.
If it's possible in your organization or release strategy, self-deployment is good for the reasons you say, and it corroborates Larry Wall's virtue of hubris [0].
The PR author is like a salesman. You should be making the lives of your customers easier and incentivizing them to look at your product in order to move things forward. That being said, you should prioritize team profit and not your own (i.e. don't be a crooked salesman).
> you need to add as much formatting/linting into [step 1] as possible
Yes, project formatting is a whole other topic but this assumes the project already has the team's linting/formatting rules baked into the build. As a reviewer, we are pointing out failing builds here, whatever they may be. If there are deeper issues/disagreements with the build tasks, that would be a separate issue.
> Developers should be responsible for their own QA. QA is not what code reviews are about.
While I agree that each dev is responsible for their own QA and test should be run before opening a PR, two eyes are better than one. If checking the code out on local and testing doesn't take time and there is risk, then I'd say go for it. Catching changes earlier in a PR is less work overall than having to restart a large part of the process when QA catches them. Also see the link Smotko commented with [0], it also addresses your point.
> if proposed change is complex or reviewer want to visually confirm this change, feel free to checkout this branch
Yes, I specified that usability tests are usually reserved for PRs that introduce sufficient code changes and/or risk.
Author here. I agree with your point. The show is not only news but a political cartoon and most of my arguments could share the same criticisms that come with those formats.
However, I do think the show differentiates itself with the extra mile it often goes to act against issues (even if the call to action is small). It engages the audience further and I think has led to some misplaced idolization in a time where talk is especially cheap. From there, viewers' critical thinking faculties might start to break down and their biases, strengthen.
Thank you! I'm glad you see the benefit of a resource like this. And users can create the tools as well as the categories so feel free to add a DevOps category, as I'm not as well-versed on tools in that space.
Success is measured with time spent with the language. Find something that interests you at your skill level:
https://languageroadmap.com
and Anki for top 1000 words + sentence mining if you like flashcards.