Me: Hey sys admin guys (group chat), our servers are in a complete different ip range. (192.168.x.x)
Sys admin: acknowledged
Sys admin: *installs tools on our server*
Sys admin: hey dev, please open up your ports
Me: why?
Sys admin: our tools can't talk from your server
Me: ok, what ip range
Sys admin: (10.0.x.x)
Me: 😑😑😑

I've became a better dev/sysadm since I've got a girlfriend. She has no freaking clue what I am doing when I'm working or sitting in front of my laptop. But she's often interested in the things i'm talking or ranting about when somthing doesn't work out like i've planned or some stupid problem occurs that I'm not able to fix. I am so glad i've got her. :)

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