This may not be news to developers, but might be useful for broader company discussions.
This may not be news to developers, but might be useful for broader company discussions.
> (Also, their license page could do with some proofreading)
Interested to hear more! We did a few rounds of proofreading, did you find any typos?
Or what if I start taking notes on some random subject for fun, and eventually I write and sell a book based on them? All of a sudden I need to start paying a yearly fee?
It's not a prohibitive amount of money, but I'd be much happier with paying a one-time fee for the current version, then buying future versions if I choose to.
Yes, and there is some correlation between age and seniority. If companies are so eager to hire senior developers, they might consider the preferences of candidates who have been working long enough to fit that description.
You're also now competing against a national talent pool vs locals only
You decide that B has to compete with A on talent, but A doesn't have to compete with B on price.
Does that make strategic sense?
Companies: "I don't have to pay you $big_city rates because you live in $small_town and nobody there will offer you $big_city rates."
Candidates: "I don't have to accept $small_town rates because I work remotely and can work for a company in $big_city."
That said, I wouldn't trade this lifestyle for anything. The only complaint I've ever had is that coworkers not capable of performing in a remote environment sometimes last too long at the company.
OTOH, your applicant pool is limited only to the time zones and legal jurisdictions you're willing to hire from. If you're office-based, it's limited to those who can reasonably commute there.
One thing I find difficult in remote teams is the ability to ask a coworker a question quickly. There can be a fair amount of lag time over messenger and this occasionally blocks the completion of work.
Agreed. But the reverse is also true: it's harder for people to interrupt you.
80 seems good to me.