We discovered a bug in AWS Bedrock that is double counting cache writes when thinking/reasoning is enabled for the Anthropic models. It’s not clear to me if this is limited to just AWS Bedrock or all providers. AWS Support is aware.
We’ve also observed a much higher cache miss rate in the past few weeks. Combine both together and your usage consumption can be greatly increased.
This is the way. As others mention opening window is your cheapest option, but you lose a lot of your heating and cooling efficiency. We installed a whole house ERV for about $10K and saw a significant drop in CO2 readings.
I wonder if there is a case to be made for a patch branch that gets all PRs. Then the maintainer can do any further tweaks needed before merging down to mainline.
Another way to look at it is you are expected to include business factors into your decision making. Sometimes the most optimal engineering solution is not the most optimal business solution. Politics can definitely be a factor, but being able explain clearly why doing something helps the business can be a big part of making the jump to more senior roles.
Have you considered looking at Amazon for their ARM offering (Graviton)? I'd be hesistant to use M1 minis for a production workflow as they are not really production grade (lacking ECC memory, not sure how long they are rated to run at high CPU, lack of user replaceable disks, no RAID, etc...).
It sounds like you just don’t enjoy frontend work. If you are trying to build a product on your own it’s impossible to avoid, but there are plenty of companies in the EU and US hiring for backend developers. Understanding how both sides get work done is important, but there is nothing wrong with focusing on just one area.
It's funny I have a logitech cam at the top of my monitor, which effectively covers the exact same space as this new notch. The bezels on monitors have gotten so thin it's tough to include add ons.
I get the use case, but I just can’t get behind using software like this for security reasons. It’s too easy to add users to slack, leading to accidentally exposing secrets.
Having worked remote before the pandemic I found having my camera on was a very good reminder to the team that I was still there. Increasing your visibility when you are one of a few remote employees is very important.
All that said a camera only helps so much. There is something to be said for traveling to your office periodically to put in real face time. I’m looking forward to offices starting to open up here soon.
I think having a zero P0 and P1 bug policy makes sense. As others have said some bugs may not make business sense to fix. I do think it is useful to set thresholds for other bug priorities as well. 1,000 P2 bugs may make your product feel unusable.
Type inference is super handy in a lot of places. The problem I've run into in the rust book and other intro docs is they almost always use type inference, which makes it harder to learn what is going on. I'd prefer they used explicit types to start and then ease into type inference.
That's fair. When I say appreciate, I mean the results of the grind. Washing Dishes or any type of cleaning isn't fun, but finding coping mechanisms (zoning out, music, etc...) you can enjoy the results.
All jobs have some amount of grind. Being able to acknowledge its going to suck and push through it quickly can be super beneficial to your career. It's also one of the reasons why I encourage those in high school or college to try a non technical job first. Learn to appreciate doing monotonous tasks well.
We’ve also observed a much higher cache miss rate in the past few weeks. Combine both together and your usage consumption can be greatly increased.