gpantazes

The petition does not have "District of Columbia" as an option for "In the US".

Bash Hackers wiki is unavailable. The domain name has expired.

I noticed that the default /etc/hosts file has a comment saying not to alter the localhost.

   # localhost is used to configure the loopback interface
   # when the system is booting.  Do not change this entry.
   ##
   127.0.0.1       localhost

This article on dscl (https://tomafro.net/2009/07/dscl-the-easy-way-to-add-hosts-o...) is one such finding.

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.

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).

[1] https://chris.beams.io/posts/git-commit/

I use PlantUML[1] for my UML diagrams.

  - 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]

  [1]: http://plantuml.com
  [2]: https://plugins.jetbrains.com/plugin/7017-plantuml-integration/
  [3]: https://plugins.jetbrains.com/plugin/10387-sketch-it-
  [4]: https://bitbucket.org/pmesmeur/sketch.it/src/develop/
  [5]: https://mermaidjs.github.io

I'm guessing MYOB => Mind your own business.

Wouldn't it be interesting if we didn't get the same level of pesticides through meat & dairy? I think it's worthwhile information to point out.

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.

"I implemented this using some technology that abstracted away the server configuration, but it is running on a server... hmmm"

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.

I hated this about CoronaSDK (how the framework would render everything like a game engine to one canvas). It was so much harder to debug things if the only way you can debug components is only within the scope of the framework, and you don't have any of the benefits of using the native views/containers. This means you can't effectively use Appium or UIAutomator or anything nice like that. If Flutter does render everything like a canvas, then that will pretty negatively affect my impression of it.

I think it's less a calculated act of hostile design and more of a Hanlon's Razor moment; a manager says "It's working so it's good enough. We won't work on that because it's not a priority right now." I don't think the companies have enough time and energy to purposefully implement dark patterns.

Was the bokeh functionality using software to create an artificial depth of field effect, or does the camera capture a range of depth of field? My immediate guess was that it's actually clever software, but was it confirmed either way?

So what I'm hearing is the solution to this migration problem is to also store the entire issue tracker as a git repo alongside the real repo and wiki repo? Git repos for all the things! (Seriously, I think this solution would fit right in along with the way Wikis are handled)