Won't it get annoying if new posts of lesser ranking keep showing up first?
11 karma · joined January 28, 2017
Won't it get annoying if new posts of lesser ranking keep showing up first?
Writing also helps develop ideas. Trying to explain things well in short sentences helps develop your mind. Surely this isn't useless.
That's not what companies think.
And a candidate that thinks of applying to a position knows nothing about the company's willingness to give feedback.
Most of the time I search for information I need is because I don't know anything about that part of the software. I never found this kind of information in Slack.
Parse the company docs, or our rep, and now we're talking.
Do you see other ways of getting feedback?
I'm thinking of writing a website that requires the employer to give feedback. Else the site will list the bad employers.
Or it requires the employer to pay upfront per candidate who applies, and they employer gets a full refund if they give full feedback.
If I were HR I'd be running away from this, because of liability, which is probably why employers don't give feedback at interviews. So the site will require candidates to sign away their rights of of suing the employer over the interview process.
https://news.ycombinator.com/item?id=13536957
What'd y'all think?
> something I have a solution for in a way that no one is doing
Is the general direction for this something you can share? 30 years of database literature accumulated a lot of knowledge. It's be a bold claim to say there's something powerful yet non-obvious.
That's not what I meant. I understand caching helps.
What I meant is will there ever be a way for caching to happen automatically behind the scenes without me ever having to do anything at all to make all this happen.
For example, the OS caches files, but I don't have to configure the OS file cache by hand. The OS takes care of it.
You also meant to say the go fix command does a lot (which is great), not that calling it is simple (which is not great).
Simply run the command below:
go tool fix -diff -force=context state-of-go/tools/gofix.go
How is typing 59 characters simple?It might be. It's a kind of garbage collection. Long-lived dynamic programs with bad GC run out of memory and exit with fatal errors, precisely because they didn't forget.
This is vague.
Running on the cloud is always more expensive than running your own infrastructure past a certain size and always provides less predictable performance.
Two days ago I thought of making a job site that requires the employer to provide feedback, and the candidate to sign a form that says they won't sue the employer over the interview process. This way the employer has no excuse for not giving feedback.
Would you use this?