If anybody has suggestions about the best way to add hostnames for testing/override purposes, whether that's /etc/hosts or something else, please comment with your favorite.
As a Duolingo user, I am pleasantly surprised to find this site today. This site seems to ~~solve~~ mitigate problems I've been having with tips (or more accurately, lack of tip accessibility on the iOS app for certain languages).
To be honest, I've never really thought about viewing all tips on the same page, although that is very convenient. A fine feature that should probably be adopted by Duolingo as well.
The convenient one-page format ~~solves~~ mitigates a different issue I've been having lately though. Duolingo doesn't consistently publish (existing!) tips to all Duolingo frontends/apps. Well-supported languages get the best tip-content support, but languages that aren't as supported sometimes don't have tip present even if the tip content exists.
For example:
- Duolingo Web always has tips if tip content exists. This acts like a source of truth, as far as I'm aware.
- Spanish is a language which has tip content both on Web and iOS. I believe this is because Spanish is popular and well-supported.
- Greek is a language where tip content is not accessible via the iOS app, but is present on the web site. I believe this is because incorporating the presentation of tips is probably some hardcoded markup thing (React?) and nobody has gotten around to doing it yet. Also, there's a possibility that the underlying documents need different rendering treatment or style enforcement, and have been omitted from the mobile app on purpose. Still, this is a thorn in my side.
So for me, a one-page-tips fills a gap in the Duolingo UX (which should probably probably be fixed on Duolingo's end since this simply seems to be a prioritization/maintenance/time/effort problem).
As a user, I'd like an easy way to refer to the tips before each lesson without pulling up the actual Duolingo web app - otherwise, why don't I just do my actual lessons on the web app as well? Usually I'm doing lessons on my phone, not my computer, because the phone is not only more convenient (small) but it's easier to change keyboards and type in non-latin alphabets.
To me it seems like Duolingo is doing a lot of A/B testing, but in a really weird manner. I was also annoyed by not having access to language tips in the mobile app, while they were available in the browser. I also have a friend, for whom the whole app changed after reinstalling: they didn't have the heart system before, now it was on; the gem system changed to gem of a different value, while prices in the store stayed the same. They always had notes on every platform in every language though.
I use these 7 git commit message style rules [1] to establish my foundation of "committese". Things like "Use the imperative mood in the subject line" give commit messages a succint, consistent style.
Everything after that is finesse, personal effort, and ability to express things succinctly (much like the personalized "headlinese" styles mentioned).
- It uses a human readable text-based file format renderable via the PlantUML jar. Friendly to CLI and git.
- The diagrams are stylable, should you wish to style them.
- There's a PlantUML Integration IntelliJ plugin that's easy to use for preview/rendering[2]
- Overall simple to use, but I imagine it can as robust as you want it to be. For example, the IntelliJ plugin Sketch.it automatically generates PlantUML diagrams from Java source code[3], and the source code for how it works is available on BitBucket if you want to know how it works[4]
I've seen other people suggest Mermaid.JS[5] before, but I haven't used it so I can't say how it is.
I'm just trying to suggest ways to make it easier to read the comment. I suggest you read comments giving the poster the benefit of the doubt, you'll probably be much happier than telling people to bugger off.
The PlantUML Website used to look like you were about to download a whole bunch of malware into your computer, but the software is really great. Diagrams are simple text files that are then rendered by the tool. This frees you from having to drag and drop circles and arrows into an editor, and allows you to easily version-control your diagrams.
Software Engineering Daily was the first software podcast which, for me, sparked my interest and delved into technicals but also explained the simple things. At the time I was feeling rather like a novice even though I had a BS in Computer Science, but this podcast really got me excited and made me feel like I was learning what was out there; what was possible to explore. While I still don't understand everything, the broad sweeping topics are great for sparking certain ideas or improving overall understanding of software engineering topics.
The distinction here is that the links you've posted are from the browser console line, while the tool in question can take screenshots from the terminal/command line (sans browser, can be automated).
Firefox and Chrome, and most major browsers can indeed take screenshots from the browser _console_, but taking screenshots from the command line is a separate, interesting concept.
