__exit__'s comments

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?

First thing in my mind when reading "sednoid" was "mathematics!".

As for the rest of the terms, they are new to me due to my non-familiarity with cosmology in general.

Thank you. So many new terms there: sednoids, Oort clouds...

Glad it worked out in the end for you!

Thank you for the response!

I am currently reading the "Programming Rust" book. My problem is not on the concepts themselves but on applying them: I am finding it quite hard to think of some small project to apply the learning. In addition to this, my thinking is that systems programming requires a different approach to coding/architecture of applications (because it lies closer to the OS layer than other kinds of apps such as web apps).

This is quite the answer. Newer generations should realize such things as respect, self-discipline and responsability.

In the meantime, enjoy life the way one prefers.

There is this book called CSS The Missing Manual, by David McFarland.

Although I did not finish it, I started it with regards to learn CSS properly (like you) and started to grasp some basic concepts (could not finish it though, due to procastrination). Honestly, I think the books delivers , maybe you could use it!

I remember Path back in college. It was not that popular but its mobile app was beautiful, top-notch in terms of UI design and animations back then.

Sadly it did not take off, which on the other hand is comprehensible, having other options such as Facebook and Instagram where most of the friends and connections are.

Knowing a stack deep is rather difficult when one attempts to also learn and keep up-to-date with the newest technologies. Or were you referring more to system/protocol stacks instead of programming languages/frameworks?

When you mention technical books, do you have in mind books on programming languages/frameworks or more focused on general concepts/skills useful for the daily work?

I cannot stress enough how true this is when talking about types of engineers.

However, both types are not mutually exclusive. There may exist some overlap between them, but of course, an engineer may feel more comfortable being one type more than the other.