I’m 42, never went to college (I joined the army) and am now a Principal Security Engineer at a serious computer security firm. I’ve got a background in Linux high performance computing and software engineering.
If I can do this, anyone can. I believe in you internet friend. In tech, every day’s a school. Embrace it and learn something new daily, or get left behind. You’ve got this
Oh yes, because the well documented clean syntax of sys v init shell scripts was so nice.
If I never recall hacking in ulimit calls in the top of buggy shell scripts for crappy old services that done respect pam_limits it won’t be soon enough.
My poor fellow. You wrote about how something is a bad tool for a long list of serious reasons. Then it failed spectacularly because everybody decided to depend on it anyway - exactly what you were cautioning against. But somehow you have to respond to people who think you are the one who got it wrong! As a third party the whole affair gave me a good chuckle at least ;)
Even if example.com is unsigned, the delegation from .com to example.com will still be signed (including an attestation that example.com is unsigned). So lack of DNSSEC adoption by users of the TLD wouldn't save them here.
I believe tools like graphify cut down the tokens in thinking dramatically. It makes a knowledge graph and dumps it into markdown that is honestly awesome. Then it has stubs that pretend to be some tools like grep that read from the knowledge graph first so it does less work. Easy to setup and use too. I like it.
Michael Meek’s referenced blog post. The irony is I remember him championing openness for OpenOffice and I remember how transparent he was when he helped found libreoffice and TDF. What a shame we have devolved to this situation.
reply