euphemize

Agreed, I'm quite sensitive to the scrollbar size when I land on a new article, and in this case I almost closed the window, thinking this would take the whole day to read :)

Yep, sounds much more natural at the end :)

Jamais entendu ça de mes trente ans au Québec

Also agreed. I will use single-letter variables like "c" or "x" occasionally for lambdas or anonymous functions, but that's about it. "lambda x: not x" in python - anything longer I think should be descriptive.

Agreed with you. Perhaps if you're using temp or tmp, something could be done better, but I see no harm in using the others. If you're counting things, a variable named "count" sound perfectly reasonable to me.

Interesting. Had a google interview not too long ago, and this was exactly the question asked to me - how would you design an algorithm to find overlapping free time from person X, Y and Z. I guess they got more practical with their questions over the years.

Looks great, liking that is suggests times too.

Great realization. I'm in a similar boat. On the upside, 30 is still quite young, there's lots of time to do other stuff and slow things down ever more.

Montreal is not known for its tech scene. Scrolling through this page, I can immediately identify:

- the "startups" that are a 1-guy team doing "disruptive-PASS-agile-SCRUM" consulting

- large, partially government-backed monsters where money is burnt and not much is produced

- the students who just built their first social photo-sharing app, wondering why they can't find any funding

I've heard of them from others or was offered jobs there - there isn't a lot to choose from around here. Salaries are low as the city is cheap. There are also good companies in that list (some great ones even), but I'd say it's pretty inflated.

I work remote for a US company with its headquarters in Europe, it's the best arrangement possible, I'd recommend it for others (paid USD, half-day overlap with coworkers = lots of time for quiet coding, trips to Europe often to catch up with team).

So, you were in MTL for ~1 year? Working / studying?

I used to try and reason with ES settings on production, for about a year or two. Something would invariably break, unless you spend time with it every day, checking configurations and monitoring performance.

We use the AWS ElasticSearch service, and while it does not provide the same flexibility, it's been fantastic for us. No configuration files, no weird restart behaviour, no thread pool madness - it just runs. You can upgrade your instance sizes seamlessly and it integrates well with other AWS parts (ex: cloudwatch).

> My ground rule is that anything I easy_install will go into env, and env will quite often be (re)built on a separate machine that matches my target environment. So I treat it as a disposable folder, and it’s never committed to any repos.

Was wondering, do you pip freeze > requirements.txt? I don't see the file in there, but I assume that's what you mean since you mention that none of the env folders make it into version control.

On a semi-related note, I used to have tons of projects like this a year ago, and having moved most of our python code to AWS lambda, our repos have shrank to maybe 25% of their original size. Granted it's not fabulous if you need to run a JS app on top of your Bottle framework, but we used to have a lot of small services here and there, the provisioning and deployment was so much work.

This is an unfortunate title for this post. AWS released API Gateway sometime last year, and this makes it sound like a caching layer behind API Gateway, to access S3 files.