How does domain collecting even work? Don't you have to continuously pay in order to renew your domain ownership? Even if it's $5/year per domain, surely at some point you have to stop collecting.
I think that was the owner being shortsighted. If the plugin was something that a reasonable fraction of your users would like to have, then very shortsighted.
Not only you had a person that already knew much more about your product than the average potential hire, but a person that probably was interested in your product (and maybe knew what users wanted) too.
I agree. I am most annoyed by the use of maxims with something so subjective and context-sensitive as code. I've read and written code with 4 (and maybe even more) levels of indentation that made complete sense and code with 2 levels that should probably be refactored into only having one.
I've seen people propose things as dubious as a character limit per function body. Most programming languages are so flexible that no matter what guidelines you set for your project, there will still be very bad code that conforms to all of them.
Forcing function splitting by rules is a good example of this. Very large functions are probably doing too much, but where and how you split them matters incomparably more than if you split them at all.
> The reason cited for this was that "a supported file system is required as Dropbox relies on extended attributes (X-attrs) to identify files in the Dropbox folder and keep them in sync".
Given that extended attributes are available in most of the filesystems used in Linux today, Dropbox still hasn't answered why they decided to go "ext4-only" for a while.
> The operating system is delivered in images that are created by utilizing the rpm-ostree project. The main benefits of the system are speed, security, atomic updates and immutability.
The article never mentions speed (or performance) again. Is the OS somehow expected to be faster because it is mounted read-only?
I agree that JS is not substantially "worse" than some other languages.
Despite these three languages giving far too much freedom to the programmers (which some might even like), high-quality code can be written in all three of them, as long as intelligent and strict coding guidelines are thoroughly followed.
I enjoyed the article, and I know that writing these takes a nontrivial amount of time. So I think it would be wise of you to run these through a spell checker before publishing, as this is a less than a minute investment which pays off every time someone reads it.
> Google certainly doesn't seem to value feedback at all.
As it is with most big companies that profit from ad revenue. They seem to consider performance indicators to be sufficient to know if a new feature is good or bad, instead of worrying about written customer feedback.
I think it is mostly an issue caused by how managers are evaluated. Do the teams you supervise outperform (in a short-term metric set) the other teams? If so, you are deemed a good manager.
Upper management usually does not seem to care whether the people you manage leave the company eventually or try to change teams to get away from you.
However, even if you were to pay the people behind the journal for their work it should be fairly inexpensive as long as they did as little as Elsevier does.
Good point. I think that by their logic selling "enthusiast" versions of anything will almost always be classifiable as a practice that "preys upon the mentally ill".