Wanna hear a story? The consultancy firm I work for has been hired to work on a WPF project for a big Fashion Industry giant.

We are talking of their most important project yet, the ones the "buyers" use to order them their products globally, for each of the retail stores this Fashion giant has around the world. Do you want to know what I found? Wel, come my sweet summer child.

DB: not even a single foreign key. Impossibile to understand without any priopr working experience on the application. Six "quantity" tables to keep aligned with values that will dictate the quantities to be sent to production (we are talking SKUs here: shoes, bags..)

BE: autogenerated controllers using T4 templates. Inputs directly serialized in headers. Async logging (i.e. await Logger.Error(ex)). Entities returned as response to the front end, no DTOs whatsoever.

WPF: riddled with code behind and third party components (dev express) and Business Logic that should belong to the Business Layer. No real api client, just a highly customized "Rest Helper". No error reporting or dealing with exceptions. Multiple endpoints call to get data that would be combined into one single model which happens to be the one needed by the UI. No save function: a timer checks the components for changes and autosaves them every x seconds. Saving for the most critical part occurring when switching cells or rows, often resulting in race conditions at DB level.

What do you think of this piece of shit?

I've got an enquiry for all you devranters. Is anybody here using WPF and XAML in their everyday life at work? If so, is it for legacy or new projects?

I'm interested.

I used to blast throught everything accademic in a really short time span. I used to push hard on the gas pedal since my college years, up to my bacheler degree. I was always on schedule with every exam, even graduated top of my class and first amongst my colleagues. But then, I felt the urge to change university, I moved out of my parent's home, in a far away city, and everything simply collapsed. All of the sudden, not only was I struggling with my exams, but, most importantly, I started struggling with telling the truth about it. I constantly felt in debt of my parent's efforts to put me through university, to have given me a chance. This caused a strange feeling in me, it was similar to a weird form of depression, I was unable to...act. To do stuff. To even wanting to do it. I started procrastinating everything. I lived at my parent's expenses in this far away town but all I could do was playing videogames. I somehow managed to get to the point that I only had three exams left plus my thesis, but I did this by avoiding all the real hard exams, somehow cheating myself. I was already two years behind schedule at this point, and willing to quit. I was desperate, I cried a lot, thought about running away fron everything as I fear the disappointment I would have caused by simply telling the whole story.

Thankfully I met my girlfriend who helped me realize all I needed to do was move back to my former university and take it step by step from there onwards. I almost didn't make it...again. But I was able to pull throught, I worked during the day, wrote my master thesis early in the morning and late in the evenings. I gave it all. And I made it.

I graduated last year and got a job in the industry. I don't feel as useless anymore. I still fear and dread what the burnout made me feel. How it almost destroyed all confidence I had in myself.

Tldr; I burned out right after getting my bachelor degree. And I stayed like that for years, up to the point that I ended up being years behind schedule. I was able to recover thanks to my gf but still fear and dread those feelings I had when I burned out.

Today I'll be working in Prada. I'm scared as hell.

The one and only "Linux beer" I've ever seen.

Idiot mode: on

It's bad when you realize you are the most idotic person you know. I just bought a wifi card replacement for my laptop only to find out that one of the screws on its back was completely unscrewable. I foolishly decided to force my way through by forcing the plastic. I tought I got away with it as I only damaged a plastic support tighten to the laptop base but now, my laptop screen isn't showing anything.

When I first booted it up after this, it was working, but it started showing troubling signs shortly after. Now, all I can get out of it is a completely black screen, no backlight at all.

What should I do? 😥

I'm in need of advice. I reckon this is no stack overflow but that's probably for the best as I wouldn't feel as comfortable posting there as I am doing it here. So, back to the question: I'm currently working with legacy code, written in .NET 2.0. This code is responsible for calling upon PEC services in order to finally create personal smart cards. I was tasked with the job of creating a repository system that would allow the program to call on the old legacy services or the new ones without any distinction. We are talking about SOAP services in both cases. The issues is: the new service definition is comprised of soap policies. This wouldn't be a problem per se, with more modern version of the framework, but with .NET 2.0? Yes, it is. It doesn't support policies and signing the body with a certificate right out of the box. How can I manage this? I feel like the only way would be letting the proxy class do its thing up until the very last moment: intercept the SOAP request before its sent and modify it according to the specifications. But I reckon this is very bad practice. Is there any other way out of this?

Thanks for anyone that would like to help. 🙂

I've a question. Has anyone in here ever be forced to use something as remotely frustrating as SQL Server Reporting Services (ssrs)? I swear it is one of the most convoluted piece of shit ever.