And here is how it looks after it’s on your phone
And here is how it looks after it’s on your phone
People keep treating me as if it’s a bigger deal than I think it actually is. “Like” (my therapist said) “when a toddler falls and you rush to their side and they start crying because you’re scared.” (This is when I asked them if I was heartless for not being devastated about the whole thing. Was I not feeling much because I was protecting myself or because it actually wasn’t that big of a deal? Therapy is great. More people should do it.)
Many people rightfully take it hard when pregnancy doesn’t work out for them. Whether because of religion, or because they’ve been trying so hard, or because of whatever… and I respect that. But this isn’t that story. If hearing that perspective will be harmful to you in some way, please stop reading now.
When Reed and I first started rolling around together, we talked about kids. (As anyone having sex should.) It was off the table between us, but we kept enjoying each other while I sought a person to procreate and raise children with (ah, the bonuses of polyamory). As our relationship deepened, it was put back on the table. We decided to be primaries, to cohabitate, to get hitched, to try to procreate. Like many things we do together, we set a timeline and a budget. If it didn’t work out within those constraints, we’d both get sterilized and pick up hang gliding.
Our plan worked out surprisingly quickly for us. Reed found a great OB, and as things developed on track we carefully told our families and made plans at our workplaces. All the tests were in the clear for the first trimester. We heard a heartbeat and saw tiny raised fists on an organism that was bizarrely growing inside me. Side note: AS A NONBINARY PERSON HOLY SHIT THE GENDER DYSPHORIA. I opted to know All The Things All At Once via a microarray CVS at the beginning of the second trimester. Why keep honing in on probability when relative certainly is an abdomen-puncture away?
The results came back, and we talked about them, and the micro deletion that showed fell outside our acceptable risk profile. In short, we should try again on our own or via IVF (still figuring this out). EG, having a second trimester abortion.
The dilation was the worst part. The actual procedure is fine, although I’ll end up with bruises from an IV as usual. And the thought that so many other people don’t have access to harassment free clean care and caring nurses is fucking horrific. As I’ve said in other places, if this story moves you to any action, please let it be supporting Planned Parenthood.
So we’re going to try again. Maybe it’ll work, or maybe I’ll get to learn hang gliding. I now know I can survive the first trimester and still be gender queer while I do so. I know I’ve got loving, supportive people around me and a Reed who is amazingly present.
I know this is a big part of many people’s stories, but it’s not for me. It’s just another thing that happened. And that’s fine.
Thanks to Ride Free Fearless Money and to Reed for helping me to not shrink away from conversations about money and my responsibility in its orbit.
So I grew up with some money. I think my parents did a pretty good job of navigating it – we were spoiled with things like good health care, good mattresses, healthy food, and comfortable shoes. I didn’t have a lot in the way of clothing or toys or other “frivolous” things, but we did have our basic needs well met. They helped with my school until I got a scholarship that paid for the bulk of it. At both times I worked part time to cover the rest. I graduated without debt. When I was in an abusive relationship, they covered my costs leading up to and after I left him. I am privileged.
I also have had the luxury of being principled about what jobs I do (and don’t) take. I’ve asked for (and gotten) loans from my parents (as well as gifts from an aunt) in the long stints between jobs at places I could work at in good conscious. I’ve since paid them back for the support, but I want to acknowledge the impact their support had on my career path.
And so now I can take jobs that I enjoy and feel are net positive impact and which pay well. To get here without the level of support I’ve had takes a bigger badass than me.
Now that I make dirty tech money (that, while less dirty than most, is still a part of the narrative of over valuing some skills and under valuing others) I’ve found this stupid thing to be absolutely true: having money makes it easier to get more money. In fact, people tend to just give you more money once you’ve gotten to a certain point.
It’s broken and I hate it.
Back in 2015 when I got my first steady-income job making a bit more than I needed to live off of, I started thinking about how to responsibly invest that money. In addition to that starting point, I also give to nonprofits and GoFundMes and Patreons. But there’s this thing that is still really awful to me, and it’s this: I am now wealthier than some of my dearest friends and some of my family, and to have a microcosm of society’s larger ills so close to our faces fucking sucks. I’ve been wondering if it’s possible to just give people money (also one of the most effective humanitarian interventions!) in addition to the organizations I support.
Enter the Protestant Work Ethic, AKA “the American Dream.” What it says in brief is that your moral goodness is evident in how well you do in the world. EG, you don’t have to wait for your rewards in heaven, you get signals that you’ll go to heaven based on how successful you are while alive. It’s some bollocks and it’s what I think of as a core illness in American Society.
So I can’t just give people money because it’s indicative that they didn’t earn it and therefore to have it is an evil (even tho money is just being given to me without being based in merit or need). While to me at this point it’s just another resource I’d really rather share, I can’t because of Protestantism. Or maybe they have other reasons of their own.
I’m pretty new to all this, so I expect to be immature in my approach, and I’m eager for feedback in the comments.
After consulting many great humans I respect, here’s where I think we’re at:
It seems to be ok to give them money without a lot of explanation. Can just be marked with “for a rainy day” without further explanation. This may also come under the expectation of middle- and upper-class environments based on “if money goes from your parents to you, you’re middle- to upper-class. If it flows from kids to parents, you’re lower class.”
A Patreon, an artistic practice, etc: commission something from them. Pay them as good or better than market rate so they also value their work more and can point at the sale in future negotiations to uplift their entire business. If you’re already supporting their monthly Patreon (or whatever), increase your amount.
This is also a great chance to give gifts. If someone is into a new hobby or embarking on a new adventure, giving gifts to get them set up well can launch them and not feel invasive.
Offer an interest-free loan you’re potentially willing to forget about. If not willing to forget about it, work on clear, flexible ways to do the repayment.
Another great point for gifts.
Include a note about how wealth disparity in general sucks, how a windfall was just come into (inheritance, signing bonus, etc), and that you’d like to redistribute it. Make it clear there are no strings and what they chose to do with it is up to them. Don’t be offended or mention it if they don’t cash a check.
Money is a point of deeply personal stress and pain for many folk. It is not easy to talk about, to need, to offer. And you know your friends and family better than I will, so your mileage may vary. I anticipate that if you’re kind and loving and up to make mistakes you’re willing to own up to and you’ll be fine.
Stick ’em in the comments!
Wish me luck as I embark on enacting these even more in life.
If we haven't met yet, I'm Issac.
I am an engineering manager at a company in San Francisco (though they're a worldwide company) called Stripe. I am inside a group called Treasury Engineering, where I work on helping manage Stripe's liquidity and foreign exchange products and services both internally and for Stripe's customers.
This is not about Stripe but I'll say: It's really quite nice to be able to say all of that.
From April 2017 until September 2019 I worked for "Astra". They are building a small disposable orbital launch vehicle, or ideally, dozens of them. I started the test and launch software discipline and built a team there.
Ashlee Vance wrote about us here for Bloomberg: https://www.bloomberg.com/features/2020-astra-rocket/ (IA Link)
Eric Berger wrote about us here for Ars Technica: https://arstechnica.com/science/2020/02/at-astra-space-failure-is-an-option/ (IA Link)
From November 2013 until October 2015 I worked for "Nonchalance". They were building something. It was a game, and a society of like-minded folks, and an art installation. It was lots of things to lots of people. I spent my time there running the "Systems" group, which was both hardware and software with a very strong bent toward experimental human computer interface design.
Lots of people wrote lots of things, but I'm going to only list my two favorites
Jessica Lachenal wrote about us here: https://medium.com/@jeslach/the-latitude-society-a-story-45915e489937 (IA Link)
Lydia Laurenson wrote about us for Vice: https://www.vice.com/en_us/article/xygykj/my-year-in-san-franciscos-2-million-secret-society-startup (IA Link)
In many ways I loved both of these jobs tremendously. In many ways they were both quite crummy. One thing that they both had in common until very recently was that they insisted that we don't talk about it in public.
This does a disservice to the business in at least these ways:
This does a disservice to the employees of your business in at least these ways:
I learned a lot of things at ORDcamp this year in Chicago, but I wasn’t able to attend the “How To Make SPAM Musubi” workshop. After hearing from so many people about how easy it was, I decided to learn. I’ve gone through two cans of SPAM since then.
Here is the video that taught me how it’s done.
The caveats here are : I’m running the gitlab-omnibus-ce in docker
It mounts all of it’s data (etc and var) at /virt/gitlab
# Make the backup docker exec -t gitlab gitlab-backup create BACKUP=gitlab-full-backup # Put the backup somewhere good s3cmd put /virt/gitlab/var/opt/gitlab/backups/gitlab-full-backup_gitlab_backup.tar s3://go.rottenboat.co/gitlab/etc/gitlab/gitlab.rb # Copy gitlab.rb and gitlab-secrets.json s3cmd put /virt/gitlab/etc/gitlab/gitlab.rb s3://go.rottenboat.co/gitlab/etc/gitlab/gitlab.rb s3cmd put /virt/gitlab/etc/gitlab/gitlab-secrets.json s3://go.rottenboat.co/gitlab/etc/gitlab/gitlab-secrets.json
I saved all of that to a file called “backup_gitlab.sh” which I run daily on a cron job.
I need to setup wal-e on my home server because recovery plans are good.
First I setup a new S3 bucket and IAM user for it
Then I started following the README and the following blog post.
I have modified some of the instructions to use a python virtualenv because I like clean environments.
umask u=rwx,g=rx,o= sudo mkdir -p /etc/wal-e.d/vars sudo su echo "my secret" > /etc/wal-e.d/vars/AWS_SECRET_ACCESS_KEY echo "my access key" > /etc/wal-e.d/vars/AWS_ACCESS_KEY_ID echo "us-west-1" > /etc/wal-e.d/vars/AWS_REGION echo 's3://mybucket/wal-e' > /etc/wal-e.d/vars/WALE_S3_PREFIX virtualenv env -p python3.8 source env/bin/activate pip install wal-e[aws] envdir chown -R root:postgres /etc/wal-e.d
First and foremost I want to make sure I can push a full backup via cron
sudo su postgres /etc/wal-e.d/env/bin/envdir /etc/wal-e.d/vars /etc/wal-e.d/env/bin/wal-e backup-push /virt/postgresql_data/postgresql/10/main/
I got this error, so I installed lzpop and pv
postgres@pelennor5:/etc/wal-e.d$ /etc/wal-e.d/env/bin/envdir /etc/wal-e.d/vars /etc/wal-e.d/env/bin/wal-e backup-push /virt/postgresql_data/postgresql/10/main/
wal_e.main INFO MSG: starting WAL-E DETAIL: The subcommand is "backup-push". STRUCTURED: time=2020-02-08T22:28:37.586041-00 pid=25452 wal_e.main ERROR MSG: could not run one or more external programs WAL-E depends upon DETAIL: Could not run the following programs, are they installed? lzop, pv STRUCTURED: time=2020-02-08T22:28:37.693263-00 pid=25452 postgres@pelennor5:/etc/wal-e.d$ exit root@pelennor5:/etc/wal-e.d# sudo apt install ^C root@pelennor5:/etc/wal-e.d# apt install lzop pv
Next time my cron-capable command worked from the postgres user, which suggests a few things are going well.
Now I need to edit postgresql.conf
archive_mode = on archive_command = '/etc/wal-e.d/env/bin/envdir /etc/wal-e.d/vars /etc/wal-e.d/env/bin/wal-e wal-push %p' archive_timeout = 60
sudo systemctl restart postgresql then seemed to work…
After that, I setup the base backup on crontab for postgres. All set on the backup side.
Now I need to test a restore to prove to myself this is reasonable, so I am going to setup postgres10 in docker on my laptop and try to restore from S3.
I have to update my expired GPG key today.
I followed a guide saying "Set up a master key, with no expiry and keep it somewhere safe, and use that to make new keys, and revoke/expire them if necessary"
I did that. Then my "child" key expired (in April 2019) and now I can't make new password with "pass"
I followed these two guides
Updating the expiry
Importing and Exporting
Originally posted on the Truss blog
Most of us rely on documentation in one way or another. In this blog post, we attempt to make the following points:
“Documentation” is the media object (text, video, images, etc) which explains how to do something. Docs can take the form of descriptive policy, READMEs, How-Tos, welcoming, etc.
Documentation is nearly always worth having, but if you only have time to get one piece of documentation in place, it should be made on the assumption it’s being used to onboard someone to the project, organization, process, etc to which it relates. A person rarely looks at the whole project, organization, process, etc as a whole as that is overwhelming. They instead look for signposts that provide context and support in understanding the system they’re about to interact with.
When I got started at Truss long long ago in 2017, we had an onboarding manager checklist but no real guidance for the new Trussel outside of that human contact. Ari, who at the time was doing onboarding (and is now an engineer), is an incredibly high-touch, welcoming human. However, if she or another person helping with the process had a more pressing thing to be doing (which was often the case at a suddenly and rapidly growing consultancy), a new Trussel would stall out and be left in a sea of tasks, new tools, and new people, with a sense of “what even do I do?” And when one doesn’t have a clear path forward, one can feel useless, which is not a good feeling when you’re just getting started somewhere and want to prove your worth.
This was because we had documentation about how things worked, but not from the perspective of the person being onboarded to the organization. If we were to get this in place, a new Trussel would feel more welcomed and solid in their footing.
Luckily(?) I compulsively document things. So as I learned about bits and pieces of the organization, I wrote down in one place what others should also expect as they came in. Oh, we do have a document about PTO? Link it up and give a quick summary. We don’t have one on role definition? Could I help make one? I tried to set it up so when something was unclear or incorrect in the docs, a new person would feel safe enough to ask questions and empowered enough to edit the docs when they learned the answer. This generated a surprisingly long document which was complete enough, but also incredibly overwhelming.
Documentation takes a bunch of different people of different practices to make it good. Sharing the load also makes creating and maintaining the docs a lighter lift and a shared source of truth and object worth maintaining together.
Our document was way too burdensome, so we called on our design content strategists James and Kaleigh, who suggested it be reformatted into phases of onboarding time. Delivery Manager Amy tried this format out first on her project, and then I expanded it into the MilMove project. When it stuck well enough, we did a card sorting exercise for who wanted to know about which parts of our operations, and when it made sense to learn about them. We also started linking out to external documents when a section got too long or convoluted. This allows people to focus on the big picture, and dive in deeper when something is relevant to them. Then we took our honking document and rearranged it and edited it down to a mere 28 pages.
Just as people had started asking to have new policy or reference docs put into the emerging guide, everyone also helped edit for clarity. It became a thing for more folk to reference and make use of. And just as Nelz, Jeri, Andrew (all engineers), and Mallory (designer) have held my hand in multiple ways to migrate the Guide from a Google Doc to GitHub Pages, many other folk have also refined the Guide to make it what it is. Including our general counsel Burstein writing the best damn disclaimer you ever did see and otherwise making sure we’re not just witty but also reasonable legally.
We have all done this in the spirit of being a warm, welcoming place for new Trussels. All those folk named here (and those I have forgotten ) have demonstrated our values in order to make it an easier transition for others to also represent those values.
If you are working on onboarding documents, call in help! Ask tenured folk to verify knowledge is represented, newer folk that it’s clear, content specialists to review structure, etc.
Growing and large organizations are often accused of “the left hand not knowing what the right is doing.” This has to do with the functions of the different hands not being clear to the other. Enter (you guessed it): onboarding documentation! By describing how different components of a system work, the system itself has opportunities to become more aligned.
One thing that came up time and time again as we worked on the Trussels’ Guide were points of inconsistency or lack of clarity around internal workings. As we grew from 14 to 90 Trussels during the development of the Guide, our processes were also scaling. We became more robust and more formal. But importantly, we always did so with an eye to being comprehensible to an incoming Trussel. Docs shouldn’t only be intelligible in the context of the whole — each should stand on its own in a meaningful way. While most Trussels can’t (and shouldn’t have to) know about every tiny detail of how the business operates, they should be able to look up the details and/or who to ask if they start to care.
As an aside, there’s also this great piece about how you can’t fix a product (or a process) by having good words. The thing you’re describing has to be good, too.
Documenting can surface where things are out of alignment and provide a route to bringing them back into sync with each other. This is important for your organization, project, or process to be functional within the context of itself and the larger systems of which it is part.
What’s worth documenting? I start documenting when roughly three people ask me the same sort of question. Rather than respond to each separately, I
This allows emergent areas of interest, guided by our new Trussels, to determine some of the aspects of the business we next define more clearly.
So now we are ready, dear reader, to show you how we work at Truss and, as importantly, how we talk about how we work. And so I introduce to you the Trussels’ Guide to Truss. In it are the ways we are kind to each other, how the business functions, some of the decisions we’ve made, and how we embed assumptions into our work.
We hope you’ll have a look, take what works for you, leave what doesn’t, and continue to engage in the conversation of how to build great businesses together. Also, if this seems like the place for you, we’re hiring!
It’s o-fish-al, we just crossed the 500 backer mark on the KnifeTank Kickstarter, so we’ve unlocked the new “Fish Tank” card that you’ve been herring about. This is a bonus tank that will come with your KS rewards. For those who missed it, the Fish Tank was a tank originally suggested in the comments on a previous post, then my artist mocked up 3 versions of what the tank could look like… and now you get to see the fin-al art!Fish Tank art (not drawn to scale)
Some of you may have noticed something fishy about the this particular card… most tanks only have one turret symbol (the yellow circle), but Fish Tank has two. This means the Fish Tank allows you to choose which turret you want to use when making an attack. Will this break the game? Any fin is possible, but don’t think it’ll be a turtle disaster. Besides, this seemed like a good oppor-tuna-ty to experiment with a new idea. It’s bass-ically a normal tank with one more turret in the back.
I look forward to hearing many tails of epic Fish Tank battles. Will your tank be the sole survivor?
Cod I hope I don’t lose too many followers from all these sofishticated puns. At least I’m kraken myself up.
I might be the only one that thinks these videos are enjoyable, but I still crack up every-time I watch one. Making them was a blast, I just sorted iTunes by song length then found my favorite songs that happened to be four and half minutes long, then I scoured Youtube for a few performances of John Cages “Composition 4’33” and mashed them together in Premiere. You can still hear some of the audience sounds and incidentals from the live performances. You can watch all 7 mashup videos here.
For anyone interested in learning more about Composition 4’33”, I highly recommend this episode of 20 Thousand Hertz. It’s my favorite explanation of the piece and has a powerful experiment at the end of it.
One thousand folks have asked me “Who’s that rapping on your Kickstarter video?“. I produced the beat and hired a death-metal singer to scream on the hooks, but the real star of the song is Beefy, a legendary nerdcore rapper from Kennewick, WA.
Beefy is one of my oldest buddies in the nerdcore rap scene. We’ve made dozens of songs over the years including “Ball Pit”, “Tub of Tobasco“, “Tilt“, and “The Sound“, but our KnifeTank collabs are some of my favorite projects.
Ten years ago, when we were working on a point and stab adventure game called KnifeTank: The Hauntening, I reached out to Beefy to add hist talents to that soundtrack. His verses for the “Crimson Dreams” perfectly captured the silly/scary/metal vibe of the KnifeTank universe. You can check out the full album, which was co-produced by Crashfaster, here or check out the 8bit Betty remix of “Crimson Dreams” here:
Beefy and I still collaborate occasionally. In fact I recently appeared on Beefy’s new song “Tag Team” along with MC Frontalot, ytCracker, Glenn Case, Mikal Khill, and Lil Jordo. That song just went live this morning as part of the Nerdcore VPC 6 challenge coming later today.
I’m so proud to say that my first tabletop game, KnifeTank: The Shüffling, is now live on Kickstarter. The game has already reached its $8,000 goal, but now I have my eyes set on reaching 1,000 backers. I’m at nearly 400 now, so I have quite a ways to go, but I think I can do it.
If you can help support the project at any level or spread the word, I’d really appreciate it!
If you need more convincing, check out this fantastic review on BoingBoing.net
What I wasn’t expecting was a game I instantly wanted to play over and over again and invite my friends to come and play (which I did). KnifeTank can hold its own against anything coming out of a large commercial game company and I look forward to it enjoying a long and happy life, with many expansions and a worldwide, enthusiastic player community.Gareth Branwyn for boingboing.net
The post KnifeTank: The Shüffling is live now on Kickstarter appeared first on Doc Pop's Weblog.
Min Park decided to try learning how to fingerspin with his yo-yo, unfortunately he was surrounded by LCD TVs and this happened:
I thought this would make a great addition to my cracked screen wallpapers for mobile phones, so I’m adding it here:
Here is how it looks on the phone:
The post A Wallpaper Made From An LCD Screen That Was Damaged By A Yo-Yo appeared first on Doc Pop's Weblog.
I’ve finished recording my next album and we’ll begin mixing and mastering it in February. I can’t wait to share the whole thing with you, but for now I thought I’d share a demo version of the album’s title track: