I fucking want to skin alive my engineering senior director and VP.

Fucking piece of shit people. Looking at their faces from behind the screen, I can sense them stink doneky balls.

They have made my life hell.

The entire tech architecture is absolute shit in nature and engineers cannot even build a single blue colour button without creating a major fuss about it.

Every single aspect of product is built kept in my only the engineer persona. Everyone else can go and suck a racoon's dick.

And they have no concept of tech debt. They just keep building and building stuff. And then build some more.

Entire engineering org is in rush to ship shit at the end of sprint and if they don't then VP and Director are pissed. So to keep those two half witted donkeys happy, these people ship garbage. And all they comment is "cool, very cool".

And hence, entire fucking product is built because it's cool irrespective of whether it solves a problem or not.

A single user role authorisation or authentication is so fucking complex that it would take an eternity for even a developer to figure what's happening.

Fucking toxic human wastes.

There's a company wide mandate to use a certain tech stack, design guidelines, and a vision that all teams have to align. But these faggots are going in opposite direction to do what they feel like and forcing everyone else to ignore all other engagements or alignments with other teams.

These two people should be skinned alive in town square during noon and then left there until they dehydrate entirely. Fucking baboons.

I am so fucking pissed with such mindset.

What's all the fuss about Message Queuing? Why so much hype and noise? It's just literally message Queuing? What are use cases?

I'm moving from back end C#(self taught) and want to learn how to build effective ecommerce and administration sites. I've built a few web apps with old ASP.Net tech before but not MVC, I'm gonna dive right into MVC 6, what's all the fuss about Angular JS? I suppose I'll have to pick up 1 javascript(arghh! ) API, which is the most mature and/or best for rapid design and easy data management?

Learning C# coming from Java...
What's the fuss about properties? As i see it, theyre only usefull for binding, as else they just work as syntetic sugar instead of getter/setter methods.
But properties are also limited to give response back, like a successfull set, unless you start throwing exceptions..
And if a set property has if(age>5){this.age=age} then if i pass the property a 4, you will never know as a user that it failed (again, unless you start throwing exceptions)
Im kinda feeling like i want to use get/set methods until i need to bind, then of course use property ?? Am i all off here?