terrortrain's comments

Mmm, still seems snappy to me. What makes you say it feels bloated?

I guess I'm the foolish one, but I thought the title implied that the book was about algorithms you can use to make decisions, not decision making algorithms.

If the former sounds interesting, here is a similar book I read a long time ago: https://www.amazon.com/Algorithms-Live-Computer-Science-Deci...

Spherical photos or videos are my favorite. Yes you have to put on Google cardboard or whatever to really experience it, but it brings the VR experience brings me back to the moment, mentally, in a way that pictures can't.

We had the old essential phone, with the spherical camera attachment, and used the hell out of it. I still go back and watch those old videos. Venice in the snow was absolutely amazing.

I need to get another spherical camera ASAP, now that traveling is possible again.

I implemented a policy of "loom video, for all PR", at my last company.

Every video should include: an explanation of the problem, a walkthrough of the patch, a recording of the result.

PRs never sat long, because the willpower it took to understand the problem, the solution, and how to replicate/test manually (if you feel that necessary) was drastically reduced.

It shifts the burden of extra work to the requestor, who has motivation to get things merged.

Additionally, git blame became infinitely more useful.

I wish I saved the source, but I saw somewhere the term: "Don't repeat concepts"

While it doesn't spell out a word, I think it's much better advice than DRY, and better aligns with your heuristics.

Lots of people are staking already, so validators are running. The system shouldn't be vulnerable when the fork goes live.

What will really determine the successful chain, is where the stable coins go.

Linux for laptop just isn't great in my experience. My desktop is Linux, and all is well.

But on all my laptops, I find things to just be to much of a PITA. Eg: hibernate, is way too buggy to depend on. Half the time something prevents hibernate, and my laptop is dead and/or over heated when I pull it out of my bag. The other half the time everything is bugged out when it comes out of hibernate.

I found that when I'm traveling, I'm happier with a very underpowered laptop, which has great battery life. I don't even use wsl. GitHub codespaces has been working well enough.

If there were a track point keyboard, I don't think I could resist buying this laptop.

I would also love a 16 or 18 inch version.

Nice, I bookmarked your site. Weather data is surprisingly hard to navigate. Did you source it from NOAA.gov or somewhere else?

I tried to slap together a simple weekend app based on historical weather data by zip code, and never even got to the coding. Just spent most the weekend trying to decipher those API's.

Some if the comments here are way over the top IMO. Like a full time DevOps person went solo and spent a few weeks setting up their perfect deployment process.

If we're talking a plain saas type deal, I'd keep it simple, elastic bean stalk, or use a heroku or render.com like setup until you grow to the point of hiring a team. If it's just a basic saas, I don't see how a 1 man team could really out grow this setup. I've seen 100 person teams using heroku.

K8s is just way too much work. Even cloud formation is to much for my tiny show.

Use the automated backups setup by your host for your db. If you need to roll back, just redeploy your previous git hash. I typically use GitHub actions to deploy, so rolling back is just a matter of force pushing the prod branch to the sha I want to deploy

Skip micro services, they are too much work for a small time thing, and don't really provide much benefit.

I am generally following that advice.

IMO the fact that this is the best path is clear evidence that we need mobile app store reform. It's mind boggling to me that people still defend this status quo

I completely agree with this.

At a few of the start ups I've worked at, "no" wasn't in the dictionary.

It was always a dumpster fire, the product had some many configurations and options. There were entire sections of the apps I didn't know existed. I think that all these features are ultimately what killed the start up.

At one point I (developer) had to go on a call with a customer to tell them no because the PM didn't want to disappoint the customer.

Learning to say no is extremely important for startups.

Windows laptops with wsl have gotten pretty nice lately...

I have not regretted the switch at all.

The title is so click baity and the whole premise seems flawed.

Spacial reasoning wouldn't work on mac if the users were constantly resizing their monitor. If you always want your website to look and feel the same, keep your browser the same size.

If you don't want a site optimized for small screens, don't make your screen small.

Additionally, this is all complaints with no solution.

It's not an anti pattern if it's the only way to solve a real problem.

Just assume everything is touch and mouse...

My laptop is touch, and I use touch and the mouse frequently. Most apps work fine with either.

If you do and context menu or whatever for right click, make sure you also implement them for long touch.

All clickable things should be 40px or greater.

Is there something I am missing? Some great mouse functionality that I never learned?

It's not a ponzi.

Lookup what a ponzi scheme is.

I came here with the same question.

Hasura is really awesome, so far as I have used it.

Now I gotta look into prisma

I almost wonder if they aren't mutually exclusive. With hasura, you need to run your own server anyways, for auth or special cases. Maybe that server could run prisma? Let hasura do the migrations, and prisma track it?

This list is awesome, i love everything except:

12. Award all ties to your reviewer

A true "tie" is really rare IMO. If it really is a tie, we should all should agree that person putting work into it should be able to decide their own code. Not only does it cut down on discussion, but it cuts down on work and communication needed to get the PR past the finish line.

Allowing ties to go to the reviewer can lead to all kinds of discussions about meaningless stuff, like:

``` We should use forEach(...) instead of for loops, because that is how a most of other code is written. ```

In that example (from a real code review), the code is practically the same, just different style. So now the coder has to go back, re-write, re-test, signal for a re-review, re-discuss etc... All for something that is a tie, and doesn't actually matter either way.

Alternatively, letting non-issues through without a duel every time, saves a bunch of time and energy on every ones part.

I've been working on a competitor to this. http://tengable.com

Additionally, you may want to check out https://www.sococo.com/ which is another competitor.

I personally think this space is going to be big as people adapt to permanently remote or fully remote.

I'm getting closer to an MVP, and am interested in finding a co-founder. I'd love to find people interested in this space!

I haven't looked at it for a while, but wasn't that the big feature of ipfs?