AtNightWeCode

In your case it sounds more viable to move to VMs instead of RDS, which some cloud providers also recommend.

Nice. The pulse is a bit too fast for syncing breathing I think. Also, exhales should be slower than inhales.

My theory. When hovering or clicking on an icon more of the icon is visible with a tilted arrow.

It was a bad tweet and some people should have an alcohol lock on their social media accounts. But to call it a death threat is just silly.

Just to be clear. Red is the correct answer, right?

Because it is a trick question. That state is not in play.

It also breaks many user flows like when a site in an app opens an other app to complete a process. Then there is no way to get back to the site that works in all cases.

A colleague had a valid German driver license with a photo stapled on, way into the 21st century. Nice.

INTENT is the keyword for most laws. If the intent here was to check the security it is 100% legal within EU. Don't know about UK. I guess the guy poked around.

Yak shaver?

Another thing. Queues often lack prioritization of messages; for instance, the importance of a new user signup may be overlooked compared to an address update.

Next project can be a service for planning a walk in a city based on how much time one would like to spend in the shadow or in the sun.

And a public endpoint is any Internet facing endpoint including the ones where the user needs to be logged in. People seems to forget that.

I would put something like Cloudflare in front of a service like this. Bot protection may handle it and if not a technician can fix it in 5 minutes.

Looks like it. I used to work with it some years ago. I will never use it again or any other actor model based platform with remoting and magic schedulers.

Just by switching from Scrum to Kanban one can improve progress a lot. For being two very similar pull based systems the difference in effectiveness is just incredible.

I believe that the most valuable aspect of Scrum is the retrospectives. These are recurring meetings where we assess what has been effective and what hasn’t. If the retrospectives consistently focus on the same issues, such as ongoing complaints about test environments, this also indicates a fundamental flaw in the overall architecture.

Any benchmarks for implementing caching in fib in a lang with a good compiler?

A long time ago I worked on a mathlib in C/C++ and when reviewing the assembler output it often did some really clever things.

Egress bandwidth costs have been discounted for years. Including GCP. Bandwidth Alliance... Like 10 years ago traffic cost was a real problem with the cloud. Today there are other areas that are expensive.

Exactly, I had the best performance review ever at a corp I worked at. Did not make much difference when they reorganized.

Public DNS servers use rate-limiting in various ways. It should not be possible to do a large brute force attempt.

Biggest? How about serving TLS certs when doing direct IP access? Or how about leaking sub domains in TLS certs?

I, as a mediocre hacker, cough, security advisor, cough, use certs to find vulnerable subdomains all the time. Or at least. I get to play around in your test envs.

Edit: Ok, the problem in the topic is also not good.

Using emails like this is usually found during pen tests. Not Googles fault I would say even though I think OAuth is overly complicated. This is along the line of sending secrets in the token. Tokens are signed, not encrypted.

The irony. You can ask chatgpt4 if it was the right decision to fire the guy and it kinda confirms it.

This biz have basically driven me insane.

Some comments.

The problem with time estimates is that you often have to estimate not what to do but a vague vision of something. We want it to be easier to do X. How many hours?

I agree with what to promise. The problem here is that you will get pressured into bad decisions. Somebody might say that it's just a new button. It is never just a new button.

The joke, junior devs work with coding, senior devs with people is true. Many coders quit coding after some years and go full time into management positions. At some companies that is expected and you are being looked down upon if you are "still" coding.

Clean code does not really tell if a solution has good architecture. I have seen horrible solutions that use clean code and great solutions that have mediocre code.

Management typical just want new features. Prepare to be called in to help resolve issues related to bugs that has been known for months but not been prioritized.

Third-party companies are not your friends. Be prepare to work with people that will straight up lie about things. Also be prepare to work with colleagues that does the same thing.

People will try to take credit for your work. Management people are experts in this field.

But the worst thing is also the best thing about being a coder. You have to to keep up and learn new things. The biz is crazy fast. It is easy to challenge yourself. The amount of new cool stuff coming out is just amazing.

I believe the PersonClass should be sealed in a 1-1 comparison.

They most likely lie about the power outage. Azure does this all the time. I am so fking tired of these services. Even minor data centers in Europe have backup plans for power.

I also wonder how the heat maps looks like during these tests. Let me guess, there are none...

Don't hire this guy, I guess. Mobile first problems was solved like what, 10 years ago? The problem the other way around is still way more prominent. The amount of sites that still can't function normally on any mobile is just silly.

We sell CF with every customer. Not the point...