flylikeabanana
flylikeabanana on Hacker News
Burning Man culture draws a distinction between participants and spectators - one of the best ways to get the “participant” experience is by working and actively being a part of putting it on. This definitely includes build and strike. There are people (many paid by the Burning Man Org) who get there months before the event and stay for months after.
Beyond just playing the files from storage, I also get subtitles, metadata, play history / continue watching / next up, a nice 10-foot UI, and the ability to satisfy my ADHD curiousity by clicking around tags / actors / directors and seeing what else I have from them in my library.
Location: Portland, OR
Remote: Yes, open to hybrid
Willing to relocate: No. Could be talked into commuting to Seattle.
Technologies: Scala, Java, Typescript, Rust, Python, AWS, Nix, (no)SQL, React, ML-style syntax
Résumé/CV:https://github.com/ccarlile/resume/blob/master/resume.pdf
Email: see Resume
Hello! I'm a functional programmer with lots of experince doing distributed systems in regulated environments. I left my job as Tech Lead in an extractive industry to seek roles with missions that align more closely with my own - I'm looking for opportunities to make a positive impact (in e.g. climate tech or med/bio tech). I'm also a "people person" so I'm happy to teach, lead, or represent as well.
I run emacs on MacOS specifying the `emacs-pgtk` build in my Nix config as the package. Seems to work quite well for me
They're fun little tinker devices, cheap enough that you can get multiple and play around with different form factors or loan out to friends
You'll note it specifies AMD devices, i.e. x86-64 architecture
I don't believe there's Bazzite or SteamOS available for ARM devices, which make up most of the "portable handheld" market in terms of device variety
MJ stays in your body long after the effects have worn off. You can test positive weeks after consumption.
>The problem is will you admit you were dead wrong and potentially spewing propaganda if democracy survives Trump’s second term?
The answer to this question is the same as the answer to "what if climate change is a hoax", and that is that I would love to be wrong and would gladly admit it rather than live under a dictator or on a dying planet
I got several morale game overs (one of them from a 12 year old bully, that didn't feel good) before I realized there's a button to take Magnesium to restore the lost sanity. So I feel you, but I pressed on and it's a quite rewarding gaming experience
One way would be to use emacs’ artist-mode to draw ascii lines and boxes then use ditaa[1] to transform them into images. It’s not a pretty packaged GUI app but it’s certainly an option
[1] https://ditaa.sourceforge.net/
Tenkeyless (TKL) keyboards are popular because you can keep your mouse hand closer to your keyboard. The tenkey is a easy thing to lose if you don't do much data entry.
As for writing code and playing games, I use vim keybinds everywhere and play games with WASD controls. So nav keys aren't particularly critical either.
There are screen protectors with a rough/matte finish that provide some of the friction you'd get from paper. It's not exactly the same, but it's a discrete step above writing on raw glass
I don't know if there's a way to indicate a project with the built-in project.el without a VC root. The other feature i use regularly that I don't think exists in project.el is projectile-toggle-between-implementation-and-test, which does exactly what it sounds like. You can configure it by build tool and give it path regexes to substitute to specify how to find the corresponding Spec for a file.
I actually use a mix of both. Project.el being built in means it properly leverages the built-in completion stuff, which has a level of awareness for the types of things I search and gives appropriate icons and context information (see all-the-icons-completion[1] for details). I fibbed a little bit about my workflow - to switch projects and find a file I use this:
(defun project-find-file-from-projectile-project ()
(interactive)
(project-switch-project (completing-read "From which project?" projectile-known-projects)))
[1]
https://github.com/iyefrat/all-the-icons-completion
> I guess you have to globally gitignore the projectile file too to avoid committing them everywhere?
Indeed, in my global git ignore, same with other workflow-specific stuff that nobody else at $WORK uses
Sure - projectile is one of the packages that convinced me to migrate from vim to emacs. It curates a notion of "project" and maintains a list of projects you visit. My workflow is based around a lot of using projectile-find-file, which prompts you for a known project, then dumps you into an completion interface to open a specific file.
Projectile works OOTB with .git directories, so if you visit a git-controlled dir it's added to your projects. You can similarly specify other directories as projects by putting a .projectile file in them, and the contents of the .projectile file act as an ignore list.
So the workflow is work/myMonolith is the git controlled root, while I have work/myMonolith/frontend/.projectile and work/myMonolith/backend/.projectile. So I can use the project-scoped find file, grep etc. to inherently narrow the search space to that module. When I'd want to globally search, I'd use projectile-find-file (or grep, or whatever) on the myMonolith root.
Orderless is probably the way to go for a “pure emacs” solution - its selling point is that you can feed whatever function you want into the completion framework, so if you feed a fuzzy completer then you get fuzzy matching. It’s also part of a relatively new completion stack (that includes vertico, marginalia, and others) that leverages the inbuilt emacs features instead of replacing them.
At that point, I’d be project-scoping to individual submodules rather than the whole monolith. For something like projectile, that would mean dropping a .projectile in the submodule root so my “rip grip in project” functions are scoped to the submodule, then using VC to mark the root where I need to expensively search the whole project.
A .nix file is a lot like a regular programming language, except the "compile target" is actually something like a big digraph of dependencies. Each package is hashed based on the content of the build steps and dependency inputs, so to nix "python 3.9" and "python 3.10" live in two entirely different places (because the hashes are different)
The next step is to actually take that digraph and instantiate a bunch of packages on your system. Each package has its dependencies symlinked to it using env magic, and bubbles up into your shell session or whatever.
All the different offerings in the nix ecosystem are based off this idea. Home-manager focuses on user session environments, NixOS extends the concept to a linux system (e.g. systemd units are managed in the same way - its just another hashed object in the nix store that gets symlinked to systemd), NixOps lets you do it to other machines, and nix-shell lets you create per-project development environments.
Nix flakes are the next evolution in the ecosystem, where some of the "inputs" get taken out of your env where they were black-box magic and put into a flake.nix (with a pinned version locked in flake.lock) so the input package set is controlled for across builds.
Nix aims to solve a much more general problem than homebrew. If all you want is to get some packages on your system, there might not be that much in Nix compared to brew for you. The zen of Nix is that building packages is expressed as pure functions, where inputs, outputs, and side-effects are carefully managed. Thus, if you have specific build, packaging, or environment configuration to do, nix can be really helpful. Since everything is in code and every generated nix configuration is effectively isolated from the rest, it makes rolling back to previous configurations trivial in the event something goes wrong. That, and you can VC a config, and in general once a package is properly expressed in Nix it more or less solves the "works on my machine" problem
The contrast between text and background is way too low. I have "good" eyesight and strained to read the blog post
Nit: It's a proper noun "Emacs" unless you're maybe referring to the executable "emacs", but at any rate the eMac was a computer sold by Apple in the education sector, and eMacs is the plural of that. Your iOS device is likely autocorrecting to that spelling, because to Apple, what else could you possibly be referring to?
FP in python is painful without tail call elimination and the higher-order function syntax is so clunky
> Pointing to google as a positive example hasn’t made sense in quite some time.
I don't usually get pedantic about typos, but the twofer here really made it hard to understand what you were saying
Also John Kennedy Toole, his novel The Confederacy of Dunces was published by his mother after his suicide and it ended up winning the Pulitzer.
That phrase is usually referring to some sort of judgement or characterization, not a particular action. If a teacher makes the whole class stay late because a few were acting up, that's not painting with the same brush. If you think that all children are disruptive because a few acted up, that is.
Let's say I block all Tor users for my website, because the level of abuse that Tor enables means an overwhelming amount of the malicious traffic I encounter comes from Tor. Am I painting all Tor users with the same brush here, or am I just min-maxing my time and energy trying to wrangle all the crap?
Isn't this the difference between concurrency and parallelism? Like you said, Tokio (I'm coming from effect systems in Scala, the current generation of which take heavy inspiration from Tokio) is good for informing your program when your code is blocked so it can perform some useful work elsewhere, which is a fundamentally different problem to parallelizing code. So if I'm understanding your complaint right it's that Tokio sneaks in when its concurrency features aren't particularly useful for parallelization?