picardo

I see, thanks for your input. Most of the workflows I worked on involved provisioning one database per app, so I hadn't entertained this angle.

Are there any risks to changing ACL rules on a production database server from a stability perspective?

Good point. Phrasing it as a trade-off is the better approach. Agree with the downsides you listed, as well.

Better security guarantees, for sure, but if an unauthorized user gains direct access to your database, you might have bigger problems from a security perspective.

I qualified it by saying "if you're building an OLTP app" though.

I speak from personal experience. If you know a good usecase for ACL in database for OLTP workflows, I'm all ears.

> Grant Permissions on Specific Columns

This feature might be great for OLAP systems, but it's awful for OLTP systems. The last thing I want is debug permission errors bubbling from my database into the application layer. It may not be as efficient, but you should always manage your ACL rules in the application layer if you're building an OLTP app.

Even teams with good team cultures can screw up their processes.

In my experience, a bad process is one that 1) produces responsibility without accountability, and 2) does not account for process bottlenecks.

Your description makes the first company seem better in comparison until you stop to think the tradeoffs. There are always tradeoffs.

My previous role was in a team run like the first company. There were sky high barriers to get code into production, mostly centered around code reviews. It could take weeks to get the attention of enough people to review your code. Complex features had to be broken into multiple code reviews, and only people at your level or higher could review your code. So you ended up with a lot of code reviews and not enough reviewers.

The result? Politics. And where there is politics, there is corruption.

One time, one of my former team mates casually asked me to send him some Bitcoin if I wanted him to move faster. I refused, and the code review was delayed. Another team member stonewalled my code reviews as a retribution on an unrelated technical dispute.

It took me weeks to move through all my code reviews into production. I left the team immediately thereafter.

Be careful what you wish for.

Good to see IDE support for TypeProf type hints[1]. I've been doing a lot of work in statically typed languages lately, and spoiled by how good IDE integration is with the compiler. Ruby has been moving towards static types for a while, but the lack of IDE support has always been the dealbreaker for me to go back to Ruby. The ecosystem needs more tooling like this.

[1] https://github.com/ruby/typeprof/blob/master/doc/ide.md

I built an API proxy using a CF Worker today. The deploy takes only 2 seconds. Its speed is its killer feature.

> Vagrancy describes when birds veer off-course and continue roving around — potentially indefinitely — in search of others of their kind. It is not uncommon. There are records of albatrosses spending decades living as vagabond singletons in the wrong hemisphere, Dr. Lees said.

This paragraph is almost poetic. As a human, I can relate.

Mitch has always struck me as a singularly sincere and dedicated individual. His passion for the end user experience show in his every product decision. As a developer, I've enjoyed using his tools more than I should. Most enterprise software is designed by committee. Hashicorp's products feel like they were designed by one person -- or perhaps they know their users extremely well.

I have no idea what this company does. Are they even in the same line of business as Facebook?

What would you say is the advantage of Vantage over AWS's Billing Dashboard?[1] I can configure it to send me daily reports and notifications if the costs exceed my daily threshold already. Why do I need Vantage?

----

[1] https://console.aws.amazon.com/billing

The counter to that argument is that the brick-and-mortar chains don't claim to be platforms or marketplaces for other products. The business model of a Walmart is pretty simple. Buy wholesale, sell retail.

Jeff was still with the company when the last version of the policy was announced, i.e. "3 days from office, 2 days from home." It was probably the head of HR who came up with it.

Jeff accepted it like, "Oh well." You could tell he couldn't care less.

But Andy Jassy looked ashen. I think his becoming CEO was the reason Amazon changed course. If Jeff had stayed, he would have let HR decide the policy for the entire company, and it would have been disastrous for AWS.

> The last update added support for the page up, page down and home keys. That should make it easier to get back to the top.

I use a Mac Air. I don't have these keys.

> Do you mean loading more posts when you reached the end of the list? This will also be added in one of the next few updates.

No, I mean the usecase when let's say I'm viewing a post or even when I'm on the home page, and I want to check if there have been new comments or new posts without reloading the page.

Some of the comments in here don't show up on Haxplore until much later. It looks like the API response is being cached... which gives me a pause because navigating the comments is the best part of Haxplore interface.

A couple of more ideas:

* Some way to go to the top of the page without refreshing the page.

* Some way to load new posts asynchronously without refreshing the page.

Nice work. Minor issue, but when I open the Menu with M, the focus should be in the dropdown menu, so I can navigate it with the arrow up and down. Otherwise, works great!

Thinking back on it, we always used Terraform with Pulumi, which creates its own abstraction layer for a CF stack. It's hard to pinpoint where the root cause of the slowness was.. but in principle having fewer abstractions allowed us to iterate faster, and fix the bugs more quickly.

Terraform can be frustratingly slow at times. You have to realize that at the end of the day, it's an abstraction layer on top of the public APIs of a cloud service. If all your services are hosted on a single cloud, you don't need Terraform.

We saw a huge improvement in our build times after we started using AWS CDK directly.

What is the usecase for Deno Deploy? Can you build full blown web apps with it? Or is it mostly for building small services, e.g. image transformation, CDN, etc.?

The biggest pain point of Yarn 2 for me has been configuring CI servers. With `node_modules` there is one folder you need to copy between build server to CI server, but Yarn uses some virtual directory system to link the packages, and I have never been able to make it work. I ended up using `nodeLinker: node-modules`, which keeps node_modules folder, and that completely negates the benefit of using Yarn 2 in the first place.

Great read. Thanks for the write up.

After a day of trying it out, I have to say... this is really terrific. I was fully prepared to be disappointed, but I was pleasantly surprised by it at every turn. I hope I can replace all my yml files with a single Earthly file someday.

Ah, I see. That's pretty cool. But all builds are run on the same machine, which is not a deal breaker; it'd be nice to distribute them on multiple machines, as well.

After a cursory look, it seems like there is no support for parallel and dependent builds in the syntax right now. Is this correct? Are there any plans to support that? That's the advantage of CodeBuild spec files –– they let me specify build dependency and order, but I have to write a file for each job. I'd rather write a single file with a simple syntax like the Earthfile.

I've been wishing for something like this. Can I generate AWS CodeBuild buildspec.yml files from an Earthfile?

I tried this a few months ago. Many features were missing then. I couldn't set up backups, and connect directly to `psql`. It was such a pain. I don't know if they've addressed those issues yet. It'd be a hard sell for me to store a database system for a production app in a Docker image.

Maybe for the very small sellers, yes. But Shopify will be fine without them. They provide a lot of value to medium size sellers with a lot of turn over, through their app marketplace and integrations.

Reddit started allowing its users send cryptocurrency to each other recently as well, through "community coins." ResearchHub's model isn't that different.