HN user

danieljacksonno

155 karma
Posts1
Comments55
View on HN
Writing is thinking 12 months ago

It seems obvious to me. Just like drawing and sketching helps thinking about design, coding helps thinking about programming.

It's one of the reasons for the "one to throw away"-idea of writing shitty code first just to get it to work, and then remake it after you have thought through the problem by coding it.

Trump has several times threatened to take Greenland, by military force if necessary. He categorically has "not ruled out" military force against a NATO ally.

First source, but there are many: https://edition.cnn.com/2025/05/04/world/greenland-annexatio...

This has, for obvious reasons, been huge news in all of Europe and especially in Denmark.

I'm sure MAGA Americans want to hand-wave it away, and since Trump is so difficult to understand and says so many whacky things, we're all hoping he doesn't mean it, but it's underscored the need to quickly get independent of the USA.

I had the same reaction. It's a one time password, so it does not need to be as secure as a permanent one, but it still feels silly to have a long password that you can just type the first few characters and have it auto complete each word, versus just having a shorter password to begin with.

That said I can see how autocompleting from the first three letters of each word for "beaver-grass-hypocondriac-shelf" might be easier for a human than typing "beagrahypshe"

What? Of course they should. It shows they care about their customers, and that they are confident in their use case and honest when they say what they are a good fit for or not

The question is what is legal or not.

The US has laws that give them the legal right to snoop on any data about EU (avd other foreign) citizens.

Those laws make it impossible to follow EU privacy laws as a US company.

One of the two have to give, and the US should make exceptions for EU citizens, or rescind the CLOUD act.

I'm trying to pay for Kagi search to see if it's better. Not sure if it is, but at least it's not worse. In my tests they seem to get most of the results from Google, but just jumble them about a bit. They do have a "programming" mode though, which is useful.

If nothing else, it's refreshing to pay for search, to support non-ad-driven revenue models for the most important feature of the web.

For SOWs, I find that it helps to keep them very explicit about the larger goals and the "why" of the project, but vague on details, and then enter into an agreement where the customer pays you to keep scope at a level where the larger goal and "why" can be accomplished within budget, not into an agreement where the customer controls the scope and you just balloon the budget if they increase it.

Stop billing hourly. Instead bill for the value you provide. How you provide it should be immaterial, and so you can do it as cheaply and efficiently as possible while still reaping heaps of money as long as it creates value.

That's how all other markets work. Billing hourly is the death of progress.

I think the difference is not in the amount of layers between an IC and the top - but the amount of layers between the customers and users and the top. As long as c-level still keeps on touch with reality outside the org and doesn't depend on truth being filtered through four layers you might have a chance

Dear Chess World 4 years ago

He only (recently) admitted to those two cases because he was publicly outed. It seems extremely unlikely that the only two times he was caught was also the only two times he cheated. I think it's very probable he has cheated dozens or hundreds of times and not been caught or not been publicly outed for it.