sharpy

Yep. That is what I do too. But a lot of times the changes it makes are bandaids rather than addressing root cause. I have to periodically evaluate the skills for consistency and opportunities for simplification.

What will that accomplish? Does it give license to developers to check in code that they don't understand/trust fully?

Ultimately, people should be responsible for the code they commit, no matter how it was written. If AI generates code that is so bad that it warrants putting up warning sign, it shouldn't be checked in.

We are having an unusually dry and sunny winter in PNW.. I wonder if it is related.

That sounds nice, but I think that increased tax will just be passed down as higher rent.

I wonder if US still manages to keep the most promising?

Once upon a time, our team was paying Oracle $6 million a year in DB licenses alone. We ended up building our own bespoke storage solution.

And decided that it was cheaper and easier to just outsource it to Microsoft. Because doing it in today's environment - different work computers, backend servers, mobile devices, etc - is much more complicated than just managing permissions on a mainframe.

I think AI can be really powerful tool. I am more productive with it than not, but a lot of my time interacting with AI is reviewing its code, finding problems with it (I always find some issues with it), and telling it what to do differently multiple times, and eventually giving up, and fixing up the code by hand. But it definitely has reduced average time it takes me to implement features. But I also worry that not everyone would be responsible and check/fix AI generated code.

Probably a lot of private equity buying up homes to generate rental income? Usually, I am more pro market, but I think there needs to be some regulations on this. Although if you are an existing homeowner with low interest rate locked in, you probably want more private equity investments to drive up your property value...

Intellectually, I think people agree with that. But I think the weight of history works against it. When you have a history filled with war, and intense competition...

If they get things like PyTorch to work well without carinng what hardware it is running on, it erodes Nvidia's CUDA moat. Nvidia's chips are excellent, without doubt, but their real moat is the ecosystem around CUDA.

If it becomes a liability, wouldn't the onus be on the network operators for failing to support devices sold within X years?

When they added the CM bar raiser, I felt like it hit day 2. When was that? 2014ish?

Nah, I used to work for defense contractors, and worked with ex-military people, so...

Anyway, I actually loved my first time at AWS. Which is why I went back. My second stint wasn't too bad, but I probably wouldn't go back, unless they offered me a lot more than what I get paid, but that is unlikely.

The culture changed. When I first worked there, I was encouraged to take calculated risks. When I did my second tour of duty, people were deathly afraid of bringing down services. It has been a while since my second tour of duty, but I don't think it's back to "Amazon is a place where builders can build".