![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
4·
9 months agoBut now you know for next time! Everything is a mystery, until you figure it out.
But now you know for next time! Everything is a mystery, until you figure it out.
Same here, played a bit of DS2, but never really got into it. Started on DS3, but got tired of that pretty quick as well. But when Elden Ring came out, I got really hooked on the games. I finished Elden Ring, then I played through DS 1, 2 and 3. And then a few more playthroughs of Elden Ring with different builds. I’ve started a bit on Sekiro, but jumped over to Lies of P when it came out. The plan is to play the new Lords of the Fallen, when I’m finished with Lies of P. It’s really satisfying to beat a boss after a few hours of learning the patterns.
Cool, hope it continues to grow!
I guess this entirely depends on what country you’re from. I’m a developer, and I constantly have to deal with ignorant bosses. They push me to write code faster, sacrificing proper planning, architecture, and testing. Then I’ll be the one sitting up all night fixing a broken release, because my code doesn’t work.
As the professional in this scenario (the one who knows how to develop software), it’s my responsibility to make sure it’s done right. My boss isn’t supposed to know how to do it, so it’s my job to let him know.
Of course, you still have to have your bosses permission to do it, so I totally agree with OP putting pressure on the boss. It’s important that the boss knows what’s at stake, and it’s OP responsibility to make sure he does. But at the same time, it’s important for OP to know why the boss doesn’t want to upgrade, he might have a good reason, or at least it would be easier to argue against.
Again, it probably depends on the country. I work in a country with high job security, but it might be different in other countries (not the responsibility, but the danger of doing your job properly).