This is so wrong, I cannot even take seriously the rest of the points.
360 karma · joined September 15, 2016
This is so wrong, I cannot even take seriously the rest of the points.
It is a review of the most fundamental tools and strategies in Red Hat flavored Linux distros. Things like troubleshooting the entire stack would be far too advanced and specific.
@strzibny, it would be great if you can put some curated links or references at the end of the book so the reader know where to go if they want to go deeper in that particular topic. It would really improve the value that some of us get from the book.
I always though it was quite fun detail.
Dislike: A billion products, most of them half-baked, terrible DX, terrible documentation, pricing all over the place. Examples: regular Sagemaker is much worse than a normal VM, Sagemaker Studio is so so. CloudFormation is not great and only works with AWS. Smaller products are even worse.
I try to avoid as much as I can dealing directly with AWS APIs (specially their web) and focus on third party tools like Terraform, Ansible, etc. It makes it tolerable.
- I want something lightweight and not bother to deal with compiling/preprocessing (like Milligram).
- I want a MVP without classes (like Picnic.css)
Otherwise I pay a premium theme or create one myself.
https://medium.com/@jacobp100/tree-shaking-bootstrap-95d6301...
University education in UK (sans Scotland) has gone from zero to GDP 9k a year in fees, the average debt per student is GDP 35k. I know that this quantity and the associated conditions for Americans, or London IT people, sounds like a joke. But AFAIK the average pre-tax graduate job salaries in about GDP 24k.
We tune up a little bit the difficulty. The point is to start a conversation and see what the candidate knows about, ¿does he knows about time complexity?¿differences between passing by reference/value?. Afterwards we talk about the technology that they use, what they like, and what they will like to use in the future. Just to see if they read about their field and are able to talk without saying something egregious.
And if they do fine we bit the bullet and hire them.
> nobody owes them an employee either
Now that I am "in the other side", I can see a lot of things that will definitively would improve the problem at micro/team level, like posting salary or increasing the WFH days. But ¿would they improve at macro/company level? The things is, companies, including tech companies, from small startups to big corps, usually have much more problems than the quality or quantity of their software.
(signed, someone that has been rejected, and will be rejected, to more interviews that he has passed)
It is still a very useful test.
An example is Pinterest, Google can drop or deprioritize their properties, like they do with other actors. But for some reason they do not. Maybe they are scared of litigation.
Other would like, or even try. But Amazon management, an enormous American corporations, are determined to not allow to do so. Amazon warehouse workers are, generally, not a particularly wealthy or powerful segment of the society.
They have an excellent and unique product and I would love to pour them money (between me and my employer we pay about EUR 1000 /year to Intellij, and this is only one provider). But for some reason I do not feel comfortable between the immense power imbalance between them and myself. It makes me uneasy to invest in the ecosystem.
I wonder how many clients they have their CAP users in the academic world.
I believe working in pandas/sklearn/jupyter ecosystem is much slower (>50%) if you are doing EDA and statistical modelling (ML) than tidyverse/tidymodels/rstudio. The exception is deep learning and adjacent fields (like computer vision).
Of course Python is better at everything else, so adding an extra languages might or might be worth the hassle.
I agree, but I think this actually depends on the media. I do buy my technical books ($50-$150/a piece), but I want to take a look at them first before purchasing.
Or with a cash flow for a permanent position. Tech workers are used to be in companies with healthy gross margins and revenue where they make sense (theoretically at least). But even it tech I would not be surprised if there are teams of DS/SWE people in Uber or Doordash helping their companies to lose money faster.
Somewhere in the same company might be someone making the same as you with a couple of SQL/Qlik courses in their well groomed head and a handful of ironed shirts in their closet. But we will look down at them because dressing well is for sheep and SQL is like, 100 years old.