__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.

Really great set of resources! Bookmarked! Also a great companion to rewatch the series!

BTW, does anynone know where I could buy the complete series on bluray or dvd?

I loved watching the show on TV at its time, but cannot find all the seasons to buy and rewatch.

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.

[0]: https://sentry.io

[1]: https://newrelic.com/

What's the source of that document?

I found a page[0] with more info and link references to multiple sources that seems to explain everything in detail.

[0]: https://dev.to/aryanjnyc/ken-wheeler-and-dan-abramov-deactiv...

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...

The Uber Engineering Blog[0] is the first thing that that comes to my mind.

It has posts describing optimizations and approaches they took in certain subsystems.

[0] https://eng.uber.com/

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.

I personally prefer Django because everything is more explicit than in Rails.

Explicit imports, no magic file locations or configurations...

Amazing! Thank you for these links!

Nice to see this series continued! I wish there were more, potentially non-discontinued series or books on how to build actual projects with Rust from scratch.

Thanks to the author for this piece, it was a nice and inspiring reading.

I cannot help but feel related to the author himself. My career, short in tech terms (2+ years at current job, similar durarion at previous job) has reached a stagnant phase, where motivation and professional growth almost do not exist.

As a consequence I'm thinking of switching jobs, but have no idea where should I aim for, for what kind of role and industry I would like to work for...Right now I'm lost regarding jobs lookup.

Maybe I should take a sabbatical period to think things over, but it's quite a leap forward, mostly economically.

Holy molly! This sounds similar to what I thought a couple of days ago: China is the major electronics supplier to most technological companies, what if China added some sort of sniffing or malware on the chips to spy on their customers?

Ask questions, no matter how stupid they may be. REALLY. Ask any doubts and questions you may have regarding coding practices, implementation details, technical workarounds, etc...

Even if the questions sound silly, which is what terrifies the most, just ask. At my first job, I was too afraid of asking my teammates unless I came up with some smart-sounding question.

Fast-forward a couple of years until now: I have a teammate who is quite less experienced, and revealed me he does not want to ask questions because he thinks it's a waste of time for the other person and/or he feels silly to the whole team.

I attempt to mentor him and teach him to ask questions, no matter how dumb may be. We've always been there.

This leads me to another aspect: have empathy towards your colleagues.

Did you hear from that team lately in regards of how they're doing? Do they still put in 60+ hours a week or did they switch to a more balanced work life?

The message may be heard, but putting it into practice is the more difficult task in my opinion. Changing a whole company's (either big or small) policy regarding meetings/working hours/etc... is quite a challenge

Still, the new book's cover may attract an audience that is not familiar with DHH/Jason/Basecamp's opinions on work/life balance.

I read Rework and Remote (previous Jason/DHH books) an although full of common-sense ideas that I applauded, they were quite similar in terms of content.

This new book seems to be kind of a mix of those previous books.

Losing a few months once in a while may be bearable, and even worthwhile as a positive experience towards a more selective criteria regarding future workplaces.

However, I would argue that depending on one's need and situation, time is gold, and jumping from one zombie startup to another continuously may not be feasible.

Agreed. Until you do not enter a startup, it's hard to know how it actually works.

During interviews and preliminary hiring-talks they may sell the pitch as if everything were wonderful, but potentially, the unfortunate reality could be that things are not that nice.

I acquired Pbrt in order to learn the basics of computer graphics rendering in a practical way. However, I struggle even with the most basic things (math mostly).

Do you happen to know of any resource that provides a good mathematical foundation directed at computer graphics?