348 karma · joined March 9, 2017
I updated the container for usual appliance maintenance. Entire thing is toast. Metadata files can't be read, mounted, permission issues and more. It's been four months since.
Thanks all, and have a great day.
When I had someone from another team take a look at broadcom and what they could do to spring, they said the licenses are permissive, it will be fine. Likely not that simple.
On the other hand, my mom used to read the physical newspaper. She would buy it at the gas station. She refuses to buy any type of news online. So it's unfortunately all Facebook and YouTube news shorts slop for her now.
A semi-related story: Freshmen year in college, I was about a week ahead in the sci curriculum and I blogged regularly about novel errors I encountered and how I fixed them. During lab late in the semester, I happen to look up into the next row. I found the duo there reading my blog post.
Good riddance indeed.
At a technical level, there have been previous attempts for these shared design libraries with reusable components. We're mostly using react. The first generation the design system ended up putting all of these complex components like "Product Display" or "Order Builder" and so on, all driven by props. That resulted in prop explosion and increasingly unreasonable maintenance burdens. It also became effectively locked to the versions of React that were available when it was made - teams could not afford to upgrade either their own apps which caused the library to freeze. A second generation of repeated many of those same mistakes, not composable enough, too tied to a definite version of react, too tied to a definite version of mui, and so on. The tech piece, in addition to the people-problems, is just as hard and important too.
Adoption will be driven by funding, value and time.
All that said, I also read HN regularly and I know I don't touch beyond the very tip of the iceberg and that's fine.
This isn't the same as the forwarding service, but maybe the overhead wasn't worth it anymore.
As I entered into a more senior work role, I refused to put work email or teams on my phone. No device management or malware on my personal device.
Instead, I found out that my company let me use an iPad with email and teams and the management software didn't infect the whole system making it nearly useless, and I could even take screenshots. It's not perfect but let me have a lighter daily carry.
All that said, I can't develop on an iPad. I think if I could get an MBA for on the go meeting type work and a mac studio for delivery, that would be fine. But then we're right back to: I refuse to have any of that stuff on my personal device.
First time it worked great even with only a link. Second time I had it generate some comments based on a small prompt and kept telling me something went wrong, alternating between comments and that error state.
Good work!
There's definitely price creep in the iPhone lineup and I'm sure ASP has increased because of it.
In your readme, in the "A bit of history", it should be `has many fewer features`
On a more technical note, I wondered if you have any stories working with Prisma and Next? It works but every ORM has its pros and cons. My annecdote with the two is on a project recently, I had issues bundling the appropriate prisma packages during a Next standalone mode build.