atomicity

16 ms·

31.
by atomicity 6y ago
There are definitely not too many SWEs out there. Total compensation above $300k is something that at least thousands of engineers receive. A lot of these engineers work 8 hour days. A lot of 7-3 and 10-5/6 hours being worked. They lea
32.
by atomicity 6y ago
It's really in the best interest of the interviewer to set hard time limits. If you want your developers to work reasonable hours and be productive, you better hope that they can get shit done in a reasonable amount of time. A start wo
33.
by atomicity 6y ago
The problem is that OP is dealing with work where design is the hard problem. They need to do prototyping without considering all of the faults of their programming language, all of the concurrency bugs they could make, and all of the logic
34.
by atomicity 7y ago
This seems to be a significant (and sad) trend. It's also good to note that the increase in college grads doesn't offset this trend. "Younger Americans are more likely to have attained a four-year degree than older groups. Am
35.
by atomicity 7y ago
I liked the clarity of the article and the reasoning is solid. Still, I'm not too convinced: - A key reason for splitting up a monolith into services is because collaboration becomes too costly with 100s to 1000s of developers working
36.
by atomicity 7y ago
Capturing most of your data in your commits/revisions seems to suffer from a lot of the unsolved event sourcing issues: - How do I quickly find the info that I want? How do I "query" the commit log? Often times, we want a &qu
37.
by atomicity 7y ago
Just wondering, why is TAOCP or SICP (as mentioned in a child) essential? I've always considered reading them since I hear about them all of the time but I could never really relate it to the work that I do (around distributed systems
38.
by atomicity 7y ago
This feels like the difference between someone who _needs_ mentoring and someone who does not. In other words, a senior engineer according to your definition can (mostly) "manage themselves". I do think that this is good in that i
39.
by atomicity 7y ago
Spark still depends on Hadoop for a lot: - Using Parquet files = parquet-mr which is tied to Hadoop MR https://github.com/apache/spark/tree/master/sql/core/src/mai... - Using S3 instead of
40.
by atomicity 7y ago
I like how mentioned this fact. K12 education, church, prison, and re-education through labor are all systems that hold certain people 'captive'. I've always felt arguments like "the parents can choose not to send their
41.
by atomicity 7y ago
The newly hired faculty at my school have mostly been ML/AI people. While it seems completely wrong that ML is needed to break into industry, is it true that research roles strongly favor ML right now?
42.
by atomicity 7y ago
I hope you are joking since the industry collectively knows how much employers/interviewers value algorithms-based coding interview, which doesn't correlate strongly with performance. Even if you are talking about senior positions
43.
by atomicity 7y ago
Yeah, the core reason to use Helm is for the ecosystem. The value that comes from being able to quickly set up and compose packages on https://github.com/helm/charts/ is larger than the (very) annoying YAML templa
44.
by atomicity 7y ago
| 38. Employers care about which courses they took. Dark side: Employers care about your technical interviewing ability and your GPA. Technical interviewing focuses on a subset of skills around certain algorithms and data structures. The co
45.
by atomicity 7y ago
My anecdotal experience interviewing this year is that they don't. LeetCode/Hackerrank-level algorithm questions are common. I haven't seen any TopCoder-type questions and brain teasers. According to some posts, it seems like
46.
by atomicity 7y ago
Still think that tests have a role, but there's room to improve them. While human contact is nice, it's also costly, so improving testing would still be a great way to innovate. For example, I received a great coding test from Ver
47.
by atomicity 7y ago
Personally I don't think it's worth Anki. There are so many things that you can memorize: - common standard library method - code-level design patterns (like the factory pattern) - system design patterns (like caching in Redis) -
48.
by atomicity 7y ago
Just because you learn more from failures doesn't mean that you will learn more in aggregate over time with more failures. If you fail too much, your brain will tell you that it's better to quit and spend your attention/time
49.
by atomicity 7y ago
By using a remote machine, you gain in upfront cost but you lose dev time due to poor tooling. It's possible to use X11, SSH, SSHFS, or Kubernetes but it never truly replaces the flexibility of developing locally with an IDE. Kubernete
50.
by atomicity 7y ago
Yeah, cloud providers do advertise DBaaS as 'simple' but there's a reason they don't advertise anything on parameter tuning or say that they replace DBAs [1]. You pay them so that they give you a self-managed database, b
51.
by atomicity 7y ago
Definitely interesting how performance between different cloud DB services is so untransparent, similar to object storage [1]. Well, it wouldn't matter much with CSP lockin. In addition to factors you can't control, maybe Digital
52.
by atomicity 7y ago
This looks awesome! This covers all of my complaints and even has some core material that I don't have but probably should have 'cached' in the back of my mind. Props to Pavlo and the course TAs for the great work! A lot of D
53.
by atomicity 7y ago
Yeah, I also agree that databases are a lot more about database internals (or DBMSs). Not sure if I would agree with splitting databases into separate courses. I think it's a lot more useful to learn about general concepts like concurr
54.
Ask HN: Ideas For
1 points by atomicity 7y ago|0 comments
55.
by atomicity 7y ago
The best reasoning I can come with is: Allocation: (1) stock market rebalances share prices somewhat well, which means that (2) companies who produce more growth are valued more highly, which means that (3) those companies, which frequently