The satisfaction/get rekt feeling when I do this.

When a client sends an email asking us to do something "ASAP" and end it with "thanks in advance!" while it's something that we have user guides for.

"Dear {client.name},

I'd like to point you to a tutorial we have about this on our online help desk: {tutorial.link}.

Have a great day!"

Ha, rekt!

Programmers nowadays have to...
… write 100%-covering unit tests;
… set up continuous integration, linters, hinters, style checkers, …;
… follow style guides for every language;
… meet impossible deadlines;
… meet impossible management/customer/end user expectations;
… read through terrible code others made;
… read through terrible documentation others made;
… make terrible documentation themselves;
… fight with the IDE;
… fight with the build tools;
… deal with unreproducible crash reports coming in from everywhere;
… debug code written at 2am (by themselves AND others);
…
…
…
… KNOW HOW TO PROGRAM.

Writing CMS user guides for a site I'm just about to deploy so boring 😭😭😭

Old old organization makes me feel like I'm stuck in my career. I'm hanging out with boomer programmers when I'm not even 30.

I wouldn't call myself an exceptional programmer. But the way the organization does it's software development makes me cringe sometimes.

1. They use a ready made solution for the main system, which was coded in PL/SQL. The system isn't mobile friendly, looks like crap and cannot be updated via vendor (that you need to pay for anyway) because of so many code customizations being done to it over the years. The only way to update it is to code it yourself, making the paid solutions useless
2. Adding CloudFlare in the middle of everything without knowing how to use it. Resulting in some countries/networks not being able to access systems that are otherwise fine
3. When devs are asked to separate frontend and backend for in house systems, they have no clue about what are those and why should we do it (most are used to PHP spaghetti where everything is in php&html)
4. Too dependent on RDBMS that slows down development time due to having to design ERD and relationships that are often changed when users ask for process revisions anyway
5. Users directly contact programmers, including their personal whatsapp to ask for help/report errors that aren't even errors. They didn't read user guides
6. I have to become programmer-sysadm-helpdesk-product owner kind of thing. And blamed directly when theres one thing wrong (excuse me for getting one thing wrong, I have to do 4 kind of works at one time)
7. Overtime is sort of expected. It is in the culture

If you asked me if these were normal 4 years ago I would say no. But I'm so used to it to the point where this becomes kinda normal. Jack of all trades, master of none, just a young programmer acting like I was born in the era of PASCAL and COBOL

Enterprise software vendor with scarce, outdated and useless documentation. Claimed 'we are working on it' - they weren't. I had to write 75 page admin and user guides.

I am quite worried about the approach users have towards technology...

I am starting now to work to my bachelor thesis research in algorithm, so I'm still very young.
But when I think about which mental process guides people when they use or try to fix their pcs is very worrying...
I mean I am no mechanical engineer but I don't pretend to know perfectly how an engine works. But I try anyway to understand it the best as I can...

Instead I see users that don't try to know at all our products... People (and not only elderly) which think that Facebook and Internet is the same thing, people that think that you can find anything one the net, while I found myself stuck many times in the middle of a research for something...

I had a course in human computer interaction... And I see the point of simplifying the user experience... But I fear that it will be soon to much :s

I hate the android development website. I'm trying to learn android development since two weeks and I didn't understand anything even though I was following everything the "Training" section said... Only yesterday I discovered that the "API Guides" section provides all the informations I need. Come on, why the hell is this se second section on the website??
This seems to be a user experience error to me.
Am I the only one?