etothet

I found this really fun and interesting.

I wonder how often inventions are created for one purpose, but end up primarily being used for another purpose the inventor never considered.

In our case, this is exactly what happened. An acquisition of a company where their AWS accounts that were inherited were no longer needed.

And in this case, it’s actually less secure for this one user and the account if as a workaround I’m required to create an IAM user for them (even though I can limit their use of the system).

Yes. There are solutions to all of these issues, but what often happens is these situations come about through the natural course of companies changing over time - different people managing accounts, different providers, etc. The happy path is easy, but the happy path is rarely the one we find ourselves walking down when we inherit a previously made decision.

IAM users get usernames - they don’t log in with an email address. Root users log in with their email address.

This was a secondary AWS account in use by the company that had been in place for quite some time and that secondary account was just no longer needed. So to consolidate things down, it was deleted. Also at that time, SSO wasn't being used for anything with the company - and they were on a completely different email provider.

I'm not arguing that it was impossible to know the long term outcome here, but it doesn't mean it isn't frustrating. If you've spent any length of time working in AWS, you know that documentation can be difficult to find and parse.

I can certainly understand why the policy exists. What I think should be possible is in these situations to provide proof of ownership of the old email address so it can be released and reused somehow.

Speaking of unique names within AWS, I learned the other day that even after you delete an AWS account, you can’t reuse the root user email addresses (it’s documented, but I wasn’t aware).

Someone at my org used their main company email address for a root user om an account we just closed and a 2nd company email for our current account. We are past the time period where AWS allows for reverting the account deletion.

This now means that he isn’t allowed to use SSO via our external IdP because the email address he would use is forever attached to the deleted AWS account root user!

AWS support was rather terrible in providing help.

Under "Prerequisites"[0] I see: "Get an Anthropic API key".

I presume this is temporary since the project is still in alpha, but I'm curious why this requires use of an API at all and what's special about it that it can't leverage injecting the prompt into a Claude Code or other LLM coding tool session.

[0]: https://codespeak.dev/blog/greenfield-project-tutorial-20260...

Adding Simon Willison's announcement: https://simonwillison.net/2005/Jul/17/django/

Thanks for the correction!

Over TWO decades! Rails has been around since 2004, making it just slightly younger than Django.

edit: Django was release in 2005

“I’ll just say it: I think I’m done with iPads. Why bother when Apple is now making a crackerjack Mac laptop that starts at just $600?”

I’m curious to see this machine in person, but I’d bet the an iPad is still the best large device in Apple’s ecosystem for anything that benefits from viewing in portrait mode.

Also why regular backups are necessary. Glad they helped in this case.

With great power…

“Hey you got new lines in my URLs!”

“You got URLs in my new lines!”

Sorry to hear that. From that description this person does not sound like a good manager.

If you are reading this and you are thinking you want to become an engineering manager, I urge you to think long term what you want that to look like. I've seen too often that developers who want to become managers because they think it's the next inventible step aren't prepared for the people management and HR part of that role.

And, as you move up to Director and beyond, those higher often have much less to do with actual engineering than tasks that sort of surround the world of engineering - lots of organizing information and attending meetings.

I've seen too many developers who though they wanted to manage become victim to the Peter Principle [1].

There is nothing wrong with staying a developer, even if you're not "moving up" to some idealized title. If you like the work and you can tolerate the place you work, you're probably ahead of most people in our field.

[1] https://en.wikipedia.org/wiki/Peter_principle

"The real reason is: native has nothing to offer."

I get it, but this is a bit dramatic.

One of the biggest challenges I've found with using non-native tools (and specifically the various frameworks that let you write JavaScript that compile to Native code) is that there is much less of a guarantee that the 3rd party solution will continue support for new OS versions. There's much less of a risk with that with 1st party solutions.

Additionally, those 3rd parties are always chasing the 1st part vendor for features. Being far behind the regular cadence of releases can be quite inconvenient, despite any advantages initially gained.

I encountered my first run-in with an age verification prompt when I went to authenticate into the Claude iOS app. It asked me to use me iOS/iCloud account to confirm myage. It was quick and seamless enough, but even though I'm aware of this trend, it struck me as a bit jarring.

AWS actually hosts the models. Security & isolation is part of the proposed value proposition for people and organizations that need to care about that sort of stuff.

It also allows for consolidated billing, more control over usage, being able to switch between providers and models easily, and more.

I typically don’t use Bedrock, but when I have it’s been fine. You can even use Claude Code with a Bedrock API key if you prefer

https://docs.aws.amazon.com/bedrock/latest/userguide/what-is...

https://code.claude.com/docs/en/amazon-bedrock

(I am not affiliated with AWS in any way. I’m just a user stuck in their ecosystem!)

Even if you have some basic understanding of how LLMs work, I highly recommend Karpathy’s intro to LLMs videos on YouTube.

- https://m.youtube.com/watch?v=7xTGNNLPyMI - https://m.youtube.com/watch?v=EWvNQjAaOHw

The tech sector continues to be impressive, largely due to AI (and headcount cuts). When will the bubble burst?

I've been a mostly happy 1Password customer with a Family plan for quite some time. This may cause me to jump ship.

My biggest issue with 1Password has been 1) how intrusive it can be in the browser, especially on mobile when it's too proactive to show its dropdown and just gets in the way of my experience. I know this is challenging because a mobile device is a small screen, but it is incredibly frustrating. 2) how bad the Safari extension. It regularly fails to load at all.

Aside from that, while you're absolutely correct - 1Password is still relatively inexpensive, let's look at the improvements thet mention:

1. Automatic saving of logins and payment details

Isn't this what 1Password has always done or am I misunderstanding?

2. Enhanced Watchtower alerts

I haven't seen any of these alerts ever help me.

3. Faster, more secure device setup

This I have noticed. It is very convenient

4. AI-powered item naming

This is weak sauce. I don't care for "AI" to help me name my logins/accounts/etc.

5. Expanded recovery options

I'm not sure what this is and how it's different than what they've always offered on a Family plan.

6. Proactive phishing prevention

Fine, I guess.

“The workflow I’m going to describe has one core principle: never let Claude write code until you’ve reviewed and approved a written plan.”

I’m not sure we need to be this black and white about things. Speaking from the perspective of leading a dev team, I regularly have Claude Code take a chance at code without reviewing a plan. For example, small issues that I’ve written clear details about, Claude can go to town on those. I’ve never been on a team that didn’t have too many of these types of issues to address.

And, a team should have othee guards in place that validates that code before it gets merged somewhere important.

I don’t have to review every single decision one of my teammates is going to make, even those less experienced teammates, but I do prepare teammates with the proper tools (specs, documentation, etc) so they can make a best effort first attempt. This is how I treat Claude Code in a lot of scenarios.

Part 1 is linked in this article and explains a bit: “Minions are Stripe’s homegrown coding agents. They’re fully unattended and built to one-shot tasks. Over a thousand pull requests merged each week at Stripe are completely minion-produced, and while they’re human-reviewed, they contain no human-written code.”

I could be wrong, but my educated guess is that, like many companies, they have many low hanging fruit tasks that would never make it into a sprint or even somewhat larger tasks that are straight forward to define and implement in isolation.

I second this. I do use some terraform, but for most of our stacks, CDK has been fantastic.

I definitely noticed this on Opus 4.6. I moved back to 4.5 until I see (or hear about) an improvement.

I came here to ask this question. I find the existing agentic coding integraton to be clunky and slow. I've had much better luck with my Xcode projects just using my agentic coding tool of choice in the CLI.

The short answer to your question is “yes”. I’ve been a part of projects that largely leveraged agentic coding tools and produced net posititve results. BUT, we didn’t skip code review and we didn’t lower the bar for what good code looks like.

In my personal experience (working as part of a team and not a solo dev), good documentation and well-documented/enforced practices can produce great results. That said, it’s not 100% perfect but neither are humans.

Maybe the US government can make a requirement that DJI divest and spin of a US controlled subsidiary. That seems to have worked great with ByteDance and TikTok.

It feels like the author is conflating Tailwind the open source project vs. Tailwind Labs the business, which Adam says has run into a bad situation with their revenue because Tailwind Labs’ paid projects aren’t getting as much traction as fewer and fewer users visit the official Tailwind docs, which is currently the primary source people find out about those commercial products.

Regardless of what happens to the company (my personal opinion is that they’ll come out of this strongee than before) Tailwind as OSS probably isn’t going anywhere for the foreseeable future.