HNHacker News
TopNewBestAskShowJobs

dhbradshaw

1,223 karma · joined March 29, 2007

Working on 0tm8.com: gardening automation for coders
submissionscomments
dhbradshaw··on Orb weaver spider glue properties evolve faster than their glue genes
I like to think of genes as keys on a piano. But the genome also includes the a lot of the musical score. You can get a lot of different songs with a finite set of keys played in different combinations and sequences and amplitudes.

In this picture, most of evolution wouldn't be changing the keys but changing the score.

dhbradshaw··on Dark Patterns in Substack
Huh, I did indeed unsubscribe from a bunch of people because I didn't want those emails.

Interesting to have it called out here that it's default behavior that's inconvenient for the author to change.

dhbradshaw··on The average American has the same life expectancy as the worst part of England
Interestingly, within the US people who live on islands like Hawaii and Puerto Rico seem to have longer life spans. This is true even taking race and gender into account.
dhbradshaw··on Life is a game, this is your strategy guide (2014)
If you can afford it, following the intrinsic motivation may be exactly what you need to do.

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.

dhbradshaw··on I love building a startup in Rust but wouldn't pick it again
We have a fairly complex app with a front end in Typescript and a back end in Rust backed by Postgres on AWS.

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.

dhbradshaw··on Ask HN: Why did medium.com "fail"?
If you punish me every time I follow a link to your site, I may learn to avoid following links to your site.

Medium changed from reader-friendly to reader-hostile over time.

dhbradshaw··on Building a Cloud Database from Scratch: Why We Moved from C++ to Rust (2022)
Try using a test -- can stick anywhere and just run code there (push of a button with analyzer in vscode). Almost like embedding a repl into a module for experimentation.
dhbradshaw··on Scalability is overrated
I think this is the right approach.

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.

dhbradshaw··on Low-code is not a cure for overworked IT departments
I think a lot of times the problem that people want low code to solve isn't IT being overworked but IT being out of their control.

To put it another way, I think the demand for it is often just another manifestation of Conway's Law.

dhbradshaw··on Brex layoffs
No layoff is fun. But props to the company for the 7-year option extension and removal of the one year cliff.
dhbradshaw··on Super-Earths are ideal targets in the search for life
This is exciting, but I think I'm most excited about learning to make self-sufficient and self-replicating colonies in space.

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.

dhbradshaw··on Why stream your events to B2
B2 offers cheap, durable, worry free storage but it's slow and not appendable. Add a low-latency appendable adapter and you have something interesting.
dhbradshaw··on Farm vehicles approaching weights of sauropods exceed limits for soil function
I think one of the reasons to get bigger and bigger is to save human time.

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?

dhbradshaw··on Can Slack-mania be cured with systemized discipline?
In the main article Slack communication is assumed to be synchronous. I find life to be a little happier when it's assumed to be asynchronous. That means turning off some channel notifications.

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.

dhbradshaw··on Pedestrian deaths spike in U.S. as reckless driving surges
Here's kind of a weird hypothesis worth at least considering:

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.

dhbradshaw··on Feynman on group decision-making at Los Alamos (1985)
I think you have to distinguish between being socially humble and being humble about truth.

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.

dhbradshaw··on Single dependency stacks
I'm interested -- would you be willing to develop on this a little?
dhbradshaw··on Being Slow to Criticise
It's easy to criticize and hard to understand.

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.

dhbradshaw··on Everything must be paid for twice
I do the same -- that is what moved me from Matlab to Python and Windows to Linux about 15 years ago. I had no idea at the time what a blessing that move was going to be, but the principle of maximizing future freedom led me in the right direction.
dhbradshaw··on Everything must be paid for twice
I learned this the hard way when trying to create iron nanoparticles. I found a great deal on a fair amount of iron pentacarbonyl while I was working at LANL. It was a few dollars to buy. Later I learned that it would cost thousands of dollars to dispose of!
dhbradshaw··on The harrowing journey to Elephant Island by Ernest Shackleton and Endurance crew
One of my favorite quotes is by Amundsen, who led the group that first reached the South pole:

"Adventure is just bad planning."

dhbradshaw··on What happens to developers who never go into management?
If his status came from the trust of one person that might be true. But it comes from ability and from character and from the consequent respect of many people. One bad manager could certainly tank his group (as in https://steveblank.com/2009/12/21/the-elves-leave-middle-ear...) but that theoretical manager wouldn't tank him -- he can just move on to a better place.

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.

dhbradshaw··on What happens to developers who never go into management?
I work with a developer who's in his 50s. He chose not only to stay in development but also to stay on the front end where he turns out beautiful and beautifully effective UIs using Angular.

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.

dhbradshaw··on Iced: A cross-platform GUI library for Rust, inspired by Elm
I've been playing with the iced examples, particularly the styling example. The code is beautiful and the result is clean and responsive and fast. Love this.
dhbradshaw··on Chip shortage: Toyota to cut global production by 40%
I'm not sure the reasons for the shortage matter. If you have a dependency that's causing you major problems, you try to become less dependent on it.
dhbradshaw··on Chip shortage: Toyota to cut global production by 40%
As a chip supplier, I'd be feeling a lot of pressure right now. In the short term you can squeeze and the tail can wag the dog for a bit. But longer term this opens the door wide open for new competitors in the market and / or vertical integration.
dhbradshaw··on Ask HN: Who is hiring? (July 2021)
If you refer yourself, does n=0?
dhbradshaw··on Class-action lawsuit over gender pay disparity at Google
It will be interesting to see how the numbers play out. I'm confident they'll have the resources and knowledge necessary to check for interesting effects like Simpson's paradox.

https://en.wikipedia.org/wiki/Simpson%27s_paradox

dhbradshaw··on Three things to never build yourself: auth, notifications, payments
It's been said a few times here, but it's important so I'm calling it out on the top level:

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.

dhbradshaw··on Previous Covid-19 may cut risk of reinfection 84%
One interesting thing here is that this is working against selection bias.

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.

← PreviousPage 3 of 10Next →