[...] they *also* added a raw image mode that will never break again and doesn't require Mach-Os.
And people said they wouldn't help. This is intended for us.
Over the past ~half year I gradually established a workflow consisting of a simple directory structure, a handful of bash-aliases and chromium profiles. It looks like this:
Each project gets its own directory somewhere in my $home with some subdirs. There might be various others specific to the project-domain, but these are the most common:
• notes/ contains plaintext files of everything i write down. File-name structure is <date-str>:<note-type>, e.g. 2020-05-09:call (:call are the most typical ones). As others have also suggested, I take a lot of notes for record keeping & plannning purposes.
• workspace/ contains all source code repositories, or other files necessary to work. Pretty much anything I might touch while coding.
• auth/ for things like ssh public keys used on the project
• downloads/ Project-specific downloads.
Then I create new entries in my ~/.bash_aliases that "get me" right into the coding-env of a project. Say I work on a python project, I might have an alias that looks sth like:
alias fb='cd ~/fooproject/workspace/foobot && echo "loading virtualenv..." && source .venv/bin/activate';
On of my current side-projects is a full-stack clojure(-script) app with these aliases:
alias foh='cd ~/opendecks/workspace/foh';
alias fohj='cd ~/opendecks/workspace/foh/src/clj/opendecks/foh';
alias fohs='cd ~/opendecks/workspace/foh/src/cljs/opendecks/foh';
First one gets me into the the source-root of the project, the other two into respective sub-paths for back- and front-end. These aliases allow me to immedeiatly "jump into a project" from any open terminal.
Lastly, I started employing chrome/chromium's user-profiles to seperate browsing for each project. This isolates work-related browsing from my personal activity (cookies, logins, passwords etc), and provides a nice cognitive barrier against procrastination. I'm not logged into any social networks on those work-profiles and switching to my private profile to browse facebook is a more concious act than opening a new tab in the current window. Each browser profile is set-up to save all downloads to the project-specific `./downloads` directory, again not to mingle (potentially confidential) resources.
I haven't automated any of the above steps, because it's so simple and takes me at most 10-15 mins to create a new instance. This has worked really well for me so far, because it clearly seperates almost all resources associated to a project, while being friction-less in tooling/switching between workspaces (versus e.g. waiting for a VM or docker instance to start). Another nice side-effect is that I can easily archive or clean-up past projects.
In Clojure, and I assume other lisps as well, you can use the < operator in the same fashion. By merit of prefix notation it's also unambiguous regarding precedence.
> But until any of these new age apps/platforms support federation and decentralized communication, there's not much use for the masses to look for servers run by specific people.
Federation of self-hosted servers and the "official cloud" seems to be on Wire's road-map, cf:
If I read this correctly, the "Enterprise Grid" section hints at one technical reason for this move. Slack recently announced[0] a new feature that allows multiple teams, err "Workspaces", to share a channel. This violates the uniqueness of @usernames within the namespace of the shared channel, e.g. both teams having a "@john".
This announcement anticipates (a) getting developers to use surrogate UIDs instead of @username for mentions, and (b) that their clients will only use display names in the future and rely on specific UI elements to distinguish ambiguous ones.
Thanks! During peak-temperatures of the day it's definitely warm inside, yet cozy/cool enough to have a nap. Also kept the warmth inside at cold nights.
Show HN: Years ago, some friends and I designed & built a dome/hexayurt hybrid[0] for Burning Man. The walls are made of insulation sheets and the hinges are taped with 6" bi-directional filament tape (many here will know Hexayurts[1], I'm sure). Additionally it has connection-edges which feature a system of fabric-strips and 2" velcro to connect edges reliably. In total it consists of 3 separate, foldable pieces that can be set up in ~20 minutes by 2 people, even in windy situations. It has 2 "windows", the pointy things on the sides. The door is a bit small and definitely requires some flexibility getting in and out :) It survived the harsh desert conditions of 3 years at Burning Man so far, incl strong winds and rainstorms, only requiring a bit of tlc between each year. The "strap-down-spider" tightens the structure down against winds and keeps it firm enough that you can easily lean against it. To make it fully rain-proof, one needs to tape the floor-tarp up against the walls (visible in the pictures). Apart from the floor-taping the setup and tear-down is entirely zero-waste, due to the velcro system. Hexayurt enthusiast might notice the silver tape that covers the filament-tape seams, which helps protect the tape from deteriorating in the UV light (w/o the silver tape, the filament tape would go brittle after abt 1-2wks of direct sunlight).
Here[3] is some very outdated documentation on the first version. We initially tried to connect the walls via bungees - didn't work out at all as you can imagine. The following year we added the velcro system after I found this amazing post [2] on a hexayurt mailing-list, describing someone's experiments with materials. Without that person's efforts and time spent on research I could have never finished this one!
Of course there's already a bunch improvements lined up for a v2 - hopefully next year :)
https://www.hiroapp.com - Note-taking reduced to the core that just works™. Offline first, no signup needed, easily sharable (url, sms, email) and (web)realtime sync between all devices and collaborators.
My co-founder and I moved on to a new project a year ago, but this thing is still buzzing along on a cheap DO box and works like a charm with basically zero maintenance. Frontend is vanilla JS, backend in Go and the protocol is our slight modification of differential sync[0] to (re-)synchronize all text and metadata.
Bali is just the first location we launched and Miami being the next we open soon. Many more to come, any regions in particular you'd like to see one opening up?
$1600/mo for a bedroom with en-suite bathroom. Also included are a communal kitchen, co-working space and perfect wifi/internet signal and speed. Some places have a pool :)
https://www.instagram.com/fontwien