doctorbuttes

Dataloader is a super simple idea + library; I doubt it needs any updating. Edit: great video on it by creator: https://youtu.be/OQTnXNCDywA

I think just a brief "too slow" underneath the input would suffice.

Good thing what he does outside of work isn't any of your business. We should make decisions based on outcomes rather than our assumptions.

Let's ban anything not written in assembly.

Sure, many sites are bloated, but I can't help but feel the sentiment is somewhat dramatic. Cancerous growth? "Client-side queries!?"

Performance is just one piece of the UX puzzle. Users don't really care about bundle size... They care if your site provides value in a reasonable amount of time.

Retool seems pretty awesome so far! I got an immediately useful admin panel working in about 20 minutes today.

I have friends that believe there is a moral obligation to take psychedelics to expand the mind and increase empathy. That’s a little extreme for me, though.

Using Notion is awesome, but does require you to bring your own structure. Templates help, but much like any other process in your organization, it requires occasional review to keep the team on the same page to keep it tidy and useful. It helps to have a champion/steward for it.

Really big fan of everything in this stack; I've been building my product on React/Apollo/Prisma/Postgres and it's been a pleasure. It's nice to see a well-thought-out architecture added to the process. Great work.

I'm also enjoying Kubernetes. I started a hobby project on GKE just to learn, but now the project has 8,000 MAU or so and will be scaling up more in the near future. K8s is totally overkill, but I've had a good time and it's worked well so far.

Cutting myself off and just shipping it. It can’t be understated how important it is to cut your own scope and get something useful out there. The feedback and validation you get will keep you going or force you to pivot to something else. This runs counter to the exploratory, learning nature to building something new, but i think it’s possible to balance. For example, for this feature I’m going to noodle on and play with for a while, but for this other feature I’m going to deploy a 0.1 version of it immediately, and then a 0.2 the next week, etc. It’s amazing the half-baked shit I’ve pumped out that someone out there has loved and wanted more of, which in turn motivated me to keep going and improve the experience.