ryanthedev

Poor design. Sharing code between microsercices is always a design smell.

You are just building services on top of another monolith...

Sounds like you needed to abstract the work being send to the worker, instead of abstracting the worker around the work.

Meaning don't have many workers for one payload type. Abstract the payload and have a single worker...

That's why most systems become complex and spaghetti. Poor abstraction, so you use shared code to fix it...

So http3 will be using UDP? Makes sense.

Will we see more performance tuning when it comes to MTU sizes?

I like that. Change it to understand it.

Everything is an abstraction. Everything is a protocol.

Keep expanding your knowledge.

Read the new pragmatic programmer.

It took me about 5 years to get over my imposter syndrome.

Dont get hung up over one project. I have written a lot of bad code and a lot of clever code. Both in the same project.

Being a good dev is a lot like being a good doctor. Study and practice, sometimes you will get it right, sometimes you won't.

It's like a seat belt. You are only happy to have it when shit his the fan. Lol.

Kube isn't for small businesses. It's for enterprises.

Most developers aren't running the clusters, they are 99% of the time managed by the cloud provider.

Why would I ever order VMs and manually run a kube cluster.

But as an operator needing to manage clusters and multiple teams, I spend my time coding automation.

I'm not saying kube is not simple, but it's a lot easier then managing application runtime on VMs.

Before kube I was managing 260+ VMs (hyperv was internal managed DCs central/east) for my products in-house app. I had to essentially build my own poor man's orchestration platform to manage applications and deploying.

I love it! Really cool idea and execution! I would love to experiment using a ball as the selector.

My current strategy for binding automation is using my razer naga and binding all those buttons to do various actions depending on the app that's up.

I enjoy this line of thinking, having domain knowledge is always critical to success. Being invested is always ideal.

I would like to counter with the delivery transformations I have been apart of, the role of the architect has dried up.

I do predict for most large enterprises the role of a manager will start to become more full stack and becoming that invested visionary technical leader and mentor. At least that's what I hope for...

Well you misunderstood that I was referring to refraction as being the reason for dark matter predictions. I was trying to imply that it can explain why the universe is expanding. Instead of the theory of dark matter.

I already gave you my reasoning for dark matter calculation, baryonic waves. Which you so happened to ignore?

Also I would like to add that galaxies have been observed to contain non dark whatever. So baryonic acoustic waves still fit that model.

First thing to understand is the only evidence we have for the universe expanding is redshift.

Do I believe refraction is at all related to Dark mass/energy? Not all all. Refraction has nothing to do with that. Refraction has to do with redshift being miscalculated.

Compression waves are the culprit and the field that propagates those waves for dark garbage. baryonic acoustic waves give direct evidence as the perp.

We know very little about our universe. We can't even define the Hubble constant. Dark matter theory is a joke imo.

These nerds don't even understand refraction. Space isn't empty.

If space isn't empty you will never be able to account for the path photons actually travel.

Gas causes refraction, how could you be sure the photos that hit the lens in your telescope actually traveled in a straight line.

I know this will get down voted to hell. IDC.

.net core in general has grown, building cross platform scalable apps is a breeze. Also they have really built some great performance libs, (Channels, Pipelines, Span, Memory).

The tooling is a little wonky at times when it comes to blazor. Hopefully they will turn this into a flagship product.

The pure rage this website brought me. I blame that for my loss of logic.

All I could think to myself was "not another one"

I have been talking about PHX having a mini boom of IT jobs. The cost of living has taken a hit though.

Just gotta stand the heat.

There is no reason it couldn't run a wasm file? As long as the OS browser supports it.

I feel like this is the UI abstraction layer. If you want to run chromium, there is no reason you couldn't extend it.

Code is prime for extending and enhancing.

Beautiful MVP. I really love this idea.

I have been tinkering around with some enterprise solutions for delivering desktop native experience for web based apps.

I use tests when I need to debug certain sections of my code. It's faster in the overall development process.

Also most of my tests revolve around business logic, where I need to test multiple versions of data.

The best advice I could give would be test cases around errors.

That's usually where most bugs are found, when something doesn't return what you expect.

The gap will be even larger, more low code UI and FaaS are going to make hiring a lot harder.

I think we don't spend enough time on socket level programming and concurrency.

I don't know how many Java devs are still writing blocking IO code..

Thanks! I scoured the wiki. Didn't find any examples of using an infinite set. Could you be a bit more specific? It's definitely possible I missed the section.

Is 90 years the representation of the average age of a person?

What if it didn't matter that they were alive or dead?

Meaning I have a hat with every name and birthday of every "human". Every time someone is born, their name is added to the hat. Essentially an infinite set of names would be added.

What's the probability when N is infinite? Like a grocery store with an infinite amount of checkout lines.

If sound propagation has a negative mass, couldn't this same effect muddy the dark matter/energy numbers?

We usually tag the release with something.

I work for an enterprise. We automated the change control process and integrated it with our CD dashboard. So a quick peak at the dashboard will tell us.

Though depending on the criticality of the app. We may only retain a previous release for a specific time period.

I mean it's not rolling back or rolling forward.

It's just doing another deployment. It doesn't matter what version you are deploying.

That's the whole point.

My teams go into their CI/CD platform and just cherry pick which build they want to release.

No. No. No.

When designing a system you always need to start top down.

Too many times I see a developer sit down an immediately start from the database.

Start from the UI or API. Just like we have UX for UI, you should be taking experience into account when designing an API.

Yeah. It is? I mean that's how we determine the half life of things...

An anycast address doesn't change. I mean come on. And it actually operates on layer 4. It uses layer 4 to actually work?

I hope you didn't pay for your education.

TTLS isn't a thing.

You're argument about keep alive makes no sense. You're confusing the nginx documentation. 100 is the number of default connections it will hold open. 60 is the default timeout. Also it's sent as an HTTP response to the client in the headers...

Here you need to read up: https://nginx.org/en/docs/http/ngx_http_core_module.html#kee...

The timeout only matters if you're not making requests. Setting a low keep alive will actually result in more DNS requests...doh

Next you're going to tell me you only write blocking code and use a thread per connection...

I guess you haven't created many 10k concurrent app servers.

That's not true. It all depends on the implementation...

Also what are you talking about? If the connection is closed, how would it be used?

Connections should only be closed due to? Inactivity. If a connection is closed, don't you think you would probably want to do another DNS request?

Also if your doing proper layer 4 load balancing using BGP, DNS is a moot point...

Magic...

Seems like DNS TTL was a big issue before HTTP 1.1.

Connections are cached and reused.