droussel's comments

Now that I am in my forties, simply having a bad night of sleep can have me forgetting names of colleagues and messing up the names between the dogs and my daughters. Lack of sleep is one of the most debilitating thing and it certainly wasn't like that 10-15 years ago. Ageing sucks!

100% that. The only way to filter on the seller is to dig to the deepest category level, which is not ideal.

I live in Quebec which is 100% hydro, thus clean.

I am a French speaking Québécois and do work with many French people (downtown Montreal). You can't deny that the French French and Québécois French uses a lot of different words. They are still the same language for sure, but we often have so much fun exchanging funny expressions.

A funny anecdote was when I was working with a guy name Jean-Nicolas and all the Québécois people called him Jean-Nic. That was very funny to the French guys hehe

I am Québécois and am in no way hostile to other languages. What we are protective of is that the official language is French, for historical reasons yes. Meaning, if I encounter an English speaking person, there is a big probability that I'll switch to English just because I'm not an asshole and want to be nice. But, I also don't want my whole culture to disappear and be assimilated to at the same time I do care that I can be served in French when I go out to the restaurant, etc.

If people made fun of OP's accent then they were dicks and I don't think the majority of people would do that. We do however switch to English quickly when we determine the other person is anglophone just because most people in Montreal are bilingual and hey, let's make it easier for everyone. If the other person asks me to continue in French, I'll gladly do so.

Hey, don't worry to much about your accent. I am Québécois and French is my first language. I can speak English very well apart from that terrible accent... I used to work at a place where we had daily calls with the office in California and most of the engineers there where Indian people speaking English. It probably took me 2-3 months before I could understand a single sentence on the conf. call. Their accents were just that bad (to me).

All that to say, don't be shy of your accent. Personally, I am simply happy when people make an effort to learn my language. I'll listen patiently if they stumble on words, I'll help where I can, etc. As long as they are also patient with my own horrible accent :)

I have an uncle who speaks 6 different languages; he really likes picking up new ones. I once had a discussion about how he could pick them up so quickly and he basically said what the parent was saying: use it, practice it, read newspapers in it, speak to people that speak it too. Immerse yourself, accept that you'll be uncomfortable for a while, and before long, you'll be able to hold a simple conversation.

He also said you know you are fluent the day you can casually joke in real time with people and make them laugh (at the joke!)

Boeing has sued Bombardier to keep it from selling their C-Series aircraft in the US which ultimately led to Bombardier basically giving away the aircraft to Airbus to stop bleeding out money.

>The timeboxing of planning is also a very bad idea. I worked at a place where we had a timebox of 2 hours for planning but really after that we were nowhere near a realistic plan for the sprint and it would take another 2 or 3 days of knock-down, drag-out meetings that would leave us all exhausted to understand what we had to do. After that the work was mostly downhill, at least the way I saw it, but one of the other team members would consistently burn the midnight oil at the end.

If your backlog is properly groomed and you have sufficient time for planning and the team has the last word on how much it tries to take in, then it works beautifully.

If my team was to have that problem, it would come up during the retro, we would add a few more hours for the planning event, hold more or longer grooming sessions, refuse to plan work which we can not yet estimate because the requirements are not clear, etc.

And btw, your "implementation of Scrum" wasn't working properly; probably because you weren't living up to the Agile principles.

"Agile" is a set of principles and values as defined in the Manifesto for Agile Software Development. If how you work contrary to those principles, then you simply are not "Agile", no matter if you call it that.

"Agile" will never fix bad management, nor will anything else for that matter.

MagSafe! I am still angry that they dropped it, can't understand the decision on that one.

I don't know much about all those and I experienced VR (other then the Avatar movie) for the first time this weekend at my friend's place on his PSVR. I really enjoyed Moss and still felt ok after about 45 minutes. I tried a kind of light sim demo with crappy 1995 looking graphics afterward and I thought I was about to vomit 2-3 times while "flying".

Anyway, what would be the difference between the PSVR and a 6DOF system?

That's funny because STS-1 was actually made in an iterative way. If it's good enough for a shuttle, I guess it's good enough for about anything else.

https://www.cs.umd.edu/~basili/publications/journals/J90.pdf

Being a "minimum viable product", it may actually be quite big and take a long time to reach. To me, the goal of properly defining an MVP is that you do everything needed but nothing more.

And getting stakeholders, or users, in the loop and validating at each iteration is still worthwhile to make sure you actually build the right thing.

In many industries as well as many government branches it still works just like that. They do not mandate a way of "writing the code", but software projects must pass gates and receive approvals at each stage before getting funding. They have to provide comprehensive analysis and architecture documentation that cover everything under the sun before a single line of code is written. And then, once a dev team starts coding, it has to go through the whole loop and if something specified doesn't make sense "on the real world". Or, more often, they just do the proper thing without telling anyone.

It was actually mandated for many government projects for a while. A good history of iterative development can be read here: http://www.craiglarman.com/wiki/downloads/misc/history-of-it...

> The average consumer conflates iOS apps with Apple

More then 1 person assumed I worked for Apple when I told them I was developing iOS apps; so you are totally right!

That's the point the OP was making. He is fine with paying 100$ for sushi (or not eating sushi) if it means there are fish left in the oceans.

It wasn't meant in the sense of "I know it leaks because of the smell", it was literally said as "The leakage is caused by the smell". The conversation was in French so I have to translate here :D. I wasn't trying to be an ass at the time, I was just... surprised at their twisted understanding of basic logic.

Yes, it does. For testing, in smaller business, this is fine however as you can register up to 100 devices. Enterprise certificates were much easier to use in big enterprise thought even if they weren't really "meant" for that purpose.