Thanks for the info

Inspired by @h3ll, this is a combination of current and former coworkers:

Awkward Wizard:
This guy has the social skills of a microwaved dog turd. He is a genius, but working with him is about as uncomfortable as sticking a grill skewer in your eye and twisting it repeatedly until close of business. He laughs at inappropriate times, and every time he does, an unborn child tears its own ears off. He explains things in a way that only himself and Satan understand, then talks to you like you're a child when you don't follow his logic. He is the guy you hide when the CEO is around. His code is immaculate.

Backstab McGillacutty:
This bowl of bile is the son of a bitch that takes credit for everybody else's work. When you do something good, he was miraculously involved, but when you mess up, this twat is the dicknose that brings it up in retrospective and calls you out by name to the boss. You can usually find these guys talking shit about the CTO, until the boss quits. Then they buddy up with the CTO and become a Joel Osteen-esque evangelist for everything the CTO wants in a shitty, underhanded attempt to climb the ladder. Fuck this guy.

Professor Fuckwaffle:
This coworker used to teach Computer Science classes. Their resume is amazing, and they can speak to the most complex of design principles. This is the shitstain that you hire because of their skill and knowledge only to find out that ol' fuckwaffle can't apply the shit they spout to save their wretched lives. You'll spend more time listening to fuckwaffle lecture than you will reviewing their code (because they cant fucking write any!) You know the saying, those who can, do, and those who can't, teach? Yeah, that shit was written for Fuckwaffle.

Last but not least:
Scrumdumb:
This guy isn't even a coder. This guy is worse than the the scum you pour out of the bottom of a slow-cooker that you forgot to wash last time you made chicken. He's a non-technical PM. You know the type, right? He usually says "cloud infrastructure," "paradigm," "algorithm," "SDLC," etc but has no grasp of any of them. He often opens his dumpster to spout off something like "You can just create a new class for that" while talking about HTML. I won't waste any more breath on Scrumdumb, he already creates enough work for me.

Fantastic sorting algorithm, O(1) runtime, so amazing

Never realized with a industry that changes by the second how relevant and timeless a single book(set) can remain. 52 year old book.

The work that knuth put into this collection to keep it timeless and language in-specific keeping it to theory rather than details of syntactical details is amazing.

Sure there are other timeless classics out there.. the algorithm book, K&R C, the dragon books, the wizard book.

But I think this single book outweighs them all in the abstraction point of view... AND it’s abstraction in the “opposite direction”... abstraction to a machine language architecture that is purely theoretical... brilliant.

He Didn't See That Coming

My very first wow, was back in 2011 as a freshman at university, algorithm classes. Our first language was Pascal, (because it was easy to learn and get to the idea of programming.) so, lecturer wrote Hello World! and that moment was the best part, when I realized that was called a program. After all these years I still remember this output. ❤️ awesome.
After this, its injected in my veins and soul. Even when I come home drunk or coming from the friends, I open my macbook and trying to write some cool , nerdy staff.

Its my life, my passion, my hobby. I dropped everything for this. ^^

Long story short, every time I feel amazing when I do something new and interesting.

So I have been a fly on the "wall" for last couple of months and never signed up, but now here I am!

Rant is about a serious topic - gender gap in tech industry!!
Couple of months ago Stackoverflow announced developer survey results! I was shocked by demographics results! It was disappointing to see biggest gender gap in general tech industry!
I believe tech industry can be the first one to have equal pay for women!

However.... (bad part)
I was going through my twitter feeds and saw this! Many of you have seen this tweet too.

(ohh!fuck I cant attach multiple images here, I should have created Medium post, fuck it!)

"They" continue, quoting from the tweet.
1)"....bias in society is reflected in AI"
2) "However, I do think it is our responsibility as designers/developers/users to be aware of this bias and do our best to correct it."

I want to rant about 2nd one. Some of you may not like it including grammar naziz!
As a developer/programmer I take 2nd one personally! I am currently at denial phase though!
And I have an OCD so gonna make points here!

1) Seriously tell me please, how the fuck you can write gender bias algorithm which can pass a big crazy amount of test suite?

2) Google has done many things for last decade to overcome gender gap related issues. I have met some of the nicest people from Google, and this is really hard for me to believe that google AI or that team has anything to do with the results!

3) Someone suggests use "they" in google translated result, can you fucking imagine how wrong that would be??? If I am developer working on that algo or even in that team and I see this ticket in jira with highest priority where it says, "make all translated results gender neutral using only they" - I would fucking like to die and may be in my next life ask me to do that, when I am a toddler!

4) I am an advocate for equal pay, equal rights and equal opportunities for everyone to "minify" this gender gap in tech, but showing google translate results of a gender natural language to make a point is wrong, it is simply undermining the efforts of something really helpful thing.

5) Moving on to the core point - What can be done to lower down the gender gap? I have seen amazing women who can code/manage far far far better than what I ever could imagine, and they are at really good place and deserve to be there. Are they doing enough to inspire other women to join tech industry?
Collective efforts are very much required. And need to keep in consideration that tech industry is highly competitive roles are also changing rapidly.

6) Many big companies have women at higher positions(CEO, CFO,....) what are their efforts to bring more women in tech industry?
(Some of you may not like this, as this is implying that it isn't only men's job. )

7) Going slightly political here, everyday we see really disappointing news related to women and their rights and health, I strongly believe women don't have to ask for or even have to mention about "equal rights" about anything. Everyone is equal!!!
This is 2017 and still fucked up!

Thats all for today! Heading for breakfast!

I've heard a lot of nice things about python so today I decided to check it out and HOLY CRAP this is an amazing language! Really makes me wonder why I didn't look into this sooner!

Seriously though! I looked at the documentation and official tutorials for like 30 minutes before writing a selection sort algorithm using only six lines of code. I'm quite mind blown.

What do you tell interviewers as a "Senior developer" when they ask you what you do at your current job.

I've been with my current for almost 8 years, since graduating... Few different time but not very well managed (semi/barely agile). Hasn't really provided any skill growth opportunities. Mostly fixing production issues, chasing other teams.

The projects I've worked on are in many different languages either enhancements or some standalone stuff. But nothing that's huge and I don't think I've learned anything from them. I usually apply what I learn and practice outside of work to work.

So to me I can probably list a whole lot of projects but to me their not that amazing, I didn't learn anything from them.

Also about those algorithm questions. I've never used any of this stuff actually at work. Concepts yes but not how do you implement ... And honestly I've never once had a situation that required algorithmic thinking other than maybe writing recursive functions in rare occasions...

But to me I've never once done anything harder or new which I haven't already done on my own....

Sorry for the disorderly rambling this turned into... which is sorta a problem too.

Everytime I think about interviews, I want to give rants about we technical questions are BS, how I probably have enough real experience to tackle any problem and come up with a good plan/solution (in a realistic timeframe, not 20 minutes from design to implementation)