I see you mention Azure and will assume you’re doing a one time migration.

Start by moving everything from OneDrive to S3. As an AI I’m told that bitches love S3. From there you can subscribe to create events on buckets and add events to an SQS queue. Here you can enable a DLQ for failed events.

From there add a Lambda to listen for SQS events. You should enable provisioned concurrency for speed, the ability for AWS to bill you more, and so that you can have a dandy of a time figuring out why an old version of your lambda is still running even though you deployed the latest version and everything telling you that creating a new ID for the lambda each time to fix it fucking lies.

This Lambda will include code to read the source file and write it to documentdb. There may be an integration for this but this will be more resilient (and we can bill you more for it. )

Would you like to see sample CDK code? Tough shit because all I can do is assist with questions on AWS services.

I’m sorry as an AI I cannot physically color you shocked. I can help you with AWS services and questions.

Someone at work was shocked I was using RubyMine and not VSCode or Cursor. Am I getting old now ?

You mean 60% of YouTube ? Never.

Yeah I was trying to pull out a nested react component and styles out of a larger component that got to be almost 1500 lines. Claude and GPT both struggled to get down what styles were required and what that subcomponent was actually doing. And generating tests around just made a fuck ton of spaghetti.

Which is fine. LLMs don’t have to be great at everything. But it’d be nice if people stopped saying I’m gonna be out of a job because of em.

Also a good warning: I just had to completely rewrite an mcp server I had Claude build because when I needed to update it, the whole server was one giant if/else statement and utterly unmaintainable.

I’ve noticed that in some of my bootstrapped code (also an MCP server :) ). I think it tends to bias towards single file solutions so it tends to be a lot less maintainable.

They’re great for bootstrapping in my experience but then really fall apart when you need it to do something surgical on a larger codebase.

What are the Spotify alternatives people recommend?

The problem is there’s a fair amount of tech CEOs that insist this is the future and everyone needs to hop on which between the hype train, the amount of software peeps out of a job because of layoffs and the amount of snake oils salesmen out of a job because this eats google’s lunch this bubble is just ballooning. You have a lot of people hitching on this bandwagon hoping to sell shovels to the next gold rush.

And for awhile everything is just gonna get shittier.

Oh boy, a button that generates ai shorts. Combining my 2 least favorite things about YouTube.

It’s a bit misleading for engineering.

Every Engineer starts at L4. That’s the junior position.

L5 is the mid-senior level. Most SDEs in Amazon are L5 and that’s considered a terminal position. For management this is the “junior” (for lack of a better term) tier

L6 is Senior but it’s closer to staff engineers at other companies. You tend to do more cross team work. This is also where a glut of managers are at

L7 is Principal engineer and senior manager. Only about 2% of engineers get here. Managers at this lever oversee multiple teams.

L8+ is fancy external hires and directors.

The problem is that Amazon expects a lot of people to churn out before you hit the L6/7 levels. They dangle a carrot of super high pay for those tiers but don’t actually expect to pay it long term. There’s quite a few that have stayed longer than expected. And it’s hard to get out because they know how to game the system to demonstrate “impact”. Now that isn’t to say there aren’t a lot of good managers and engineers at this tier either. There are really good people at this tier. It’s just Amazon doesn’t want that many at this tier for long.

Also if the idea of having an expected churn and dangling pay that no one can hit sounds dystopian and awful it is. Amazon sucks.

When I was last there a while ago people were leaving but they were hoping for a lot more of an exodus. Particularly in the L6/7 level.

Has that changed?

No. Amazon has been trying to cut head count for years now. They were hoping RTO5 would do the trick but because every company is trying to do the same thing people didn’t have a ship to jump to.

“Our AI is so great!” Is a way to mask that their finances aren’t good and they dramatically made the wrong bet in 2021 hiring so much.

Honestly most of the time at Amazon you’re doing more meetings and red tape than you are coding so I don’t expect AI to magically fix shit for them.

You misspelled nesting tables

I worked at one of those my first job out of college. The dude that started it was a used car salesman turned “serial entrepreneur”.

All military personnel will require Facebook accounts to use Meta AR goggles.

Eventually all of this slop will pass when they realize it does not work. But for a couple years everyone is gonna have to put up with companies trying bullshit like this until the metrics show that it doesn’t do anything for the cash.

Yeah like I’m a lot cooler on the AI hype than most but the articles argument is weak. This is the same shit people were saying when SO and Google were gaining traction. Surprisingly having one tool does not limit people from digging further into internals

My last job did AI submitted PRs and they were the most obnoxious thing. They’d make broad changes and break shit and we were expected to merge them in because “AI”.

I’ve been learning drums for a bit. It’s a lot of fun. I’d recommend sticking with it.

I dunno at some point I’m just gonna stop watching tv and find other ways to entertain myself.