ryanthedev

Features and stories should be completable in the span of an iteration.

Epics and Features are prioritized by the business and product. They can be expected to slide from iteration to iteration.

Any User Story or task should be expected to be completed an a single iteration.

If you keep having open stories stop bringing in a complete story. Just assign tasks.

Features and Epics are pointed.

Business looks at points earned per year or quarter. Look for trend.

IT leadership looks at amount of open stories and tasks that were moved from iteration back to the backlog. Over the span of all iterations.

This will ensure teams are breaking down work into actionable goals.

You essentially combine multiple fields. Creating a quantum entanglement between each force.

This will create a small field of negative energy. Think opposite of black hole.

>As a PhD in physics, this just sounds like nonsense to me. Energy isn't a field and to polarize it doesn't mean anything

Well considering light is energy and you can polarize that.

The inventor is saying you can create gravitational waves through with just EM. Now you need to combine sound and angular momentum. Add a shit load of volts. Like Tesla on crack. And create high frequency standing wave in a resonance chamber. Boom you have the equivalent to a laser. But using all of physics in a perfect storm of power.

You cannot guarantee the angles at which they enter the gas.

They also stated to using different wavelengths out of sync. Which would cause the angle of refraction to be different.

Different angles of refraction lead to different changes of speed as they enter one medium to another.

Also I'm not sure what you mean "the photon momentarily energizes". The photon has a constant amount of energy. A beautiful balance of kinetic vs potential energy.

What does this mean for the double slit experiment?

Quantum Computer.

This sounds like refraction. Two beams traveling through the cloud. If you use a double prisim, you could achieve the same type of results.

I wonder what graphic design app they used. it's such a common problem with these types of apps.

they never include spelling and grammar features as default options.

I think I lost a job because of this reason. I even had a coworker proof read it. I can't spell :(

Time to convert to PWAs

I totally understand where the author is coming from. Though a full stack dev like an ER doctor.

This is due to https://youtu.be/s86-Z-CbaHA

It's more common in enterprises than you would think. Remember, automated testing is a fairly new concept. Some of these applications and developers have been doing it the same way for 15 years.

Well this is more from an architect manager. Trying to manage offshore and internal tech stacks is always difficult. Out source work via FAAS user stories.

Functions As A Service! It has worked great from the few implementations I have seen.

If not passport could be drivers license. Or state id. Which would make sense because they don't allow certain state IDs to fly anymore. Everybody had to update.

This is how it works. Airline takes multiple photos of you. Sends those photos along with flight context data. Over secure lines. To Homeland. They match photo to passport and passport info to flight manifest. All outside of the airlines infrastructure. Or at least should be.

I had to use a jar in a .net program. Do you know how much of a pain in the ass that was?

I work for an airline. I known about constraints. If I knew only one language, I never would be at the level I am. Here is the tech stack I deal with daily.

VB6 Kix scripts Powershell .net 3.5 Winforms WPF .net 4+ .net core .net asp Java JavaScript React Angular C++ Golang.

If programming is a job and not your craft, it will be harder for you. You just have to practice more.

Buy vs build? Go ahead. Buy. Spend 40 million a year.

https://www.nytimes.com/2019/04/10/nyregion/nyc-gps-wireless...

Terrible analogy. 1+1=1. More like Ax + Bx = 1.

Be sure to check out open source repos.

https://github.com/haraka/Haraka

Listen on a port. Parse bytes. Encode bytes. Parse text.

Implement SMTP.

Looks like an awesome read!

I love this! Makes me remember the nights I spent lerking online for og hacking info.

They don’t care. Study basic data structures and alogrithums.

When you’re waterfall and try to act agile.

I agree, the other half of AI is classically trained learning. They end up using the help desk to train their algorithms.

You just stated reasons to move to micro services. Keep the code small and non complex. Smaller code bases lead to smaller changes. You abstract complexity through interaction. You hand off complexity to a higher level of orchestration.

I think people don’t understand what a true enterprise monolith actually looks like.

Just what I have been looking for. +1. Can’t wait to take it for a test drive.

I apologize! my retort was dismissive and not beneficial to solidifying my theory.

I agree the effects of at least earths gravity is “small”; I wouldn’t say negligible.

When dealing with predictions of a spin on an electron through a scattering process, even the smallest interference will skew your result.

We have a hard time trying to measure or detect gravity; I have a theory if you perform the entanglement process on earth and then tried to detangle the message on the moon, your results would be different. Or even better on a moon of Jupiter!

The same reason people say it would be impossible to modify an entangled qubit. Since the reversal of the scatter would end up with a different wave pattern.

Thank you for taking the time to reply! I’m hungry for some intelligent debate.