p-o

Hoax is quite a strong word where there's been quite a few replication attempts with various degrees of success. Like others have said, we're not sure what this is, but it almost certainly isn't a hoax.

As for this video, well, it's like all the other ones that came before it, we'll know more once we have more data/videos/replication attempts.

[Deleted]

Is it me, or are they implicitly saying that they're ditching React Native in favour of native code? That's a pretty big deal if that's the case.

Maybe it's the case, but Github has always had issues with uptime and stability.

At my current place of work, we have this strategy and I think it's a mistake. app/lib is just another way of writing app/service. It becomes, over time, a chaotic place where everything goes. If it doesn't fit for _any_ reason, app/lib becomes the place where those files live.

The benefit of lib/ is clearer in my opinion. Files that live there are only explicitly loaded. Some might be loaded in development, some in production, some in test. The conversation about the structure becomes more important because you need to think about what is going to consume your class.

But I think we could take this a step further and instead replace lib/ with engines/. This way, you can create multiple Rails engines that will have their own paradigm and environments' handling.

Every Rails application I got to work on had a lib/ (or app/service) that could have been grouped in a few different engines/. The benefit of using those kind of engines is that conversation about architecture, pros/cons get more defined. At least that's been my experience.

Today, we have a lot more bandwidth at home. I always wondered if having a "social network" device at home would make sense in the future.

I imagine a device like a router or an Apple TV, that you connect at home. Then, you own it, everything you post is on your little device. Maybe you pay a few bucks a months so you can upload an encrypted backup in the cloud somewhere.

There's obviously downsides to it, but I think I would buy such a device.

This is the kind of story that is amazing to read and even more amazing to hear in person. Since you're telling it today, I assume that even though it was probably a pretty stressful event when it occurred, you now have the perspective to enjoy telling the story and see everyone's face when you tell it.

Thank you for the laughter.

Every crisis introduces a new type of failure that was not expected. The 2008 came with the realization that the housing market was not as bullet proof as people thought.

This one is no different. It's possible we recover from it very quickly, but it's also possible that the bank run that we saw earlier this month introduce a new type of failures that no one thought was possible. I'm of a curious nature, so I really wonder what's coming.

I'm not sure if it's a trend but I am sure that I like to see people being vocal about highly readable codebase. I have yet to see this mindset in workplaces I've been at.

I would love to see a future where folks write code without thinking about how "scalable" or "performant" their code is and instead focus on how easy it would be to change the behaviour of existing code.

For small projects and startups that are still figuring things out, tests are useful to prevent regressions, and I would spend my energy doing exactly that.

Code coverage should only be an after thought. Whenever a bug shows up, writing a test to cover that edge case is going to help you ship with more confidence as more bugs are found and fixed.