When you say the compensation was very close to the current market rate, I assume you mean the market rate in Poland, correct? No fancy Silicon Valley salaries for devs in Poland, that is.
Exactly, that is my personal feeling as well. I'd rather prefer to spend the extra time understanding the solution instead of just copy-pasting and adapting the first Stack Overflow answer.
In fact, one of the most striking things I encountered in Github issues, Stack Overflow, etc... is the amount of people who simply try something, works for them and they share it like some sacred solution, but when asked why that works, they shrug and cannot provide an answer. And there is a sea of validated answers just like that in those platforms.
My fear is that we are slowly rolling down a hill in which IT ultimately becomes less of an empirical industry and everything comes down to trying until it works (without the proper understanding), because it is magic.
Yes, sometimes (if not most of the time) developers are in a rush and have no extra time to spend on understanding a solution, so it is much better to slam a copy-pasted code and move on. Still, this should not be the way to go...
I do feel like you, and think mankind is doomed for real in the short term. But then I enjoy a period of disconnection from news, social media, the Internet in general...and that feeling is mostly gone, while finding joy in other activities.
These are times filled with daily overflowing streams of varied information that can leave us hopeless and disillusioned. Cutting that off to some extent can help, without leading to a total disconnect.
Wow, 1.5 years of bearing such daily situations, that is something I find impressive given the anecdotes you described. I would probably not have lasted than long in such an environment.
Good for you to leave that place at last. Hope you found a much more better environment!
It would also be worth stating that frequent code changes should be applied with regards to mid/long-term maintainability, otherwise, the pile of legacy code will stack up faster, and the wall would be hit earlier.
Also, not the same people are usually working on a given piece of the codebase for a long time, but people come and go, with different knowledge and backgrounds, so if there are no common guidelines and/or practices within the team/company, it could lead to chaotic codebases regardless of the code changes' frequency.
Quite some years ago I think that symbol was used among youngsters so that if you looked at the hand making the OK symbol people would make laugh of you. Not because of some white supremacism ideology, but because of young people's stupid jokes. Politics were not involved as far as I know.
Basically, a symbol for you to look at and the other person saying "Hah, you're an idiot!".
I used external services such as Sentry[0] and NewRelic[1], which allow one to access detailed debugging and performance checks on specific errors and API endpoints.
Aside from the classic print statements and grepping log files manually.
I don't understand anything at all. It seems some dev used an OK HAND emoji in some slides during some talk, and it was misinterpreted as the White Supremacist symbol or whatever.
Someone felt attacked personally, criticized it on Twitter and now everything is going downhill...
Of all the bundle books, I only own a physical copy of "3D math primer for graphics and game development".
Having no prior experience on computer graphics before, I love the book: it is well-written, concise and explains greatly lots of computer graphics stuff.
There are more math-heavy chapters so it's not a light reading, but little by little one can learn a lot from it.
I highly recommend it as a base to learn the mathematical concepts and the terms used in the computer graphics context.