I believe he was comparing it to a similar broadband grant in a comidic fashion
solidsnail
joined 2 years ago
It doesn't necessarily mean that. It could also be that they attempt to block the rise of new platforms, and by doing so limiting the amount of platforms that they have to compromise.
Would've never expected this read to be so interesting.
Regarding section 1, won't you still get the conflicts when pushing to remote (or pulling from it)?
How is is this cyber security related?
And it's not P2P...
Jami is p2p for example. Direct communication between peers.
That's not being pretentious, that's being blunt. I personally as a dev, appreciate that.
If you think the code can be improved you should say that, and exactly why that's the case. When you're mistaken you should be able to take the criticism.
Your mission as a dev is to write the ideal code, and being overly polite can stand in the way of that.
He was probably working with bytes and not individual bits, but yeah. He basically wrote executables directly (to my understanding).
Point it out explicitly in your resume. Don't expect them to figure out your github activity on their own.
It's definitely better to have open source experience than no experience.