MS office apps are full of pig shit,
. No doubt about it!

I am copying this to keep it like a reference manual.

Kickass advise!

@peaam, you are one hell of a kickass senior dev!

Salute

@molaram seconded

What the fuckidy fuck is that...

@electrineer Even I am surprised 😀

@AkshayTolwani I already checked that twice 😅

The IDE you are using has to be really dumb to be unable to locate a missing semicolon in your code.

What the clusterfuck😂🤣😂?

I think this guy is intentionally brainfucking the whole SO community.

@dder thts c# you looking at

@netikras I totally get the point you are making its IoC's headache to spinup and provide the instances as and when required but consider a usecase for a domain that fairly utilizes interfaces, abstract classes and base classes, then you may need some convention to paint a clear picture to make it easy for new members joining your team to navigates through the codebase. I am just talking from a readability standpoint.

@netikras emm, but how would you make your code readable enough to identify you are using an Interface or an abstract class across an inheritance chain for example?

@myss some devs are way sensitive about using _ with all the private properties. But I hate seeing those "_"s spread across the whole class file with no valid reason.

ohhhh fuck😂

@dder you seem to be having one hell of a time mate, the surroundings are awesome!!

@endor 😃 na na, I knew what you meant by OP

@endor no man, that was unintentional, I recently reset my OP and forgot to switch that fuckin watermark off, even I myself I find it creepy. Next thing on my todo list for sure..

@netikras you guessed it right 😀

Credit to morons who wrote GDPR. Now every site you visit, you have to push that annoying ok button for the cookie policy.
To get rid of ads i use Brave Browser.
Thanks to Brenden Eich who is committed to make internet less annoying.

I am a full stack dev and recenly did a POC around GraphQL for one of my upcoming Projects. I know the support for GraphQL is not really good for NET, but for NodeJS is pretty good. There are a couple of benefits I did like, for example, I don't don't have to declare a new endpoing everytime I have to write an API and underfetching and overfething problem it solves. What I didn't like was the idea to declare a seperate GraphQL schema in addition to my DB schema and when consuming the endpoint every call needs to declare the list of fields it needs.

@inaba even if you find some examples they are so vague that they hardly address the real use cases. And when you fit some higher order observable together, the chain becomes so messy that at one point you feel, why the fuck don't I just use $.ajax and be done with this pile of garbage.

Error handling in sequential http calls and to track which call failed and execute Fail code block so bloody painful

@Orek I hope it's worth the pain and frustration.

@DOSnotCompute Would you mind telling us what's you work profile that requires you to have such a gigantic and amazing setup?

a clusterfuck of all sorts

Yeah thts a good idea!

@devTea, I have not signed a bond but I do sometimes feel the right thing to do is start looking for opportunities. A quick switch though may not look good on the resume :(

@DuckyMcDuckFace then start taking good care of your brainchild. Good Luck

@khateeb321
So by DI I meant, Dependency Injection frameworks like StructureMap, Unity or Castle Windsor.
As I see in the screenshot you shared, you are creating repository objects with new keyword in the controller and you have already written you repositories against an interface. This is where, instead of creating those object manually you can handover this job to a DI container.
Then parameterzing the constructor controller like ChangeRequestController(ICRGeneralInformationRepository repository), the DI will automatically inject the instance of your repository in the constructor.
http://structuremap.github.io/
Let me know if this makes sense :)

@khateeb321 why arent you using any DI framework instead of pushing new everywhere. Just curious.