rich-tea

6 ms·

1.
by rich-tea 7y ago
You may well be right. I probably only notice it with software because that's what I do every day.
2.
by rich-tea 7y ago
Unfortunately this article, like almost all others, is still wrong because it looks like commits get mutated when you rebase and the old commits disappear. It is very important to understand that commits (in fact, all blobs) are immutable i
3.
by rich-tea 7y ago
That's because a file system is something you already understand, even if you've never actually used an old fashioned paper filing system. The software is providing you with something you understand. Git is not providing you with
4.
by rich-tea 7y ago
You're actually getting at something deeper which I've been noticing more and more lately. Many people seem really reluctant to learn how to use things. It only seems to happen with software. They see a program or a new language a
5.
by rich-tea 7y ago
Git is not hard. It's very simple. But people learn it the wrong way. You have to learn it from the DAG up. If you cannot grasp how the DAG works you'll forever be reading and writing articles like this one which do not help you t
6.
by rich-tea 7y ago
I refer you to the children's story "Crying Wolf".
7.
by rich-tea 7y ago
I actually thought the flag code disallowed flying the flag in bad weather. But I'm now unable to find any confirmation of that.
8.
by rich-tea 7y ago
It can contain a link to the list of all invoices. So you could have /customer/<cid>/invoice which lists all invoices for the customer which are actually just links of the form /customer/<cid>/invoi
9.
by rich-tea 7y ago
Is that based on the size of the vehicle? In my country it is not. It is only based on emissions. Some SUVs will pay less tax than a small sports car.
10.
by rich-tea 7y ago
You gained the ability to find the invoice. There is no need to have customer id in the invoice url. Just /invoice/invoice_id is enough.
11.
by rich-tea 7y ago
> When it storms and gets wet, it’s all I can hear inside my house. Isn't that illegal?
12.
by rich-tea 7y ago
I agree but I'd also like to see tax paid on size of the vehicle because it's literally using more of the public highway. So motorbikes would still pay less, probably. The SUV users say it improves safety. OK, they can pay for it.
13.
by rich-tea 7y ago
There shouldn't be separate endpoints that take an owner's ID. That's bad design. The owner endpoint should contain a list of invoices, ie. links to the invoice endpoint.
14.
by rich-tea 7y ago
Indeed. Hyperlinked serialisers are built in and super easy to use. And it makes so much sense when you use DRF's API browser too.
15.
by rich-tea 7y ago
Why does every docker image build have to pull the packages? Are you force rebuilding and defeating docker's cache mechanism?
16.
by rich-tea 7y ago
As usual it will take a disaster for people to realise it was a bad idea. Microsoft tried to destroy Linux in the past. Literally. Linux is what gave us git in the first place, and docker, and so much technology that we love today. Oh how q
17.
by rich-tea 7y ago
All of these advantages don't make sense if half your commits are broken versions of the software. Rebasing helps ensure that each commit is valid. That's important for the reasons you mention. Having a log of what you actually di
18.
by rich-tea 7y ago
I'm not talking about squashing the feature branch. I'm talking about squashing all of master down to one commit (initial commit). If you don't take care of your history, my question is why do you keep it at all?
19.
by rich-tea 7y ago
What do you use your git history for? History is either worth keeping, in which case you should maintain it like any other artifact, or it's not, in which case you should squash down master to a single commit every time you merge. But
20.
by rich-tea 7y ago
What I really like to do is make actual fixup (or squash) commits during a code review and just push these to the branch normally. That way reviewers can easily keep up with the changes. Right at the end, the maintainer requests that the or
21.
by rich-tea 7y ago
Oh, so your point is that bitcoin-specific problems aren't a problem outside of Bitcoin. Gotcha.
22.
by rich-tea 7y ago
I've read two pages of the article and I've still no idea what it's talking about. They're clearly going for the "shrouded in mystery" marketing approach, but I haven't got time for that. Can the title be
23.
by rich-tea 7y ago
How is it disingenuous? You said that heists were "vanishingly rare" outside of Bitcoin. As it happens, your cash in the bank is being slowly devalued via inflation as the banks are constantly making new money in the form of loans
24.
by rich-tea 7y ago
Really? https://news.google.com/search?q=Theft+stolen+-bitcoin
25.
by rich-tea 7y ago
Name a technology that isn't susceptible to crooks or incompetence. Bitcoin isn't worse than anything else in that respect.
26.
by rich-tea 7y ago
The UK has the "fit for purpose" clause in the Distance Selling Act and I think you can return the product at any time. I'd highly encourage anyone who is inconvenienced by this to exercise such laws.
27.
by rich-tea 7y ago
I was going to say I fondly remember PowerToys on Windows XP, but it looks like it actually goes back to 95. They were always one of the first things I installed after a regular reinstallation of Windows. Later I switched to Linux and reali
28.
by rich-tea 7y ago
What's your point? I didn't say anything about what HN is, I just said that it is in no way a "diverse" group of people. Honestly can't see how anyone could think this is diverse.
29.
by rich-tea 7y ago
Risks to other people is also known as responsibility and that should also be accounted for. But sometimes there is an imbalance. You can be putting others at risk but not be properly considered responsible. I think there is a lot of that i
30.
by rich-tea 7y ago
> Not sure who 'us' is; HN readership is pretty diverse Do you really believe that? 99% of us work in offices. You're in a bit of a bubble. Try going to a working man's club or the equivalent in your country to get a

More ›