sparr0

In my experience, autocomplete/intellisense/LSP/etc is very difficult to get working on most codebases if you aren't already intimately familiar with how that codebase / language / framework / etc works, or someone with that familiarity has laid out exact steps for your IDE.

When I see someone using these features as part of their workflow, I semi-confidently predict that they spend the majority of their time working on a single codebase, such that the time investment to get everything working was worthwhile.

If, like me, you work on multiple different codebases most weeks, it rarely makes sense to even try setting those things up.

  Location: Boston(ish), USA
  Remote: Preferred
  Willing to relocate: SF, LA, NYC, Seattle, Chicago, ...?
  Technologies: Python, Go, C++, bash, Lua, etc. Terraform, CloudFormation, Chef, Puppet, Ansible. AWS, GCP. Docker, Kubernetes, containerd.
  Résumé/CV: https://drive.google.com/file/d/11QKYWGj4TbZW_k09ZM2xSVCOg7Hqnq0k
  Email: sparr0@gmail.com
  Github: http://github.com/sparr

The video makes it much more clear.

You should be using automated checks to keep credentials out of your repo, not relying on individual developers. And those checks can have explicit exceptions for known safe/public/test keys, just like you might explicitly allow testing or fake credit card numbers.

I reformatted and uploaded the game to a US-based print on demand game publisher. If you can't print your own and need a copy before the author has them back in stock or don't want to ship from the UK, here you go:

https://www.thegamecrafter.com/games/the-unix-pipe-card-game

Full disclosure, I will make about a dollar from each purchase.

I wish you well, and wish I had money to invest. When you grow enough to be looking for devops engineers, or sooner for just software engineers, look me up?

The Github license requires a waiver of the requirement of attribution insofar as such waiver is needed for Github to do what it already does e.g. as the license indicates, provide search results without attribution.

The whole problem is that I, as an uploader of code that I did not write, do not have the authority to make that waiver.

Is there room here for some sort of industry body or label group to promote a "Works Offline" sort of brand, like organic and kosher food labels? Device makers would get to use the logo if their device wasn't utterly dependent on cloud services.

+1 for having a "use our API and solve a problem" question on your application. I love encountering those [when the API in question is well documented, which yours is]!

I can't speak to working for Dropbox, but interviewing for this position was one of the more enjoyable experiences I've had in the job market lately.

There's an excellent response to be made regarding the "silliness" of weighing cool research vs the ethics of the body doing the research, but making it explicitly would invoke Godwin's Law.