__exit__

Didn't notice that post, thank you!

Having the same issue now after coming back to an iPhone after several years. Last time I used an iPhone there was Swiftkey, which was amazing.

Now, that seems to be gone from the App Store (not available in my country at least) and I am stuck with the default which is quite crappy, honestly.

Also, keys are too small for my fingers, so frustration keeps adding up.

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.

This is such a great advice, thank you for illustrating it with such an impactful and personal background story.

Autocorrector issues + fast fingers to click on submit without double checking. Sorry for that.

Whoever fixed the title, thank you :D

Thank you!

Do you have any recommendations on classic books about algorithms and data structures? I would be interested in checking some of them.

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.