1,604 karma · joined March 1, 2017
I find myself using markdown files these days to store my links. That way I can also store context around the links by writing stuff around the links. This sounds foolish, but it does in fact check all your boxes:
- You can publish this markdown file on GitHub pages so it has integration with browsers
- People can follow you using RSS (yes, people still do this, myself included)
- I use Epsilon Notes and FolderSync Pro on my Android device to sync the markdown files over Dropbox so there's mobile app support
- Portable across time because it's just text
- Widely supported by different tools
This is actually also my note-taking system. I have shortcuts in them that allow me to take screenshots and store them next to the markdown and link to them. I store links by simply making a link in the markdown file of the paragraph I'm working on.
This is not a shakedown. Google is only responding to people who are placing ads on their ad platform. They aren't denying anybody food or shelter.
If anything it's interesting that so many advertisers want to advertise against that keyword. Really it's not Google that the author should be angry at, it's his competitors who are paying a lot of money to compete with him.
I often find the most painful employers and experiences are the ones that I gain the most out of in terms of development and growth. Not fun to hear in the moment but afterwards it's a gift.
> Enclaves are fully isolated virtual machines, hardened, and highly constrained. They have no persistent storage, no interactive access, and no external networking. Communication between your instance and your enclave is done using a secure local channel. Even a root user or an admin user on the instance will not be able to access or SSH into the enclave.
> Nitro Enclaves uses the proven isolation of the Nitro Hypervisor to further isolate the CPU and memory of the enclave from users, applications, and libraries on the parent instance. These features help isolate the enclave and your software, and significantly reduce the attack surface area.
So it sounds like one virtual machine attached to another virtual machine via something like a point to point NIC. At that point, why not just have that program on its own VM? If the answer is "because I don't want other programs on that VM to get access to it", my response is that you simply don't have any other programs running on the machine, you can list the program as the init process for example.
That's effectively just what they're just doing here.
1: https://gist.github.com/richhickey/1563cddea1002958f96e7ba95...
> PyPI wants me to enable 2FA just because I maintain this package, which I don't care for. So this package is now unmaintained.
Just set up a KeepassXC file and put your 2FA info in there? You don't need to give PyPI your phone info, PyPI takes TOTP[1]. 2FA is pretty normal; I don't see why the author has a problem with it. It doesn't violate privacy (since it's not actually tied to any PII like a phone number), it takes like 10 seconds to set up, and it protects your packages from hackers. Perhaps the author simply doesn't see the point of 2FA, since he implies the PyPI authors only did it for compliance reasons (and not for normal bolt-your-doors security reasons, which is more likely)?
He calls setting up 2FA "an expense of my free time" when surely it took more time for him to delete and re-add his package than it would have to just set up 2FA.
EDIT:
To be fair, the maintainer owes us nothing[2], sure. But it's not unreasonable to protect the larger community with basic security practices, either.
1: https://pypi.org/help/#twofa
2: https://gist.github.com/richhickey/1563cddea1002958f96e7ba95...
The contrived example would only ever happen if the developers in question didn't talk to each other. A lack of coordination is the real problem and cannot be solved by tooling. You can never tool your way out of a communication problem.
Or maybe just:
1. Catch this during code review?
2. Run unit/integration/regression tests on PRs?
This just feels like another post from a vendor who wants to "sell you a DevOps" when proper culture and process is probably the better answer.
1: https://www.wingolog.org/archives/2015/11/09/embracing-conwa...
2: https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
ed $file << COMMANDS
g/^#.\*$/d
/yaml_key:
s/^/#/
w
q
COMMANDSUntyped languages are excellent for smaller code bases because they are more comfortable to program in and faster and more general. Types of polymorphism possible in these languages are simply not possible or much harder in typed languages. Also, as others have said, the problem domain may not be as explored yet.
Typed languages really start to shine as a code base gets huge. In these instances well maintained untyped language code bases start collapsing under the weight of their own unit tests, while moderately well or poorly well maintained instances of untyped language code bases become a mess. Mostly this is due to difficulties in communication when the code base gets worked on by so many people that it's hard for them all to communicate with each other. In these cases a typed language keeps everyone on the same page to some extent.
Both camps will hate me for saying this I think, but it's what I've observed over the years.
It also may sound like I prefer typed languages, but in fact my favorite languages to work in are Clojure and Python. My code bases as a DevOps engineer rarely pass the 10,000 line mark and never pass 100,000 line mark. It's much more comfortable for me in these untyped languages.
Untyped languages also really shine in microservices for the same reason.