int_handler
* Parents of Justina Pelletier sue Boston Children’s Hospital: https://www.bostonglobe.com/metro/2016/02/25/parents-justina...
* The Case of Justina Pelletier Still Requires Nuance: http://www.harpocratesspeaks.com/2016/03/Case-of-Justina-Pel...
* The New Child Abuse Panic: http://www.nytimes.com/2015/07/12/opinion/sunday/the-new-chi...
Why this society and these millennials believe they are entitled only to good things, positive experience and rosy road ahead?
Of course, only millennials care about improving workplace conditions, and all millennials are whiny entitled crybabies./s
The "professional" market doesn't care about visual cohesion.
[citation needed][0] http://www.thefiscaltimes.com/2015/03/19/85-Trillion-Unaccou...
If you really want to be outraged by a waste of taxpayer dollars, I would recommend that you take a look at how much state governments are overspending on prisons vs education [1], wasteful spending in defense [2], and the $8.5 trillion in unaccounted taxpayer dollars spent on defense [3].
[0] https://news.ycombinator.com/item?id=12793035
[1] http://money.cnn.com/2015/10/01/pf/college/higher-education-...
[2] http://www.foxnews.com/politics/2015/10/29/where-did-us-taxp...
[3] http://www.thefiscaltimes.com/2015/03/19/85-Trillion-Unaccou...
Most tech companies invest in things such as culture, internal productivity tools, and developer and testing infrastructure that are not deliverables to clients and thus not billable. While these may incur a higher start-up cost, these are critical for ensuring long-term productivity.
Correct me if I am wrong but my impression is that the consulting world is much more concerned with delivering and then moving onto the next project, with very little shared work or infrastructure between projects.
I'm sure 18F has areas of improvement for how it spends its resources and how it tracks costs and billing. Every organization does. However, I would not be surprised if the reason 18F exists is that the government found that outsourcing this work to consultants led to higher costs and lower quality deliverables compared to products being released by tech companies and thus wanted to try a different approach.
The 10-month investigation by the GSA's inspector general
found that 52 percent of 18F's work was unbillable and
included an internal project to change its logo by altering
its font, alignment and background color. In all, 727 staff
hours, or $140,104, were spent on developing the brand,
including that logo change.
It seems that the author is intentionally obfuscating this point and making it seem as if 52% of 18F's work was put towards "making the logos look hipper," which is likely not the case. While "developing the brand" includes logo work, in most cases, that is just a small part of it. Developing a UI design spec, similar to Google's Material Spec [0], would also fall under "developing the brand."Perhaps someone from 18F can speak to whether developing the U.S. Web Design Standards [1] is part of this category because if so, I would argue that spending $140k (which is roughly 1-2 software engineer annual salaries) on such a project is certainly worthwhile since this spec is part of the foundation for many future projects.
Makes you wonder whether the author and the poster are affiliated with one of those old-school government consulting or contractor companies that would gladly see 18F disappear so that the government would outsource the work instead.
If your organization values the existence of a standard over technical excellence, then there is no use in convincing you. Otherwise, in terms of ease of use, performance, tooling, and human readability and writability, Protocol Buffers is superior to XML-based protocols (since the API for converting between the binary and text formats is extremely simple to use).
As a fun fact, if you really wanted to use XML as a wire format, you could even write an XmlFormat ser/de for Protocol Buffers, similar to the JsonFormat that is already provided, but then it would defeat one of the main purposes of using Protocol Buffers in the first place because you would replace an extremely performant wire format with an extremely sub-optimal one.
The proto text format is actually more flexible and less verbose than JSON since it does not require the outer enclosing set of braces and quotes around all the keys and has support for comments.
Here are a couple of examples of config files using the Protocol Buffers text format:
* Bazel CROSSTOOL: https://github.com/bazelbuild/bazel/blob/master/tools/cpp/CR...
* SyntaxNet: https://github.com/tensorflow/models/blob/master/syntaxnet/s...
[0] https://developers.google.com/protocol-buffers/docs/overview...
[1] https://developers.google.com/protocol-buffers/docs/proto3#j...
To illustrate: Protocol Buffers' wire format is much more compact. It removes the complexity of having to deal with XML parsers by providing classes generated from the message definition/schema. You can use it with GRPC to implement your service APIs. It is supported for many different languages, including Java and C#. It now even has a JSON mapping [2]. Overall, Protocol Buffers can do everything XML can do as both an exchange format and as a configuration language but better.
[1] https://developers.google.com/protocol-buffers/
[2] https://developers.google.com/protocol-buffers/docs/proto3#j...
* Ant/Ivy * Maven * MSBuild * NuGet package configs
I agree with this 100%.
What I don't understand is why many developers argue that this principle does not apply to code and that we shouldn't have line length limits "because it's not 1970 and we have large monitors." If long lines of prose is difficult to parse, then long lines of code are even more cumbersome to parse, especially when you are either 1) slowed down by having to scroll horizontally all the time or 2) distracted by the awkward naive line wrapping done by the editor.
I do not think that is a valid comparison. The author did not go out of her way to point out that the server was located in China. There is no mention of China in the title, and the only place where the author mentions China is several paragraphs in explaining how and where the data is transmitted. There are more mentions of China in this comment than in the entire article.
Finally, for the record, I do not have a verified email associated with this account and thus do not have the ability to downvote.
If the author had instead attempted to tie this to, say, past security breaches caused by hackers operating out of China, then that would be framing the situation in a coerced way.
> But if you’re not home, your phone sends the command to a server in China, which then passes the command along to the socket.
> The result is that the unique network ID of your socket is transported in an unencrypted form to the Chinese server — and anyone who gets their hands on the ID can then control the socket.
The problem with tying this to the other security breaches caused by Chinese hackers would actually make this article _more_ sensationalist because that would allege that this company is somehow affiliated with the hacking activity.
If the company and server were located in other countries other than the US, it is highly likely that the author would specify the country as well.