suncherta

The way I come to look on such offers (monthly unlimited subscriptions) is not the net price itself, and not future supposed returns to it (who knows what they be, and they for sure will depend on many other things), but how many hours a week I am willing to spend on that service.

If you can and willing dedicate on average 2 hours a day (a big commitment but I think I was able to hold it for several month with them) the cost of mastering, say, Linear Algebra will be ~4 less then if you subscribe and will be spending ~30 minutes a day.

Yes, pretty much all of it.

For sure Bezos handled this badly. But the problem in my opinion is not his management skills or even his civic valor, but apparent fear of business and public people of retributions for supporting a wrong candidate.

I understand the reaction of people canceling their subscription, but I think it is a mistaken one.

To me it is looks a lot like punishing the victim.

The primary victim here is WP whose employees didn't do anything wrong in this situation and didn't have much of the choice.

Even Bezos, at worst, is the person who didn't manage to stand under pressure put on him.

I wonder where usage of Space Repetition software (like Anki) falls according to this article? Is this a valid retrieval practice?

I am happy Math Academy customer. Agree with most what you wrote above. Except for the pricing estimate for the private tutor and related 26x cheaper comparison. People generally don't hire private tutors to have lessons every workday of the week. No I think it would make sense for do so even leaving out financial cost. It is more like once a week session with take away homework (maybe twice a week for a quite intense level). This brings cost comparison down to the 5x time (10x for twice a week). Still quite impressive.

As others have already mentioned this is used in a lot (most?) of databases. It is called "slotted-page". Searching for it gives good discussions/explanations of it.

Quite a shallow article it seems to me, almost like parody on what could be a decent analysis of the impact of AI on the politics and elections.

Does it rise less or the same in the districts that were not de-funded?

Yes, that's the one. Thank you.

I am very happy to see more content like this (attempting to teach how to create a real system) becoming available. Few month ago there was a launch announcement of YC backed startup that sell you walk-through labs guiding you to build Redis, Docker, Git and others. (Can't find link to it now.)

What is still missing, in my opinion, and is badly needed, is content or even an idea on how to teach taking such projects from toy prototype version to the production quality one.

Excellent advice and explanation. It is rightly on top.

The only thing I would take issue with is the first paragraph where you try to calm down the OP:

> Okay, first things first - take a breath. This is not that big a deal. If you're at a company that's big enough to have a PIP process, then there are two possibilities: (1) it's well-established enough to know that junior engineers aren't productive for about a year after hiring, or (2) it's completely incompetent. If it's (1), even if you actually are way below average, you still have some runway left. If it's (2), they almost certainly have enough of a reputation that you can "fail" at your current job without it really harming your long-term career path.

This way things are at least in US, is next to impossible to harm your long-term career path by failing at one job. One needs to be at least prosecuted to harm their long-term career.

OP, if tomorrow you'll get fired on the spot, in a year time frame your most-likely will find yourself better of than you are now (and, frankly, likely to be better off if you stay at your present company).

Another Senior SDE/tech lead here with 20+ years of experience including FAANG and some top Wall Street companies.

There is a lot of good advice given to you. I have read about a dozen top posts (at the moment), and haven’t seen something major I would like to correct. I am not going to give you full answer, repeating most of what already being said. Instead, bellow are few actionable items I would like to emphasize.

1. Prepare to leave the ship. Start looking at codding/algo problems, preparing answers to behavioral questions, probing your network, etc. Also, if possible, look inside your company, are there teams that you will be better fit for you? Do not wait for PIP, as in a lot of companies you can’t transfer while you are in PIP.

It’s not you, but life is too short to be on the team that doesn’t nurture you. More so, as starting junior getting right exposure to good engineering culture at the beginning is critical to your professional growth. I can’t tell you how many times I got to interact with basically smart folks that could have been a good engineers but who were damaged by early exposure to toxic software development environment.

On top of this, as of now, you are going to be interviewed as junior or even out of college, with lower expectations. A year or 2 down the road you will find that expectations from people who interview you will start to raise significantly. If you don’t grow now to meet them, you are putting yourself in a bad spot latter.

You might not need to leave your team, but being ready to do this will give you comfort, and looks like you need it.

2. Find good mentor. And another one, and another. Look both in inside company and outside. Be prepared to iterate through a few, and learn to be a good mentee. I saw at least one offer here, try to take it. Also, ask proactively here. If you leave me your throughway email in comment, I may be able to help you too (mostly depending on our timezones).

3. Start asking a lot of questions. It’s bullshit that you have been at the team too long to do this. It doesn’t work like this.

At the very least, you can think that if your standing with your team is damaged starting asking basic questions will not damage it significantly more (you might find that it actually improves it, but no guaranty).

Also, think about it as a skill you are developing: the skill to ask questions easily and early. You will need it throughout your career.

Few tips on asking questions productevly:

1. If you don’t know or understand something it is a legit question. If context is in person conversation or meeting it is OK to ask it right away.

2. If you need to find somebody to ask the question or ask for the help. You will end up with having 1 or 2 persons you are most comfortable asking questions, and as result asking them a lot of them. This is anti-pattern. Do not overload just one favorite coworker, go out of your comfort zone and reach out to other people.

Make for yourself a small SOP (Standard Operational Procedure) to ask questions, and timebox, say, 10-15 minutes to try to answer question yourself before reaching out for help: 3 Google searches using different queries, looks through product documentation, search through internal system(s), maybe post on the question board (different questions land themselves to different research steps). Also amount of preliminary naturally research depends on the urgency.

Communicating to your coworker that you did your legwork before asking for their time is a good thing and will save you few embracing incidents when the answer was right in front of you (happens to me far too often and is not that big deal).

After getting help from coworker (and naturally thanking him), ask how you could have found it by yourself. This will teach you to be better at searching information in the future, and in lot of cases it will turn out that there was no reasonable way to do so.

Also ask your coworkers what their preferable communication channel is to be asked for the help in the future and do your best to use it.

If person you asked doesn’t know the answer, make note to ping them when you learn it and ask them if they are interested in it.

Document your finds at least for yourself (it will take time to develop reasonable note taking system, aim it to be adequate, not perfect). As a stretch goal see if you can also document it for others, like updating internal wiki, etc.

What would be good resources for this?

What are the methods available today to determine if received vaccine are legit?

From the text of the article I've got the impression that instructions itself received with different batches (and by different parties) differ. But how country officials can check that vaccine they received is the one that they bought, short of starting using it and tracking the result.