***Interviewing potential sys admins so us devs don't have to build everything and run everything***

Coworker: Do you know how to use cron and cron jobs?

Candidate: Yes I'm familiar with setting up users and permissions.

Me: 😳

Coworker: 😳

Boss: We will give you a call have a good day.

If you had just admitted you didn't know but we thought you could learn we might have been open to teaching you but brazenly acting like you know something when you don't is dangerous if you're running a multi thousand user production system.

Before I took on my current position (internal transfer), I stated that for what my boss asked for I would need a small team.
He agreed to that and promised I would get 2-3 developers.
6 months after (with countless reminders) he told me I could train some people at one of our providers.
Turns out those guys were Java developers, even though I asked for C# (since our codebase is .net)
After a few training sessions, where concepts as source control were a big topic ("why not just copy the code to a new folder with _good_ naming?"), I gave them a test assignment.
After reviewing their code I just gave up. They cannot program. They don't understand concepts like scoping of variables. Concepts of separation of responsibility.

I told my boss this but I had to make it work with them.

I went to my bosses boss (Head of IT) with my resignation in hand, since I felt my boss didn't want to support me actually getting a team. After a few talks I was asked to "keep it cool" and wait until he presented his new organization.

Now my boss asked me for which skills new developers should have. To which I could just laugh at him and forward countless mails from the last 6-8 months asking for developers.

<Irony>I love my boss</Irony>

Have any of you pitched a directional or starting idea to bosses and have it go well? I feel like I'm at such a low "worked bee" level is have to send a lot of time preparing data to back up the idea. Also not sure if I should go to immediate boss who is cool but a little reserved about ideas like this or boss's boss who has more leverage to put an idea like this in action?

//long rant ahead!

I need to plan a Wiki with SharePoint for not connected Sites.
Im now in dispute with my CoWorker since 3 Months, this is how the conversation goes. My two bosses are involved in this and also unhappy about SharePoint.

[C refers to CoWorker, M for me]
C: Hey, we finished SharePoint with Selfservice Storage Rooms. They even have a Wiki.

M: Okay cool, will check it out

C: Well we need to also plan the Wiki inside, I already asked our Department Head and he agreed, that you will be the one.

M: Okkkkaaayy, normaly it's your job to do such things, but welp, I will look into it, if we can work with it.

(2 Weeks pass)
M: I checked SharePoint out and tested everything. The Wiki is a Nogo, we need a other solution or programm for ourself a Wiki Integration/Engine. Did you maybe check out Confluence? It has also a SharePoint integration plugin.

C: We wont do Confluence, too expensive (already overspent the budget for SharePoint in six digits 🤬). Also we wont add to SharePoint Custom Code, it needs to stay standard.

M: Thats impossible, SharePoint Wiki is shit and also handels sites just like documents, no brain behind! Also you overspent the Budget and now it's my Problem?!

C: You need to do the best out of it.

(3 weeks passes and we get a meeting with the department heads)

M: Alright I made a UseCase and documented where the essential flaws are in SharePoint Wiki and why we cant use it.

Boss: Ok if it's impossible to use, then we will stay on our Fileserver for Documents and wont use SharePoint.

M: Thats not my Point, my statement is, as status today, SharePoint Wiki is not the right solution, code or buy software to it.

Boss: We will do a Prove of Concept, if it doesnt work then we will aboard it.

M: Well it is only some missing essentials, like hierarchy and Groups for the Pages, Example Confluence has this. If we could built in this features in SharePoint, everything would work out.

C: (angry) I told you that we wont use Confluence!

M: (calm) I said we need Features, not Confluence. Please mind the consent.

(3 weeks passes, and one more meating with bosses)

M: alright here again is a analyses, why already in Theory the current SharePoint Wiki wont work. It's already flawed in the core.

Boss: Yea SharePoint is crap, I checked out confluence and thats a real Wiki.

C: Well I dont know anything about Confluence and never looked at it. But if SharePoint is a fail we need the Proof of Concept.

M: Why do we need to do a Proof of Concept, when it already doesnt work in Theory! Thats nonsence and unlogical.

Next meeting will be in 4 weeks and I will give him the FUCKING PROOF OF CONCEPT. I will be a Bastard and build behind CoWorkers back a Confluence Wiki to show the Departmentheads how to built it right.

I hate CoWorker now, he makes a part of my loved Job a hell, I will goddamn cuk Coworker to space, that fucking Cukatron of lazyness and shit 🤬. I provide the Solutions and you just say no, how dafuq will the project advance, if you always say NO! Are you so unflexible and fixed on your Castle of Ignorancy!

!dev philosophical

Quality vs Opinion

I have a feeling that these things have always been at odds with each other and now with the constant connectedness it has just become more apparent that most people don’t understand the difference (or even realize there is a difference for that matter)

Let’s face it. Most people have awful taste. They listen to whatever new music their radio station decides was hot. They watch whatever show everyone else is watching. They are manipulated by large scale news organizations...

Basically, most people are sheep.

The problem is that sheep are a dangerous combination of loud and stupid. Giving these loud stupid sheep a platform to amplify their voice is a bad idea for a society, but a great tool for the pigs to manipulate them.

“Frightened though they were, some of the animals might possibly have protested, but at this moment the sheep set up their usual bleating of "Four legs good, two legs bad," which went on for several minutes and put an end to the discussion.”

This isn’t confined to one political party or view, it isn’t geographic, it isn’t based on education, it isn’t based on wether a person is ethical or not...

It’s universal.

You can translate “four legs good, two legs bad” into Agent Orange and his followers chanting “lock her up” just as well as it could be translated into the angry leaders of the modern feminist movement.

In both cases (both on opposite ends of the ethical spectrum) you have the loudest dumb, angry sheep getting the even dumber sheep to chant along, wether it is good for them or not.

Now to loop this back. The problem is that dumb sheep are emotional. They truly believe that they are NOT dumb and that their opinions and emotions are a measure of quality.

I FEEL bad, and you are talking to me, so you must BE bad.

I don’t LIKE this amazingly well made movie, so it must BE bad.

And anyone else who has a different opinion is just wrong. Anyone who try’s to explain the merits of the other side is either my enemy or is stupid.
^^^
Their opinion, incorrect.

————

Now for the tough part...

Most likely, based on probability, you are a sheep.

Yes, you! The smartest person you know. The guy/girl who has a degree or masters of a PHD. The person who builds amazing software. You! Are. A. Sheep. And you are dangerous to the world.

To put a cherry on top.

No, you opinions are not important. Your feelings are fucking meaningless. Your morals are worthless. Your voice has as much value and a loose asshole fart from a fat guy trapped in a deep well in Siberia.

But don’t get down about this. It’s doesn’t make you any less of a person. Remember that almost every person who has ever lived in history has been a sheep. They have chanted one useless, dangerous, misguided, harmful chant after another through the ages.

————

To those of you who try not to be sheep. Just keep trying to get a little better every day. When someone says...

“We do it this way because we have always done it this way”

... be skeptics. Explore the merits and logic of the situation.

And if you are tired of being led by stupid sheep then save some money, build something cool and start your own business.

Just remember, you will always need the sheep. They will be your employees, your friends, your bosses, your investors etc.

Treat them well, don’t hate them, and if you ever find yourself leading a pack of sheep then try to keep a healthy distance from their chanting while leading them down the right path.

They will thank you for it in the end.

———

PS. For those of you thinking “this is very judgemental and self centred”

All I can do is to try to speak your language....

Baaaahhhhh, baaahhhhh, bahhhhh

Which translates form sheep to human as...

“Eat a dick. Have a nice day”

I have a great chemistry with this coworker.

He lacks some depth of android knowledge but is always very interested in adding new google libs to the project, so we often discuss and come up with the safest, scalable solutions.

He is SE2 and I am SE1.

But one thing that is interesting about him is the way he gives estimations for the tasks. He takes usually that much amount of time that i would take, for a task, but he would quote half the time estimates.

the bosses usually come on the last days to check the feature demo, but QAs gets the first build when a task is completed. I have seen his first builds that goes to QA and most of the time, boy it has some amazingly stupid bugs.

dude would just put a util function, then run the build, if everything compiled, he would just give the build to QA directly. he wouldn't even check that the util function gave an expected output or not.

He is simply wasting QA time n efforts, and risking product quality by not testing enough, but he almost always gets a clean chit for this behavior just because he did the work super fast.

Dude is super cool and i don't envy him for his good luck, but rather think of him as an inferior dev. However bosses think of him as a better dev and my TL even once told me to "be like him"

So i guess this is how corporate works. I will try to apply this in my next role in current/next organisation.

Mu first two bosses were cool. Always defended us when top management come down. Will show with evidence that it is others (non-IT personnel in other departments) are clearly at fault and not us. But when they leave, will tear us a new one because lets face it, we were not that innocent 😅. Still, always kept us clean and out of trouble from the big guys.