In this picture, most of evolution wouldn't be changing the keys but changing the score.
1,223 karma · joined March 29, 2007
In this picture, most of evolution wouldn't be changing the keys but changing the score.
Interesting to have it called out here that it's default behavior that's inconvenient for the author to change.
Sometimes I'm in the position where I want or need to do something even though I'm dreading it or am not excited about.
A few things have helped me when that's the case: 1. Coaxing myself rather than trying to crack the whip. - Finding what's interesting about the task - Thinking through how it might be made interesting or easy - Thinking through whether I can automate it away - Starting on a tiny piece without committing to finishing it right away - Lowering my requirements on quality for a first try to basically zero - Developing a habit around the task with a reward like a streak or a check mark 2. Writing out my thoughts - Why do I want to take on this task? - Why don't I want to take on this task? If I can drill down on both of those maybe I can come to some kind of resolution
Anyway, a lot of what works depends on what's broken in the current situation. I think that sometimes your desire to avoid something is right and sometimes it needs to be worked around. But in either case it can be at least heard with thoughtfulness and compassion. There's probably insight in the feeling that you don't want to miss out on.
On the other hand, I think it's a mistake to treat these feelings as the only thing either. Often even strong feelings are temporary and situational and getting better information or just letting time pass or building up a feeling of success from small wins will let the storm move on.
My favorite part of the job is coding in Rust and we do a lot of cool things in that backend code. Unfortunately, most often the Rust code is the fastest and easiest part of a change, which means that I spend most of my time solving problems either on the front end with Typescript or on CI and infra type things rather than the Rust part.
It's a bit sad: if something just works, you spend less time on it than on the hairier things.
Medium changed from reader-friendly to reader-hostile over time.
There is however a pitfall that this approach seems to lead to unless you actively prevent it. Roughly the process is 1. You hire someone to take care of things manually. 2. As you grow, your devs are worrying about other things and so instead of automating you hire more and more people to handle the toil that should have been automated along the way. 3. Because these jobs are handled by one group of people and developers are working on customer facing features, the communication and prioritization necessary to fix the issues rarely come up.
To put it another way, I think the demand for it is often just another manifestation of Conway's Law.
If we focus on settling planets, then each planet is its own set of problems.
But if we focus on learning to live in space, then although it may be harder initially, it's a single problem to solve. Then we just keep working and improving on that solution. And there's a lot more space out there than there are habitable planets. And there's a lot more matter and energy out there than are available on those planets.
If we get to a place where it's all AI, is there a chance that many smaller machines will become more effective than a few enormous ones?
When I really want effective synchronous communication I tend to escalate from Slack to audio or video a screen share -- it seems like there's an extra layer of collaboration that you can have with a bit higher bandwidth.
For meetings I like to have audio plus a screen share of a shared document -- usually not a Slack document, because it's valuable to have more than one person be able to make edits.
Record pricing for used cars suggests that there's a car shortage.
Ironically, less cars and less driving could lead to
1. Faster driving because of clearer roads, and
2. More walking.
Combine those and it wouldn't be surprising to get more auto-pedestrian accidents.
One test would be to compare changes to car accidents with changes to pedestrian accidents. Reckless driving should bring both up. More pedestrians should only bring the latter up.
Feynman was humble in that he tried to learn what was true instead of assuming that he already knew. He was always looking to improve his understanding.
Being humble in the search for truth can sometimes even seem arrogant socially. It means that you'll regularly question not only your own beliefs but those of other people as well.
Similarly, it's hard to see the cost of criticizing and it can be hard to judge the benefit of understanding.
Because of this, we'll see patterns of ignorant criticism playing out again and again. Some of the people in the pattern will never know any better. Others know better but don't care. Others know better but can't pay the price to understand because it's too high.
So when you find someone who actually defaults to understanding rather than criticizing you've found someone of rare value.
"Adventure is just bad planning."
I hired him once and if he were in a bad spot I'd hire him again in a heartbeat. In the meantime, of course, he has lived within his means for years and could weather any financial storms likely to blow his way.
He enjoys his job, earns great pay and plenty of stock and has the respect of his managers and junior colleagues. He has helped the engineers around him perform to a higher level and teaches, but he loves creating through code and is very good at it. He also has earned enough trust and is productive enough that when he says "The snow is great today, so I'll be skiing," that's just understood as his privilege.
So that's what happened to one person.
Don't roll your own auth. But do feel free to use a battle tested auth library / or framework hosted in your own app.
Then you get both benefits: 1. You don't have to put your destiny in someone else's hands, and 2. You're not getting the risks associated with building your own auth.
That is, if you have had it then you start out susceptible to it. So the cohort studied for this number may differ from that studied for vaccines studies, particularly those performed selectively on people who have not contracted covid.
Of course, I'm assuming here that people have different likelyhoods of contracting the virus given similar exposures. That seems reasonable but I don't know how large the effect is.