> flagged it as “no” because they had too many position changes
This is wrong and misleading in many ways, you should ask people why they left, you should give a chance to those who have good skillset, not based on number of jobs they had. I know a lot of people who worked on contracts, so they had to change employers frequently, and I know a lot of people who were looking for a place, as juniors, to learn from good mentors. It is really hard to find mentors in Startups, and not everybody can make it to big companies. If companies don't invest on their employees, they leave.
I should clarify that this is not the only reason. It’s one of several. And yes, we did discuss the reasons and it was always something more interesting.
But as best I could tell, if we did hire them, we had 12 months tops. Remember, I only have the past record to go on and hiring is the most important and hardest decision to make.
I think the author didn't cover a lot of fundamental research behind NoSQL. If you are reading this comment, and want to dive into SQL/NoSQL DB fundamentals, I highly recommend checking CMU DB (Andy Pavlo) lectures [1] [2].
One book that helped me understand these challenges was "Hard things about hard things". I recommend/gift the book to any (engineer) friend who is burning to start his own business. It's a different game. Even Sr. Engineer is a different game than coding, we spend some time on System design, mentoring, presenting technical outcomes of our work/PoCs, writing new product requirements, .. etc. I think these tasks require other skillsets as well.
Disinformation is a problem for all social media platforms, for all languages, FB is one of those platforms. I have the feeling that media focuses more on FB & English, but we should rather focus on the problem as whole and its harm for all communities around the globe.
I work in a large organization, in an industry that is naturally slow. The work (in the industry) is slow because it's critical to deliver stable and reliable solution because large part of population and economy rely on this industry SW/HW. I have heard a lot of complains on how the process is slow, but in many cases, building on top of existing work takes a long time. It takes long time to understand legacy work, to go through older studies and projects, and to find spots to add contributions. Not all of us work on green field projects, but many of us maintain code/work that doesn't look "cool".
Additionally, most things that trend in that way are going to be lowest common denominator crap, or if it's from one of the better channels, broadly accessible stuff that would be a better use of the listener's time as a listicle instead of a 15 minute video.
I wish the recommendations went for the deep cuts instead of the pablum.
Is there any reference to delve in the details of GIL, multithreading, multiprocessing, high performance computing on top of Python eco-system?. There are some interesting projects such nimba, Dask, etc, but the resources are a bit scattered.
This is wrong and misleading in many ways, you should ask people why they left, you should give a chance to those who have good skillset, not based on number of jobs they had. I know a lot of people who worked on contracts, so they had to change employers frequently, and I know a lot of people who were looking for a place, as juniors, to learn from good mentors. It is really hard to find mentors in Startups, and not everybody can make it to big companies. If companies don't invest on their employees, they leave.