hiring-without-whiteboards VS errors

You might find this helpful

https://github.com/poteto/hiring-without-whiteboards

companies that do not whiteboard

You can avoid doing leetcode and get a job by choosing to interview at companies that don't use leetcode style questions as part of the evaluation. This repo contains a list of such companies, https://github.com/poteto/hiring-without-whiteboards

https://github.com/poteto/hiring-without-whiteboards and also focusing on smaller / less sexy companies which pay less.

hiring without whiteboards is the standard resource for this. i see lots of UK companies there, but haven't checked if they're all hiring right now

- you're underpaid - start looking elsewhere, there are tech companies in bhm that will pay more than that and you can get a remote job paying way more than that, the remote stuff is super competitive right now so it may take you until the 2 year mark to find something - i've never needed anything outside of my resume but certification, projects on your github, etc. are all obviously good to have. i've been in the conversation for a bunch of engineering hires and no one's every said "well the other person had a cool website" so don't sweat it too much - leetcode, et. al are really annoying imo. traversing matrices or doing binary tree stuff is hardly ever relevant to the job. here's a list of a bunch of companies that don't do the tests. https://github.com/poteto/hiring-without-whiteboards ; most big tech places are going to require them though.

Early stage start-ups and non-tech companies can also pay reasonably well and may have more relaxed interview processes. There’s also https://github.com/poteto/hiring-without-whiteboards which lists a number of companies that have interview practices that may be more amenable to your approach to work.

There are some employers that give more practical tests, but sadly they seem to be the exception.

Can you explain why we should this over https://github.com/pkg/errors?

The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.

I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`

Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors

Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.

Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.

Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".

And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)