Hacker News new | past | comments | ask | show | jobs | submit | aprdm's comments login

Why do you feel like you need to keep it up ? The foundation of computing hasn't really changed too much in the last 20 years. Master the foundations and maybe read this site once a week ?

I love this. I will bookmark / see what I can do once it stops raining everyday in Vancouver


Can you share a bit more about Bezos email ?


Ancient Internet lore at this point :)

Bezos used to (supposedly, didn't work for him) have the habit to forward emails to reports (direct and further down), with just an added comment of "!" or "?"

"!" was "Do something about this" "?" was "Can you please explain WTH?"

https://www.reddit.com/r/MBA/comments/kwryld/on_product_mana... is an example story of that. There are plenty more.

The exclamation mark version seems apocryphal, though.


Not true in my experience being on both sides of the equation


There are thousands of CVs per opening in some companies, how do you expect people who barely have time to read the CVs to also give individual feedback ?


I can’t tell if this question is just a statement about the impossibility of the situation or a genuine ask.

We should expect more professional courtesy and human decency for our peers than what typical application processes provide today. It help make candidates identify weaknesses and collectively improve our field.

Perhaps creativity or persistence will help us solve this difficult problem but we won’t get there if we write it off as a fact of life.


Sadly, if incentives aren't aligned, I'm of the opinion not much will change.

Let's suppose there were a no liability clause for employers when giving feedback, they could say we didn't hire you because we didn't like you or because you were too short, or whatever they wanted. In that case, companies could tell the truth and would have nothing to lose. However, the question would remain - what do they have to gain? To this end, if an applicant could purchase a feedback review, then companies would have something to gain as well.

I'm not saying we should do any of this, I'm just trying to sketch a scenario in which some systematic rules exist which might get both parties to be more aligned on "giving true detailed feedback".


>> It help make candidates identify weaknesses and collectively improve our field.

Actually, and this will sound wrong, but it won't.

Let's say the worker pool is 1000 candidates. If I give them sll advice, and they take it, I still have 1000 candidates to choose from. It's just harder since they're all better.

On the other hand the resume that contains spelling errors is easy to just discard (low attention to detail.) I don't want someone else to gave told them, I'm trying to find people who have attention to detail without being told.

Failing that I'm looking for people with some initiative. Perhaps someone who has recruited friends, family or even a service to run mock interviews and provide feedback.

Of course resumes are terrible starting points for job applications. You send out thousands, I get thousands. How might you take that knowledge to better stand out from the crowd?

Here's my answer to the original poster; we don't give feedback because of the legal and incentive reasons others have highlighted.

Recognizing this fact, what then is your next step? Instead of being a passive participant in the process, what might you do to stand out from the crowd? What might you do differently to the herd?


Things I have done to stand out from the crowd seem weird because I have to guess as to who I should even start with, often through tools such as LinkedIn Pro or finding contact information through GitHub repos. Many of the application processes are similar and use the same provider to serve them (Workday, etc). When an org does acknowledge your submission, it is often from noreply@org.tld, and there is no HR contact information publicly listed.

If you are a hiring manager, what are some things you have seen that you though took some initiative, but also couldn't be seen as crummy?


send them a personal email or linkedin msg


Why is it brute force and why is it bad ?


99.9% of the companies in the world will never need more than 1 beefy box running postgres with a replica for a manual failover and/or reads.


Availability is trickier than scalability. An async replica can lose a few recent writes during a failover, and a synchronous replica is safer but slower. A company using some platform might not even know which one they're using until it bites them.


99.9% of companies also aren't going to feel the performance difference of synchronous replication.

That being said, the setups I typically see don't even go that far. Most companies don't mitigate for the database going down in the first place. If the db goes down they just eat the downtime and fix it.


can use ansible (or ssh) and copy a tarball (or python package or pull docker container)


Networking with people you know in your career


Even within company, you want to have network laterally and upwards in different orgs, that is necessary for higher scope of work usually


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: