It makes a lot of sense for businesses, especially where different countries might have different regulations. E.g., amazon.ca and amazon.in. Both sites are in English but it makes way more sense to split them up by country.

Maybe, maybe not. As equity holders get older they may be looking to cash out so they can fuel their retirements.

I don't think that's something Gabe is interested in, but we're talking about what will happen when he dies.

He did at one point. I think he's said that he likes being in full control of the project, so he took back over the porting process.

It's really impressive that a single developer does as much as he does.

The Word of Wisdom, which outlines the health guidelines of not drinking alcohol and using tobacco, as well as eating less meat, eating more grains; was originally just as the name suggests, words of wisdom.

Joseph Smith drank wine, used tobacco, and drank coffee up to his death.

It wasn't until the early 20th century when it started to be treated as a commandment. This is around the time when they started codifying a lot of doctrine, stopped practicing polygamy, and started to function more like a mainstream religion and less like a cult.

Source: raised Mormon, went on mission, took religion classes at BYU-Provo on church history.

But guys, if we use agile then we don't need requirements! We just make something and then the customers tell us if we are on the right track, we just get to iTeRaTe

Wow, I didn't expect an expert to chime in.

The plural of moose is meese.

Right. There is no solution to the halting problem, that's been proven. But you just showed you can very easily create a way of practically solving it. Just waiting for 10 seconds does it. That will catch every infinite loop while also having some false positives. And that will be fine in most applications.

My point is that even if a solution to the halting problem is impossible, there is often a very possible solution that will get you close enough for a real world scenario. And there are definitely more sophisticated methods of catching non-halting programs with fewer false positives.

A full solution to the halting problem can't exist. But you can definitely write a program that will "reliably" detect them to a certain percentage.

And many applications do exactly that. Firefox asked me today if I wanted to stop a tab because it was processing for too long.

flat white wall

Hey guys, look at this light mode user! My wall is dark mode. 😎

In a serious note, a developer should be aware of how licenses work. Just copy pasting from Stack Overflow likely breaks the defaults license. You could open up yourself or your company to serious legal trouble. And it really isn't ethical. I wouldn't want code I shared in a certain context be stolen by a large corporation and make them money

There's really good documentation out there and there's bad/nonexistent documentation. So stackoverflow is going to be a more consistent experience.

Also I think it is a bit of a skill to be able to read documentation well, especially for Jr. Devs that might not have fully grasped OOP.