This time I won't be shamed into doing it again. I don't have the time or motivation.
edit: forgot to mention explicitly, it's not Firefox, it's me. I'm not strong enough.
171 karma · joined May 3, 2016
This time I won't be shamed into doing it again. I don't have the time or motivation.
edit: forgot to mention explicitly, it's not Firefox, it's me. I'm not strong enough.
Seems to me both are for similar use cases. I'm using mine as firewall appliances for example.
The material from OP won't prepare you for systems design interview (witch is also your point?). Only experience will, so we measure experience and leadership.
Juniors can apply to systems design openings and will be interviewed, but they end up as generic SWEs if hired. If one thinks one can work on distributed systems coming out of university you will have a hard time interviewing or not like it.
I understand that some candidates don't like it, because they are obviously good at something and want to be asked questions in that field. But ... I already know you are good at it because you said it on the CV, so i'm not wasting time with that (yes, if you are a good liar it takes us longer to find out).
So your example, working as intended?
I guess i understand the sentiment, but we shouldn't shame people away from discourse. Everyone should be allowed to be wrong, if comments are made in good faith.
I imagine that that's the exact reason why for example advertisers will opt for bluesky over mastodon immediately, under the assumption that the reach would be the same.
Large contracts are locked behind FedRAMP compliance, DoD ILx, and so on, and I happen to know that all large cloud providers listen very closely to customers in this space.
Your harsh criticism is valid under the assumption that GCP is an unsuccessful consumer product. I think it is only partially so and features are mostly driven by larger b2b and governments, where it is successful (in the sense that it delivers most features customers care about).
JSON-RPC makes sense if one only considers the abstract case with a single client and a single server box and minimal networking. Technically it's a viable solution but just not practical.
HTTP on the other hand is nice as it separates the business logic stuff like the RPC parameters from stuff that's interesting to the transport-network-thingies that sit between you and the data on a server, like load balancers, DoS protection, authz, rate limiters, ... etc.
If you look at the problem more holistically (say "run a reliable service customers want to use") then that metric is just one of many, and more often than not counterproductive vs some other metrics like maintainability and resilience for instance. IME frameworks reflect that and only let you write code fast, or get the hello-world-demo out fast, but neglect the later stages.
I don't know if the conclusion is no framework is better overall, but the frameworks i worked with at least showed mixed results overall.
I think this depends on ideology a lot. In europe the sentiment is to improve the life and livelihood of the average person on average, and not that of a few CEOs, and labour laws reflect that.
The cynic inside me tells me this results in universal health care, better infrastructure, less divide between poor and rich and thus less crime on average, ... in europe. In the US you have super rich CEOs fueling policies to make the rich richer. Maybe my reasoning here is not true, but I take these quality of life improvements over all the tech unicorns any time.
I really want to like it, it just doesn't click for me. There is just no practical incentive at the moment to switch (for me), just the more idealistic ones about privacy and so on.
I personally don't have the constraint that i need to give everything to my job and it needs to give back, so i agree with the GP and don't see it as dystopian, just one of the many ways of living.
Others legitimately do have this constraint and probably have to simplify elsewhere (not have kids is something I've seen a lot).
This system is doomed long-term if it only works because of information imbalance, since ways will be found around that (levels.fyi, random walk across employers, ...).
Also, one aspect of professionalism is also to be thankful for the feedback rather than trying to interpret it as attacks.
GP's feedback is direct but quite right imo. I trust the author had only best intentions in mind but "Knocking something out in half an hour" and sharing, but good privacy and security engineering requires probably much more time. Quite frankly, the wording of the article can be insulting even for folks that are working on that problem professionally for several years.
Were it presented differently, it would get different feedback I'm sure. More like "hey HN, i made the first three steps what would be next?" -- i.e. efforts towards trying to understand the problem better.
As a single datapoint: for senior positions i will look at all side projects presented in a CV after the first phone screen. However, it can only serve as a signal amplifier for traits established in the CV by experience or education. So if a candidate does not have side projects, we try to get a better signal in a different way. That said, i have never seen someone getting hired because of their side projects (or someone not hired because of the lack of them)--but i have seen us pass on candidates that accidentally provided negative signal with their side projects.
For junior positions having or not having side projects can be a deal maker or breaker.
It's a bit silly though to call out the author for not using the right linux laptop or being too hung up on their workflow. It's not unfair towards linux, the conversion of a macos power user was never meant to be!
There are racists, and fascists, neo-nazis and old-nazis. They do exist, it's just that they don't pose that widespread of a problem in every day life, like it does in other western countries.
I'd say gender (in)equality is something you will encounter much more often in every day life over there.