1,185 karma · joined September 11, 2012
This statement is false. Not all lightweight wallets (wallets that function without needing to download the blockchain) are SPV wallets. Some lightweight wallets use blockchain APIs (and therefore are immune to this problem)
Downloading the full blockhain is not the only way to secure bitcoin.
Instead I'd rather see people try to fix the problem of it being expensive to spend bitcoin sourced from many small inputs. This is a problem that the lightning network does not address.
So if the lightning network does get build, we'll all be able to use microtransaction channels which will slow the growth of the blockchain, but will still cost $20 in fees to send $100 worth of bitcoin sent in tiny UTXOs.
The main reason why I use django is because o the ORM and the admin. If I were to do a project in Flask, I'd have to build mt own admin, and i'd have to use SQLAlchemy. I had to use SQLAlchemy once for a project and I hated it.The django ORM is much more straigh forward an easier to use, in my opinion. In my 10 years of using django ORM, I have had to "break out of the ORM" maybe once.
I am a self taught programmer, I studied aviation in college but switched careers to working at startups since 2009. I do a lot of personal projects in my spare time (which you can find on my github). I've been at my current job for about 2 years.
The guy in the article pretty takes the same approach. I've always felt the best way to interview engineers is to go over installing the company's development environment on their machine. In other words, there is no evaluation, just expectation of results.
This snippet should only live in one place:
if (something) {
for (blah blah) {
something_else();
}
do_something();
}
on the other hand, this code can be copy+pasted as much as you like: do_something();
do_another_thing();
another_call();
some dogmatic programmers will want to place those last three lines of code into a separate function and instead copy+paste that. But I've found that doing that sometimes makes the code more harder to read.America is a free country, but not everyone in America is free (some are in prison, for instance).
I'm surprised apple hasn't added crossfeed functionality to any of their audio products. I remember discovering crossfeed back in the early 2000s. My audio player was foobar2000 which had a plugin to do crossfeed. When I switched to Mac in the late 2000s, I had to go back to listening to music without crossfeed. It still perplexes me that with the explosion of high end headphone popularity that this hasn't become a standard feature for audio players.
For instance, at my current job, I've been here for 2 years. I know the codebase pretty well. If an issue comes up, I can almost always get it resolved in a few hours or less. For this reason, I am currently a stack person.
On the other hand, when I first started this job, I didn't know the codebase very well, so it usually took me at least a week to complete a typical issue. Back in those days I was a queue person.
Secondly, I can never understand why some people get so offended by someone giving them a small amount of money. When you go to the coffee shop to buy a $2.40 coffee and are given $0.60 in change are you insulted by the cashier for thinking you needed that 60 cents?
def days_in_month(month_num):
if month_num in [1, 3, 5, 7]:
return 31
elif month_num in [4, 6, 9, 11]:
return 30
return 28Here is how I handle 'backups': I never do it. If the data is important, I make sure I store it on a device that is already redundant. If I take a photo that I really want to keep, I'll send it to dropdox or google drive or gmail or some place like that. Neither my macbook, nor my iphone, nor my linux laptop is the canonical living place of anything important. If any of those devices were to disappear, I will lose stuff, but nothing important. This system I've sort of subconsciously migrated towards over the past decade or so of hard drive failures and lost phones.
1. Documentation - If I have to spend the next month doing trial+error to get your API working, thats no good. The best APIs have a page that describes how get up and running quickly.
2. Good error messages - When something goes wrong I want to know what went wrong. The error message being in a consistent format isn't that important, as long as there is a description of what happened. "Oops, an error occurred, try again later" is not a good error message.
Most of the stuff in this article is superficial stuff that I don't think matters.
On the other hand, if the donation is big (say in the thousands USD), I can see why someone could decide to not accept the donation because they don't wan to report it on their taxes. An easy solution to this problem is to NOT TAKE THE DONATION. If you don't take the money, you don't have to report anything. The tip4commit site supposedly states if a developer doesn't accept a donation the money goes back to the 'project pool' where it will get donated to another developer on that project.
On the other hand, if its 2 months later and a fix still has not been issued, then it is safe to make the argument that the web is broken.