4 ms·
We, sysadmins, are not programmers. Our job is to configure and manage systems. We know nothing about machine languages. Most of us use scripting languages, lik
by pyman 17y ago
We, sysadmins, are not programmers. Our job is to configure and manage systems. We know nothing about machine languages. Most of us use scripting languages, like python and perl, to automate tasks. So please, don't ask me what the difference is between a Service and a Repository class, because I have absolutely no idea. It's Chinese to me. So, programmers, stay ways from me, stay away from my environments, and stay away from my procedural python scripts.
Or I will replace you with a very small shell script.
- mahmud 17y agoWe know nothing about machine languages. Not too long ago, sysadmins sent kernel and driver patches upstream. And the true Unix beards have a .gdbinit file per-kernel that's longer than your CV.
- gnosis 17y agoOh, please. If someone has the time to write kernel/driver patches and muck around customizing his gdb config, he's clearly getting paid to be a developer, not a sysadmin. Very, very few sysadmins have the luxury of spending time on this sort of thing.
- mahmud 17y agoSeriously, haven't you ever met unemployed systems programmers? I have, they're a dime a dozen, and most happily take crappy admin jobs and 10-people insurance and travel agencies. I happily waited tables and poured coffee while writing compilers for fun. Technical competence does not in any way imply employment in the field.
- pyman 17y agoMost sysadmins don't know low level languages such as C/C++. I know a few kernel developers myself, and they are all C hackers. If you write Linux kernel patches, then you are a programmer that a) works for a company that builds hardware b) needs a driver that doesn't exist. Lets get this straight. Adding data to an Excel spreadsheet using VBScript doesn't make you an Office developer, if you know what I mean :)