So I'm a BI consultant, been doing this for about 6 years now, and I'm pretty good at the data stuffs. Now I had to complete a project for a client where we call a web service and it had to be done in .NET. I wrote a console app in C# that called the WS, dumped the data then a stored proc processed the staging tables into final tables that our visualization tool can consume.

It works, it's done.

Mind you I'm not a pure .NET developer.

And now that it's completed and working this fucking .NET dude that works for my client is basically giving me an attitude talking about "why wasn't it done as a Windows service? Blah, blah" Like WTF!!??? I get that he's the C# BSD but like chill bruh!!

It's annoying as fuck having to work on projects that are not your area of EXPERTISE and then be ridiculed by other elitist assholes about it.

Doesn't happen much, but fuck it's something I hate about dev. FYI, if it was the opposite I would just be asking questions for understanding, not being a sarcastic prick.

//rant done

  • 2
    Feel you, sadly the dev community is riddled with fucking pickled shrimp dicks like that, they offer no value and is probably better left ignored in whatever cave you found them in
  • 1
    I think until on your side is everything ok an d the data can be used easyli and everything is by that methods standards he shouldnt complain he just isnt enough flexible or not that good lol
  • 1
    You can tell that he was just being defensively sarcastic because his guys didn't make it, and now he has to take ownership of this task he did not create. I get it, but that's not my fault either so wtf.
  • 2
    Just use task scheduler to have it run regularly.

    Making a service is not that hard but not something I would recommend unless you have some experience with .NET.

    Biggest problem with a service is that error handling is much more important since the program must never enter a state where it stops working.

    With a console running if scheduler you can always just bomb out and have scheduler rerun.

    Also, a service runs the risk of leaking memory and occupying resources even when not actively running.

    Ms runs hundreds of small tasks through scheduler them self :)
  • 0
    @Voxera in my case, the console app writes to SQL Server staging tables that get picked up via an SSIS job that runs every minute to truncate and refresh final tables, which in turn are used in our dashboard tool. Takes about 5 seconds to execute.
Add Comment