Aha! I came across some odd Whiteclaw (alcohol) product placement on Unsplash, and I was wondering if “influencers” were trying to make a go of it on the platform, but that didn’t seem likely — now it all makes sense.
I fail to see how "per capita per square mile" is a useful measure.
_Anything_ measured in that way would show densely populated area vastly outnumbering rural areas, perhaps with the exclusion of things that essentially don't exist in cites, such as "number of farms per capita per square mile".
The measure appears to be concocted specifically for Lying With Statistics™.
The "murders per capita per square mile" metric really gets to the heart of the question on every American's mind: what percentage of face-to-face interactions are murders?
If you wanted to track that you'd need to do the opposite of what GP is suggesting.
That is, a dense urban area would have more face-to-face interactions than a sparse rural one. Given two areas with equal levels of per-capita violence, it would then follow that the more sparsely populated one would have more violence per face-to-face interaction, not less.
Right, I guess you'd actually want a measurement like "murders per population density" or "murders per (person per square mile)". Or, as it's more commonly known, murder-hectares per capita.
Murder-hectares per square capita? Murder-capitas per hectare? I'm not actually sure how the dimensional analysis works out.
This is absolutely absurd. We're talking about the US here, so it would be murder-acres, and that just sounds like a country club you really shouldn't join.
Wouldn't that assume that murderers do some kind of random walk, and randomly kill some person they happen to get close by?
I'm sure there are those, too, but IIRC in most violent crime the attacker and the victim know each other. Do people have substantially bigger social circles in cities?
This article seems to implicitly characterize it as a positive, but the lower cost of business in the Toronto tech scene is subsidized by low wages for tech workers.
As the article states, the talent and diversity of education is top-notch, but the compensation is yet to match—Toronto tech workers need to demand higher wages.
When you compare cost of living in downtown Toronto to the average developer wage there, it is pretty grim. You can make the same amount or more outside of Toronto (Mississauga/Oakville/Hamilton/etc.) while the cost of living is down significantly. You could live cheaply in Toronto, sure, if you like rats and cockroaches.
I recently made the move from Hamilton to Toronto. While I completely agree, the COL in Toronto is through the roof compared to Hamilton, I've found it to be worth it.
Toronto is a world-class city, Hamilton and Mississauga simply are not.
Keep in mind this anecdote is coming from a single male in his 20's, so I've found the nightlife, music scene, and social opportunities to make the high cost of living worth it.
I would further argue that tech jobs in Hamilton/Mississauga (or other satellite/burbs) don't compete with Toronto-proper in terms of compensation. Which leaves you with 1-2 hour commute each way just to try to save a bit on housing, and still not getting the benefit of properly compensated tech work.
>I would further argue that tech jobs in Hamilton/Mississauga (or other satellite/burbs) don't compete with Toronto-proper in terms of compensation.
I have to disagree with you here. The highest paid senior developer job I was offered in downtown Toronto was about $155K (after benefits etc.) meanwhile I'm working a contract job in Mississauga that pays significantly more than that ($70-80 per hour per client, 40 hours+ per week). Its a personal anecdote sure but my experience over the last ~6 or 7 years of working in the GTA has lead me to that conclusion.
I don't think you can compare full-time employment with an hourly contract directly.
The rule of thumb I've heard a few people use to convert from employment to contract is to multiply your hourly employment earnings by 2.5 to arrive at your contract rate. By that math, you're still under-earning outside of the downtown core.
Mind you, I'm not sure that conversion has ever fully rung true to me, but the general point of not being able to directly compare still stands.
2.5 seems a little excessive. By that math someone making $100,000 a year salary should be earning $150.00 per hour contract. $150.00 per hour contract at 40 hours a week is about $312,000 a year.
You're right about not being able to make a direct comparison. My understanding, and the reason I choose to work contract, is because we have OHIP, so health benefits aren't too important. I think a company pays something like ~$5,000 a year per employee to insure them. Then when you factor in bonuses (if any) the salary rate is still abysmally small compared to if I were to work contract.
I went from making $70,000 a year in Toronto, to $70 per hour. That jump for me was absolutely massive, and I essentially started making double (after taxes $70K per year became $140K per year).
Perhaps the problem is not the pay in Toronto. Perhaps the problem is with salary developer jobs in general.
This. If you're commuting 1-2 hours this is a hit on your income...i think most don't realize this. Downtown toronto is worth it depending on your goal.
I just had a flashback to living cheaply in San Francisco. I had a room in a Tenderloin SRO. I saw a cockroach in my room about once a week. Until my neighbor the hoarder moved. Every cockroach on the planet had been hiding under his stuff, and when he moved his stuff, they decided to come check out my place. Shudder...
An important additional component of the GDPR is that an individual can revoke their consent, and require all previously collected personal information be deleted.
Kira Systems | Toronto, ON, CA | Onsite & Remote, Full time & Interns | https://kirasystems.com/
Kira Systems is a fast-growing software company that uses machine learning to help professionals uncover relevant information from contracts and other documents. Our award winning software, Kira, helps make contract review faster and more accurate through combining powerful machine learning combined with an intuitive user interface.
Our stack is a Clojure-based reactive single-page web client code and a distributed backend to handle internal computations. We're looking for people with Clojure experience, or an interest in working with it.
E.g. https://unsplash.com/photos/GMLfxktwWcM or https://unsplash.com/photos/RtdjA55Su2k