m1keil

Great viewpoint, thank you

Who are these freeloaders and what scarce resource is being consumed by these freeloaders in this case?

Ah, nice. Thanks!

If I understand correctly, this works more like a pipe and not a file in the sense that you can only read what you wrote once, right? But a nice trick nonetheless.

A poor DX can happen in the cloud as well. Waiting weeks for IAM configuration to be solved or a security group to be opened..

Just finished listening and greatly enjoyed it. Very inspiring story.

I would argue that any company with 3 or more employees needs an SSO.

Back in the day SAML was the only game in town, SSO was an enterprise feature. Nowadays with oAuth/OIDC, this is a no brainer and you can get a basic setup going with plain Google Workplace (Gsuite/Gapps/...) without the need for anything else.

Yet SSO keeps being bundled in the premium feature list of most of the SaaS products out there, costing 10x to 100x more per user.

14$ sounds pity, but when you take it in the equation of "price per slot * total slots * products * 12 months", you can get to some serious numbers even for a small 10 people company.

Notice I said "slots". That's because the nasty trick lots of SaaS do nowadays to boost their profits. They will auto provision a slot when a new user onboards, but when that user account gets removed (with or without SSO), they will keep charging you for the slot until an admin goes and reduces the slot amount by 1. This is something that AccessOWL can help with, I suppose.

The question is if the script outgrew its original intended lifespan.

In my opinion, shell scripts should be used either as glue or due to portability reasons. Rewriting a perfectly good and working script just because makes no sense.

So if the script started as some quick and easy way to deploy to prod but slowly becomes a massive cli "one tool to rule them all" kind of thing.. maybe it's time to change course.

For complete over-engineering please also add: automated CI/CD, secret store (with rotation!!) & SOC2 audit.

what?

We are really happy customers of Linear and have nothing but good things to say about it. Product is light and snappy, customisable just in the right amount and UI/UX is very predictable.

Biggest weakness is definitely the "workflow" part. For example, trying to automate rather simple workflow that involves email to ticket isn't trivial and either requires you writing your own integration or passing via something like Zapier (or writing your own integration with Zapier?).

Additional downside I experienced with .io in the past was the non existent support or urgency when it comes to technical issues.

Some of you might remember the incident with .io back in September, 2017.

Since then, ownership for .io passed hands and landed at Donuts who is also managing .org so I assume it's in a better shape now, but lesson was learned.

If it would be up to me again, I would push to use .io or any other vanity domain for marketing only.

Nix shells is a killer feature so it seems smart to me to create a wrapper around it to simplify the experience. On the other hand, it's another layer of abstraction that you need to learn and debug when stuff breaks.

Will definitely keep and eye on this.

That's exactly my point, that is _yet another_ service you need to go through to get a clear picture of what is going on.

These products have their place, but they don't make sense until you reach a certain size.

I think it is similarly easy to spin it the other way around. "AWS is just selling you the gun and the bullets, you are the one who is shooting yourself in the foot".

I don't think I said AWS is shit or that GD is worthless, after all, I use both by choice. Yet, I do not think that AWS are blameless when it comes to certain decisions of how to bill, how to present data and how to document some of their features.

For example, in order to discover something is wrong with your GD billing, you must have CloudTrail in place, and the appropriate infrastructure to query it. And even tho AWS can easily alert you about weird trend in your API calls (like suspiciously high Describe*), they won't do it. They do it with Trusted Advisor when you have under-utilised EC2 instances (which requires Business+ support plan per account).

Someone mentioned in the thread the need for SCP in order to disable regions. Why should you have go all the route to SCP? Why can't we disable regions by click of a button under root account like it's possible for some of the latest regions?

Is something inherently wrong in it and pure evil? No. But I think the defaults can be better. I think AWS can improve their customer's default posture when it comes to Audit and Security without the need to have to decide between 10 different services with different billing plans and gotchas.

Yes of course, $400/month is peanuts so does $8000/month for certain companies.

The point is not the absolute sum but how easy is it to spike your bill by 30 times.

The way GD works, you are pretty much guaranteed to overpay for it sooner or later. If you can afford it.. great.

GuardDuty is another example of brilliance of AWS pricing scheme and how they manage to twist your hand to pay extra which can cost quite a lot in the end of the month.

When comparing EC2 to servers, nobody adds the added premiums of the extras. Things like CloudTrail, Support, GuardDuty, CloudWatch. All of these things have a variable cost that grows with usage and very hard to predict ahead of time.

Just last week I discovered our GuardDuty bills went up from $15/month to $400/month. Inspecting closer, the issue was a small script that did AWS API call at a tight while loop in a couple of EC2 instances.

So if you choose to enable GD, make sure to have your monitoring in place, gradually enable GD across the infra and establish clear baselines and alerting in place for costs.

Installed via brew to try it out. Won't lunch. The process is running, but I just can't seem to make it pop up?

I really wanted to address the speaker's points but what's the point, it's just a rant (kudos to him for being upfront about it). Instead I just went and donated to Signal once again.

Good talk but most of the information is pretty much word for word from a book with the same name by Tom Standage.

Just FYI, you can only enable object lock at bucket's creation time. You cannot enable it later on.

From UI/UX point of view, it even got slightly worse since 2020: The user no longer needs to type the code. Instead, the same code is prompted and the user just needs to click "Accept" or "Decline", with "Accept" being emphasised.

Just took a quick look and couldn't find any way to do it. That would be a great feature actually.

If you need to do any image manipulations/highlight on your screenshots, two of the best tools I found are:

1) Monosnap (freemium) - https://monosnap.com

2) Cleanshot ($29) - https://cleanshot.com

Both tools also include large amount of extra functionality for taking screenshots and recordings.

I had issues between Sydney and Eu earlier in AWS.

Yeah it won't hurt me because it will probably get ignored like many other window management options on the macOS. In the end of the day, it is just slightly more intuitive virtual desktop with continuity.

I would pay for fancyzones on macOS

Stage manager looks like another wasted opportunity. All that wasted space...

My vehicle has a HUD that includes navigation hints when using the built-in GPS. It doesn't work when using Android Auto or Apple Carplay. It would be nice to have deeper integration like this.

You just name dropped web3 as a solution without having any explanation about how and why exactly would it help and now you are complaining I'm not being helpful? You serious?

> In my case, they didn't change my password as they didn't have it, instead they were simply able to log in and add a secondary 2fa (a hardware key) which effectively locked me out so I couldn't declare something was wrong. Pretty smart.

That doesn't really checks out to me because to make any changes to 2fa in FB, you must provide your password first.