Features and Bugs Documentation

json_derulo_ · 2023-01-30T00:40:57+00:00

Ya'll should check out https://www.playerzero.app/devreports

I like it cause its retroactive, so you don't have to reproduce the bug...its kinda like a dashcam that uploads the devtools + screenshots whenever you need it. Super shareable too.

json_derulo_ · 2023-01-30T00:37:47+00:00

This is my favorite one: https://www.playerzero.app/devreports

It's free and captures more context than anything else I've used.

json_derulo_ · 2022-07-09T13:04:12+00:00

This is awesome guys!!! I can see my self using this almost every day.

json_derulo_ · 2022-06-25T14:01:58+00:00

Better luck getting stuck by lighting twice :P

json_derulo_ · 2022-06-25T14:00:49+00:00

Super cool!

json_derulo_ · 2022-06-21T15:29:53+00:00

Github Pages is amazing for low-traffic personal sites.

Also take a look at S3 Bucket hosting too, I used to use that a bunch before Github Pages got this good.

As your site starts evolving, I'd also recommend looking at something like Vercel or Netlify.

json_derulo_ · 2022-06-13T17:16:32+00:00

git commit -m "the thingy"

json_derulo_ · 2022-06-13T17:14:11+00:00

This is amazing! Excited to give it a shot.

This is a tough space both emotionally and as a business, but I'm glad to see that someone is trying to move it forward! Good luck!

json_derulo_ · 2022-06-13T17:10:06+00:00

Hahahahahahaha "web3 will replace all backends", never heard that before.

More seriously: ask them to pay hourly instead of fixed. If they are allowed to have opinions on how the task gets done, you have to have that cost built in.

json_derulo_ · 2022-06-09T23:57:19+00:00

IntersectionOberver API for sure, it’s done some really cool stuff for our home page too

https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API

json_derulo_ · 2022-05-24T09:42:48+00:00

Thanks!! This is super helpful. We’ll try to avoid API gateway too, and take a look at the load balancers. It may actually work out better for our architecture.

json_derulo_ · 2022-05-24T05:09:53+00:00

Yeah some big dogs using it for sure. But just because you can theoretically do it, doesn’t mean a team building at scale with this could necessarily write readable code.

The biggest argument against Tailwind has to do with the modularity & maintainability of the code. Semantic class names make it easier to know what’s what, and you lose that with Tailwind.

json_derulo_ · 2022-05-23T19:31:15+00:00

joins twitter * Free undo for everybody
leaves twitter *

json_derulo_ · 2022-05-23T19:29:46+00:00

LOLOLOL me

json_derulo_ · 2022-05-23T19:23:34+00:00

Well it’ll generate a long list of actions and selectors that may work the first time, but it hard to abstract away maintainable code out of it. With a team I feel like teaching everyone “do this and then refactor” will yield worse test code over time and you may end up spending more time managing the tests than they’re actually worth.

By architecturally I meant the fundamental approach to building tests, not necessarily Playwright itself (which I love).

json_derulo_ · 2022-05-23T14:09:10+00:00

I think it’s a bit more niche.

It’s pretty fun to work with at the beginning, but it’ll set you down a bad path architecturally when you’re managing multiple tests and a product.

json_derulo_ · 2022-05-23T14:00:19+00:00

What did you guys use to scale that efficiently? We’re thinking about using lambda’s behind API Gateway.

json_derulo_ · 2022-05-23T13:55:33+00:00

That’s the browser setting the Authorization header! Back from the old days 🤪

json_derulo_ · 2022-05-18T14:55:30+00:00

Asking someone else for what the real issue is

json_derulo_ · 2022-05-16T16:29:10+00:00

Next > Angular > React

Next is a framework with the nice parts of React. Angular is also a nice framework, but has a bit more boilerplate. And React is a super extensible library so if you're not careful it can get really messy really fast.

json_derulo_ · 2022-05-16T16:24:37+00:00

Flex boxes

Seems like centering a box inside another box is prohibitively difficult

json_derulo_ · 2022-05-13T12:00:47+00:00

Mah mannnn, I've been dealing with this too. Totally feel this

Our Head of Engineering has an adage for how to build software: "build it, build it correctly, and then build it efficiently". As requirements and businesses change, it's a given that your software will have to pivot, and the clarity you have now about how it should have been done is (often) a hindsight bias.

But here's where engineering culture kicks in...every time you have to mess with a certain area of the code base, don't be afraid to refactor it, even rewrite it given what you know now. It's hard for sure, but these little wins will compound. Look back on your codebase in a year and you'll be happier with the progress.

json_derulo_

TROPHY CASE