p-o

8 ms·

61.
by p-o 3y ago
[Deleted]
62.
by p-o 3y ago
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.
63.
by p-o 3y ago
Maybe it's the case, but Github has always had issues with uptime and stability.
64.
by p-o 3y ago
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_
65.
by p-o 3y ago
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
66.
by p-o 4y ago
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
67.
by p-o 4y ago
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
68.
by p-o 4y ago
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 w
69.
by p-o 4y ago
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 t