Agree. Interviews taken into account side projects are biased towards:
- people who have free time to work on side projects (usually young people have more free time than people with families)
- people who don't mind sharing their code with others
- people who work on interesting side projects. If your side project is boring, that will probably bore your interviewers -> no offer
- people who work on side projects on regular basis. If I get to work on one side project every year, well, chances are I may have forgotten the hell I did on that project (depending when the interview takes place). If I work on side projects constantly, I have no trouble picking up a fresh one to talk about
As someone not familiarized with background checks, why is it weird to do bg checks after handing the offer?
If the employer does the bg check before handing the offer, that means the candidate hasn't resigned yet from their current job. So wouldn't the bg check expose the candidate? (E.g., my boss would know I'm thinking about leaving)
I'm the only one still listening mp3s? I have a sandisk mp3 player (size similar to the classic ipod shuffle) and I use yandex to get the mp3s. And I transferred all my old CDs to mp3 format as well.
I don't use my smartphone to listen to music because it's too big/heavy (running with it is so uncomfortable).
- they cannot unilaterally change the contract (Europe)
They asked me if I would be willing to relocate to a city in which they have an office. I declined. I'm still working from home. The company is big, so they don't care much about isolated cases like mine.
For Spanish speakers who know English, reading Don Quixote in English is probably easier (and more pleasant). The Spanish one is full of words that even though a native speaker can understand (with footnotes sometimes), it's just not as pleasant as reading modern Spanish.
Same. I always work on any given (hard enough) problem twice or three times. The first time I come up with some kind of prototype that may work or not, but it gives me foundation to work on the second prototype. The second one tells me how a final working and performant solution could look like, so I discard it and start from scratch. At the end I come up with the best possible solution I can provide.
Sometimes it takes fewer steps, sometimes more. And more often than not I let some time pass between attempts (maybe I go for a walk in between or I let a full day pass to work on something else).
The dragon book is a theoretical book. It's like any other (good) OS book out there: good source of information to know the foundations. After reading it, go out and read something more practical (which you probably won't have issues learning it since you now know the foundations)
The problem, I think, is what kind of employees may leave. If it's the best of the cream, then the company is in trouble. And frankly, the best employees can allow themselves to say "I want to work from home. You don't allow? Then goodbye".
AI should follow the same principle. It has the potential to become as widespread as the web... And yet here we are paying a fee per N tokens to use GPT.
Even though I know OP lives in US: in Europe you get written down the notice period on your contract. If you decide to quit or if your company decides to fire you, both parties have to honor the notice period (usually between 1-3 months).
If you get fired in Switzerland, your employer gives you a notice period of 3 months as well. Which is nice because it's plenty of time to find another job.