31–40 of 55 posts
Earlier quoted context omitted.
Just keep in mind that O(1) = O(1 + c). Depending on the relative size of n and c, you might want to stop and think :)
Happily, this gets amortized as n increases. So I just have to use Emacs more to make it worth it. A delicious proposition. (Hey, I should totally write a mode for browsing HN from Emacs! Then I'll have no need to ever leave :P.)
This is, I think, one of the classic splits between developers and sysadmins. Sysadmins are always logging in to unconfigured systems, new systems, foreign systems, and of course broken systems. Being fluent in sh, bash, vi (appreciating, but not depending on vim-isms) and knowing your way around every config file in /etc... those are basic tools for sysadmins. Developers should have the most productive environments…
Love, DevOps
This is, I think, one of the classic splits between developers and sysadmins. Sysadmins are always logging in to unconfigured systems, new systems, foreign systems, and of course broken systems. Being fluent in sh, bash, vi (appreciating, but not depending on vim-isms) and knowing your way around every config file in /etc... those are basic tools for sysadmins. Developers should have the most productive environments…
No, what this means for DevOps is that you'd better create a foolproof method to insert your dotfiles into the distribution - and that it's more important than ever to argue for individual user accounts, not role accounts, on production machines. For security and logging, of course. Love, DevOps
That's a terrible idea on so many levels, I hope you're being sarcastic.
Earlier quoted context omitted.
No, what this means for DevOps is that you'd better create a foolproof method to insert your dotfiles into the distribution - and that it's more important than ever to argue for individual user accounts, not role accounts, on production machines. For security and logging, of course. Love, DevOps
more important than ever to argue for individual user accounts, not role accounts, on production machines. For security and logging, of course. That's a terrible idea on so many levels, I hope you're being sarcastic.
Maybe one day it will be mundane to clone a tailored environment to a remote system. No changes outside $HOME and only in a controlled lifespan.
It sucks, but there is zero alternative unless you want to boil the ocean.
Ubuntu switched /bin/sh from bash to dash recently. Many distros are starting to abandon init.
It will get better. Until it does, our hands are tied.
free you from tweaking things and let you focus on getting the job done. my ability to adapt to a foreign environment without frustration is more important than the benefits of configuring a local environment to suit my whims This is overly simplistic. It certainly only applies to people spending a lot of time in foreign environments, which is not the norm unless you are doing tech support. I don't know if it's link…
Earlier quoted context omitted.
more important than ever to argue for individual user accounts, not role accounts, on production machines. For security and logging, of course. That's a terrible idea on so many levels, I hope you're being sarcastic.
You're saying it's better for sysadmins to all log in as "prod" or "root"? How do you figure?
Scattering user-accounts across machines is a maintenance headache (trust graph, sudo passwords or passwordless sudo, filesystem permissions) and encourages bad practices ("i'll just run this small script, quickly").
If you're serious about auditing then wtmp and notoriously incomplete shell-history files are not your tools either.
Earlier quoted context omitted.
You're saying it's better for sysadmins to all log in as "prod" or "root"? How do you figure?
Firstly on properly automated hosts you very rarely have to login. And when you do then 'prod' and 'root' work just fine. Scattering user-accounts across machines is a maintenance headache (trust graph, sudo passwords or passwordless sudo, filesystem permissions) and encourages bad practices ("i'll just run this small script, quickly"). If you're serious about auditing then wtmp and notoriously incomplete shell-histo…
Earlier quoted context omitted.
You're saying it's better for sysadmins to all log in as "prod" or "root"? How do you figure?
Firstly on properly automated hosts you very rarely have to login. And when you do then 'prod' and 'root' work just fine. Scattering user-accounts across machines is a maintenance headache (trust graph, sudo passwords or passwordless sudo, filesystem permissions) and encourages bad practices ("i'll just run this small script, quickly"). If you're serious about auditing then wtmp and notoriously incomplete shell-histo…