373 karma · joined December 6, 2019
When the toilet paper shortages started happening, I used them as an excuse to convince my wife that we should buy a bidet. I had floated the idea by her multiple times over the years, but she was always weirded out by it, but I was finally able to convince her.
We also have an entire deep freezer full of food and are both fortunate enough to be able to work from home, so as long as the electricity and water stay on, we can survive in complete isolation for at least a month.
No toilet paper needed! We just have a stack of washcloths and we use one to pat ourselves dry (and then set it aside in a container to be washed weekly).
I then drop the cloth into a small bathroom trash can with a lid that is marked, "dirty wash cloths only". This small trash can sits down on the floor next to the toilet, and once a week I just wash the cloths along with the other towels. The cloths aren't even really dirty, since your butt is clean by the time you use them. I don't like the idea of re-using them without washing them though.
And just like that, my toilet paper usage has dropped to nearly zero.
I honestly have no idea how Roomba is still in business
A face mask.
Masks stop people from constantly touching and/or itching their mouth and nose.
Think about that for a second, before you tell people how useless masks are.
This is why (at least in the Ruby world), it's generally considered best practice to avoid using inheritance and just use mixins instead (whenever possible).
Completely avoiding classes because you are using them incorrectly is kind of like throwing the baby out with the dirty bathwater. Don't throw away your tools just because you are using them incorrectly!
All they do (and all they have ever done) was reinvent the wheel. They do, however, consistently reinvent the wheel better than anyone else.
Case in point: In literally the year 2000, I owned an HP Jornada 548 pocket pc, complete with a wireless modem that worked on cell phone networks. It ran Windows CE, and I was able to surf the web, use AOL instant messenger, ICQ, do voice recordings (even transcription), handwriting recognition, play games, and yes, even make phone calls. But it was clunky, and it wasn't something that I would even dream of recommending to my grandmother (because the UI was terrible and slow, and it required a lot of fiddling with things to get it dialed in the way I liked it).
Contrast that with the iPhone (which was released a full 7 years later). Was it the first smart phone? Obviously not. But it was the first smart phone that I could honestly recommend to my grandmother.
What is my cost with a million objects, an average computational complexity of 3 compute units per search, etc.
If you can't do that, at least give some example scenarios (small, medium, big, huge, etc) with total pricing.
Just... something. Anything would be better than a "contact us" link.
I absolutely refuse to use or recommend anything that looks like a black box enterprise solution if it lacks transparency.
I was an alcoholic for over 10 years. I would drink multiple liters of vodka weekly. It was not uncommon for me to drink an entire 375 ml bottle of vodka in an evening.
I never really considered myself to be an "alcoholic" in the traditional sense though, because I didn't let it affect my day-to-day life as a programmer. I was young and healthy, and I didn't usually have much of a hangover because I only drank high end vodka, and I always drank a lot of fluids. Whenever I got a hangover, I would just pop an ibuprofen and the hangover would disappear after about an hour. I would literally set my alarm an hour before I wanted to wake up, and when that alarm went off I would wake up, pop an ibuprofen, drink half a glass of water, then go back to sleep. By the time my second alarm went off an hour later, I was as good as new.
I literally did this for years, while often working 12 hour days as a programmer. Nobody could tell, and it didn't seem to affect me too negatively, so I didn't see a reason not to. It helped me relax at the end of a long day, and it made movies and television more fun and enjoyable to watch. It was also fun to go out to bars and hang out with friends.
Eventually, though, it caught up to me, and I started to get reports from doctors about abnormal liver test results. They were still just borderline, but it was enough to scare some sense into me. I had just recently had a son, and I realized I wanted to be alive for when he grew up.
So I tried to stop drinking. I didn't want to go to alcoholics anonymous (I didn't consider myself to be an alcoholic after all, and I'm an atheist and didn't want to deal with all of their religion/higher power 12-step stuff).
Quitting cold turkey worked for about 3 months, but as I'm sure you know, the alcohol drinking culture in the programming startup world is extremely prevalent.
It was only a matter of time until I ended up in a social scene where I felt pressured to drink, and I had a beer along with everyone else. It was all right, I told myself. It was just a beer! No big deal! I had quit drinking before and I have it under control now, so it's ok! Nope. Once I got a taste and a reminder of the stress relief offered by alcohol, I started right back into it. Next thing I knew, I was drinking vodka every night again.
After a couple of more false attempts to stop (with each one being thwarted by my having a beer and getting sucked back in), I finally came to terms with the fact that I simply can't drink. I can't touch the stuff or I will get sucked back in. I realized I was an actual alcoholic.
So I stopped. I carefully tapered off my heavy alcohol consumption over the course of a week, and that was it. I've now been sober for a year and a half. Whenever I'm in social situations where other people are drinking beer, I simply order a diet coke or something and I sit and enjoy their company. I might even shoot the breeze and chat about all my favorite types of scotch or whatever. But I absolutely do not allow myself to have even one sip of alcohol, because I've learned the hard way what it leads to.
As a side note, during that year and a half, I also managed to get completely out of $50,000 worth of debt, pay off my car, and diet my way from 245 lbs all the way to 180 lbs (still have another 20 lbs to go before I reach my goal of 160).
And I did it all without alcoholics anonymous or medication or therapy or anything. I simply accepted ownership of the problem, made a decision, and stuck with it.
With that said, however, there was a catalyst and a "higher power" that lead to the change and kept me on track:
I had a kid, and I realized that I wanted to stay alive long enough to see him grow up and have kids of his own.
I realize this might not be a magic bullet for anyone (and I hope you get help if you need it), but my point is simply that sometimes it is in fact possible to do on your own (given the right circumstances and motivation), although this fact is something that is not very popular to mention.
I wish that when the team had migrated from SVN to git, they had used a tool that would have preserved the history. It's very easy to do! I don't know why they didn't. They did it right before I joined the company so I never had an opportunity to show them how.
- Allowing all users to freely create channels as needed
- Raising user awareness of how to use the very flexible channel notification settings (and muting channels that aren't relevant but still things you want to keep an eye on)
- Threading conversations whenever it makes sense
- Encouraging limited usage of @channel and @here (only use when very important)
Humans are remarkably capable at self-organization when given the opportunity.
At the end of the day, Slack is about enabling natural conversations between people. It is not email. It's chat. If you try to enforce rules on how people naturally converse with each other, you are going to encounter a lot of resistance and friction.
"IT pros always and without fail, quietly self-organize around those who make the work easier, while shunning those who make the work harder, independent of the organizational chart."
If you were trying to hire a mechanic, would you first give them a sudoku puzzle to measure his "cleverness" (and then use that as a predictor of their car repair abilities)?
It makes me almost not even want to bother saving up for retirement...
This approach has a lot of upsides:
1. Real work gets done
2. The developer gets fairly compensated for their efforts
3. You get to gauge them objectively, based on their actual results
I ended up trying out probably 4 different cables before I found one that was actually able to transmit the signal correctly over 25-30 feet. The cable that ended up working for me was a KableDirekt cable that I bought off Amazon. The beast of a cable is THICK. I also had a lot of luck with AmazonBasics HDMI cables for shorter runs.
The most important thing for 4K HDMI cables seems to be that they need to be well insulated and thick.
Chris Sawyer wrote 99% of the code for RollerCoaster Tycoon in x86 assembly language, with the remaining one percent written in C.
RollerCoaster Tycoon was a beautiful game which still stands the test of time to this day. The fact that a single person was able to build a blockbuster-level game almost entirely by themselves in assembly is a truly impressive feat which very few programmers would even dream of undertaking.
Being a "real" 10X programmer is like being a savant. It's about being FUCKING SMART, and it's about being able to deliver a working, polished product in the same time that a normal team of ten people would be able to deliver it (or in a tenth of the time that a single person might).
Whenever I want to post a code snippet, I just use the triple backtick technique, like:
``` code goes here ```
You can also insert code in the middle of a comment with a single backtick around it: `like so`
For the most part, though, I keep my code in the Git repository, and it's pretty rare that I actually need to share a bunch of code in Slack messages. If I want to pair with another developer I just open up Tuple or Zoom and do a screen share.