jonthepirate

My team is looking for new ideas for setting up a complex system that would be much simpler and more scalable than “microservices”, which still seem to be a standard, even though we have been using this pattern for a decade.

What would be great is a product that is specifically designed to help you deal with a GitHub outage. Oh, GitHub is down? Flip this switch and your developers can somehow keep working.

I think a lot of companies would pay for this.

I think GPT is really neat. However, it cannot solve even the most basic reasoning problems I tried.

It feels like it understands what I'm asking for and it provides good answers, but so does Google.

I think calling this "Artificial Intelligence" creates a misunderstanding of what's going on because it's pattern matching.

Sure, the input and output is way better than Google, but if it can't reason, where's the intelligence? The whole thing seems like a hype train that I'm evidently not on.

I'm mostly used to Python programming..

I seems like the Java/Kotlin world largely might be sort of used to waiting 30+ seconds for a recompile after making even a 1 line code change.

I've asked around, and I've heard that yes there are ways to speed it up if you setup everything correctly and have a good strategy in place for using cache.

However, I'm getting the sense that most of the Java projects out there might have a horrific dev experience where the devs might just accept that its Java and that's how it is, in which case, there must be a lot of miserable Java devs who waste most of their day waiting.

Please someone say it isn't so..

It seems like GitHub is getting worse every quarter. Why can’t they operate it in a reliable way?

I'm looking for the best way to allow engineers at my company (1,500 engineers) to manage their GitHub repo settings via "configuration as code". The GitHub repo settings UI webpage requires elevated permissions. The UI is not a good solution for us - we have compliance requirements as well as a general need to reduce chaos and to enforce a reasonable workflow with approvals.

From what I can tell, most companies are building their own solutions with Terraform or Pulumi.

Is there something that's clearly the best solution for doing this? One thing I've come to learn is that developers don't like Terraform because of high cognitive load, and that when Terraform changes are in someone's way, it becomes the leading cause of loss of productivity.

Having not found something that feels easy to use, I'm wondering if I should possibly start an open source project that would help make it easy for any company to allow their developers to configure their GitHub repos settings as code.

Our team has been looking at Spinnaker for a while now (as well as Spinnaker vendors) but we are disappointed with the large number of bugs in the Spinnaker ecosystem. Every time we upgrade, 2 other things that worked before break. What other tools are out there we should be looking at? We want things like:

- pipelines as code - canarying - automatic canary analysis - automatic rollback - blue/green, progressive rollouts, other rollout strategies - approval gates - integration with Vault, Okta

So far, the whole thing sounds like a modern version of going to milliondollarhomepage.com with a VR helmet. I'm an engineer - please help me understand what I'm not getting.

Slack allows you to edit your "Display Name" on your profile. That's what everybody else sees. There's no enforcement of uniqueness.

In other words, if the big boss is "John Smith", you can set your "display name" to "John Smith" and you can also set your picture to John Smith's picture and then poof! you're basically John Smith in Slack so far as everybody else is concerned.

I suspect most people who use recent versions of Postman might not realize there's a new "sync" feature that seems to upload all of your HTTP request configurations to Postman's hosted servers. That leads me to believe that if Postman gets hacked, that will probably cause a wave of data breaches which seem imminent.

Here's my answer-

Time is the opposite of the speed of light and also a locally constant rate of elapse with respect to a reference frame which is not moving through the universe at light speed.

If everything moved at the speed of light, nothing would happen. At light speed there are no antecedents, no precursors.

Time is a special constant rate set by the universe that is relative to any reference frame. Time is not universally consistent - it is an unequal rate when comparing two reference frames.

The universe is a two-sided coin: on one side is the speed of light (the maximum speed available - the maximum speed of causality itself). Because nothing can happen at the speed of light in a reference frame, light speed could be considered a zero/negative/false state - impossible for any thing to achieve because we live in a world where things happen.

On the other side of that coin is time. Any thing that moves even a little bit slower than the speed of light is where you get events that elapse in reference frames. Things happening in reference frames could be considered a positive/true/1 state.

Strangely, someone moving at slightly less than light speed in a closed box would not notice anything out of the ordinary going on. Their perception of time in their reference frame of the box wouldn’t be much different than our perception of time here on earth in our local reference frame of earth.

When things move any slower than light speed, a locally constant rate of elapse emerges unique to any reference frame. Though time is locally constant within any reference frame, comparing time between two reference frames differs and those differences are caused by unequal gravity and movement forces.