A great (free!) ebook pdf is "Programming From The Ground Up" on the GNU site: http://download.savannah.gnu.org/releases/pgubook/
On Being A Senior Engineer
Ooh Aaron... :-(
Falsehoods programmers believe about geography
Falsehoods programmers believe about addresses
Falsehoods programmers believe about gender
Falsehoods programmers believe about networks
Falsehoods programmers believe about build systems
Falsehoods programmers believe about time
More falsehoods programmers believe about time
And honestly, a lot of "falsehoods" are really just nitpicking. I mean yes, you may once in your lifetime encounter a user with a real name longer than 2048 characters (or wherever you've set your limit) but really, if those are your biggest problems you're in a really good position :)
There should be a github repo and site that lists everything so additions can be managed.
Remember that fixed point does not mean the point is at the rightmost position. It means it is in a fixed position.
I'm doing all my math in fixed point (eurocent), but that has its drawbacks too if you deal with VAT and have to hit a specific total price given only a VAT rate and a net price... or if you're dealing with gas pumps and that x.xx9 cheating. Or scales, where the law requires more precision...
Don't get me wrong, understanding FP representation and arithmetic is useful for web developers, but the comment was on that actual article that was linked which goes into it in a level of depth that most web developers won't ever really need to dive into.
1 - http://www.akkadia.org/drepper/dsohowto.pdf
I have never done any special SEO tricks and yet all my content is fairly high on the results.
SEO in general is quite useless in my opinion. Make the content good enough so that people want to visit the site! Don't trick people to come there.
I'm not doubting your experience, but this is such a common misconception that I must point it out.
If usage of your product is not what puts food on the table, by all means go for the engineering marketing approach. It's genuine.
If you need customers to have a roof on top of your head, though, learn marketing. It's not evil, it is necessary, and strange as it may seem, it is as important to success as product quality.
The title should have been "10 Articles Every Java Web Developer Should Read," and even then a few of them would be out of place.
Otherwise you end up with things called "Go" and "Ruby", both of which took years to become googlable.
If you actually read the letter you can see that it also applies to modern programming and not just to "goto". Its truly a timeless article that everyone should read (and its really short!)
You could read it as a manifesto for solutions to callback hell which do not mess up your program's state, such as reactive programming.
... Except for the final one, "Packet Roundtrip". Networks have reached a physical limit of the universe, the speed of light.
On top of that I believe faster than light transfer of information has already been experimentally shown to exist.
Yes, there is. Information has to be carried by some form of mass/energy, so if mass/energy can't travel faster than light, neither can information.
> I believe faster than light transfer of information has already been experimentally shown to exist.
No, it hasn't. If you're thinking of the CERN neutrino experiments a couple of years ago, that turned out to be an equipment error.
edit: for anyone interested, there has never been a negative leap second (it's always been something like 23:59:59, 23:59:60, 00:00:00). see http://en.wikipedia.org/wiki/Network_Time_Protocol#Security_...
edit2: however, there are negative leap seconds in UNIX time. I wonder if there's a vulernability here? see http://en.wikipedia.org/wiki/Unix_time#Leap_seconds
It's a quick, easy read. It makes a point that is important and not hard to understand, but that is often missed. And it provides a framework for dealing with the concepts you get from all those other articles you're supposed to read.
Another way to think about it is that if someone doesn't understand a rule, then they are subject to the rule. If they do understand it, then the rule is subject to them.
Kirit is saying that, in the latter case (and only in that case) they get to decide whether to follow it.
One reason your idea works is that, in the first case, they don't get to assume that others are also subject to the rule.