>> Clearly you're not going to be working on bugfixes, so why should it be deployed? > What makes you say that ? "Do not compromise". That's what "do not compr

>> Clearly you're not going to be working on bugfixes, so why should it be deployed? > What makes you say that ? "Do not compromise". That's what "do not compromise" means. If you do your work without getting those things you have demanded, then you have compromised. > And half of the world likes Kim Kardashian so what ? My point was that I don't pride myself on being a BOFH. Apparently it's not okay to say "I get along with colleagues", but it's totally okay to say "I make the standards that people in other companies follow like groupies!". Sure you do, mate. Sure you do. > You are not being proffesional then. You demand time of others to do your work, because, hej, you do your best, right ? When I say "Hey, devs, this error is appearing in the logs on production - the logs you wrote for the application you wrote - please look at it", the one who is not being professional is the one who says "I'm not going to look at it until you troubleshoot the issue to the degree that you can write a script that replicates the error". > and ability to script in the middle of the night You mean the time that devs are never around? It's a bit rich you complaining of sysadmins 'not working after hours'. > But in my team I will demand you know how to write 50-100 line scripts. If you can't do that, then you are emberresment for your proffession. a) Even if English is not your first language, if you're accusing someone of being unprofessional, learn to spell the word. It undermines your jibe when you can't spell an insult about professionalism. b) I can write the scripts. Clearly your troubleshooting is so atrophied that you can't see that I'm talking about the process and incumbent knowledge, not the ability to code. Yes, I write scripts, but no, I don't know what internal code doo-dad you devs thought to change in your last stand-up and pushed through. Why the fuck should the guy who is not intimately familiar with the codebase be the fucker that has to waste their time hunting the snark, then coding up a test for what is, to them, a (somewhat) black box? > GUI-only, Click-Next, no-value-add Admins will be replaced with a new type of Admin Again, fuck you too. I live in terminals. You're the lazy guy that wants everyone else to do the work. I'm saying that the person who knows the application should write the replicator script - you're saying the person who reports the issue should write it. God knows how you take a bug report from a non-technical person. I guess it just gets auto-marked WONTFIX. Certainly you've learned more about the politics than the technical aspects of the industry. "I write stuff the whole country uses!" carries much less cachet when it's a small Balkan state known more for nepotism than for a strong technical sector. Especially when you also say "you can't force anything on someone working in gov", given that government software projects are rarely known for their excellence. But keep on bragging, eventually you'll find someone who listens to the brag rather than the technical merits.