88 karma · joined September 18, 2017
(Also, your bullets didn't format properly, you may want to edit your response to fix that)
Code on the white board? Why not on a computer? Why not work on some real code for the project? Sign an NDA and work on an actual feature. Try to get closer to what you expect the candidate to do on a daily basis.
I don’t even know if that is up for interpretation,
> I have nothing against tools like this. I’ve even contributed money to the Light Table project. I think that good software tools make it easier to write good software. However, tools are not the answer to the “Apocalypse”.
If this is indeed the article OP is responding too I can’t but help he was missing the point. The point is scheduling pressures lead to awful code because quality is cut.
It's not unique to Chrome. There are additional sync options that are available to Chrome, but those are all opt in.
Prove to me that Google is tracking me through Chrome. Link me to an article with proof of collection.
Most of us our developers here, surely we can apply some more rigor to this conversation then “we know Google is doing this because it’s Google”.
If implicit patent grants are a thing, why have more modern licenses like Apache 2 and GPL 3 made it a point to include explicit patents grants in the language of the license?
Wouldn’t their legal counsel advise them against it if it was redundant?
Am I missing something or does this make zero sense?
I still find it to be an odd requirement. I guess the intention is to keep people from misrepresenting your original code.
So for JPA entities, each field is marked as nullable, because in Java it is. If we need a null checked version we map it from the nullable fields object to a object that has been null checked and has non-nullable fields (where appropriate).
Wrappers can be written to interact with more traditional Java libraries that do a similar null check and mapper, keeping platform types from propergating intro other layers of the system.
Platform types make interopt way easier, but if you are concerned with null safety you have to write some code to deal with them.
Also what specifically is bad about the Apache 2 license?
I really wish it made clear that the license was irrevocable. I think the understanding in the community is that once you give permission for software to be used under a license you shouldn't go back on that, but other licenses, like Apache, make that clear.
The phrase "Any modification to the software submitted to the authors may be incorporated into the software under the terms of this license." could be worded better. I think Apache nails this, "Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions". This gives some wiggle room for submissions under different license, if they are explicitly called out.
Warning, if you end up getting this keyboard you will need to take some time to learn how to type on it due to non-standard design. I personally think it's worth it but for others that is a non-starter.